OpenEuphoria

Re: 32-bit Ints in Eu2C dlls

• Posted by "Juergen Luethje" <j.lue at gmx.de> Feb 07, 2005
• 439 views

Me wrote:

<snip>

> Today I built the current version of my DLL, using "make_atom". It
> worked fine! After translating the code, I realized that the .def file
> containd 114 routine names. But I only want 11 routines to be exported!
> So it doesn't matter, whether or not there are 2 more names in the .def
> file, it isn't "clean" anyway. Sorry, I didn't think of that yesterday.
>
> So until I have a better idea I'll do the same as before, concerning the
> .def file. For each project, I'll write the desired .def file by hand,
> and after translation I'll replace the automatically produced .def file
> with my hand-written .def file. The replacement can be done automatically
> by a batch file.
>
> The cause of this clutter is, that there is no way to tell the translator
> explicitely, which routines I want to export, and that the translator
> automatically exports *all* global routines -- even those, which are in
> included files. Again that scope issue concerning "include" ... 

Some hours ago, I uploaded the new version of my wrapper for the Eu2C
Windows translator to RDS' User Contributions page. It has the
additional option to export only global routines that are defined in the
main module of a DLL.

<shameless double-plug for the record>
Using your (Matt's) "32bits.zip" together with my "ecwr.zip" makes it
_easy_ now to translate Euphoria (at least) 2.4 and 2.5 programs, and
passing 32-bit integers to exported routines in DLLs and SOs, as well
as controlling which routines are exported, and including resources in
DLLs and EXE files on Windows. 
</shameless double-plug for the record>

Regards,
   Juergen