> I would consider such a tool usable only
> if it had no arbitrary limits, such as a maximum size of 65000 bytes for
> an exports list
I have to eat my words: the exports list is _not_ limited in size by wgcc.
Sorry.
Bruno
___
http://
No. __declspec(dllimport) tells the compiler that an indirection is
needed. The compiler will simplify '&externvar' to '_imp__externvar'.
There is one _imp__externvar per library, but all their values are the
same.
The "same function name, different address" problem will occur - as far
as I und
Hello,
Markus Duft wrote:
> I implemented wgcc (a compiler wrapper behaving like gcc but calling
> cl.exe). Since the target should be to compile sources with minimum
> changes i have done lot's of work for this.
That's certainly a good idea. I would consider such a tool usable only
if it had no
Hi there!
I implemented wgcc (a compiler wrapper behaving like gcc but calling cl.exe).
Since the target should be to compile sources with minimum changes i have done
lot's of work for this. The only thing one has to do with wgcc is:
Define a macro like MYPROG_EXPORT to __declspec(dllexport) wh
