Hi Przemek,
This should be fixed by adding PP and COMMON libs.
using global export flag will not help here in any way.
You're right, now it seems okay. Too many variations
in short time, so I hope it will stay this way. It also
works with MSVC now.
Please remember that it may also reduce the speed. It's not only
additional information but also possibly different code.
It's a link time option, the code seems to stay the same.
Maybe it affects .exe loading time, but it's not noticeable
for a 23MB .exe.
Now I have to change the build process to use HARBOURFLAGSLIB
and HARBOURFLAGSEXE instead of current HARBOURFLAGS and
HARBOURFLAGSDLL, the difference between them is -n1 option
vs -n. Executables should use -n, libs (.dll and .lib)
should use -n1.
It's enough to add support for MAIN() as default startup function
when non of functions is declared with HB_FS_FIRST and make all
builds with -n1.
We can also define that when MAIN() exists it's an application
entry point instead of symbol defined with HB_FS_FIRST. It will
have higher priority. In such case we can remove -n1 flag.
Choose what you prefer and I'll implement it.
I like the second one better, as it clears the ambiguity
and even the requirement to use -n switch when someone
defines MAIN(). So there would be one thing less to worry
about. First choice however is more Clipper compatible,
so IMO we should do it.
Other opinions are welcome, of course.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
