This is a follow-up on jwa package bugs reported by me

<http://www.freepascal.org/mantis/view.php?id=10359> <http://www.freepascal.org/mantis/view.php?id=10360> <http://www.freepascal.org/mantis/view.php?id=10361> <http://www.freepascal.org/mantis/view.php?id=10362> <http://www.freepascal.org/mantis/view.php?id=10363> <http://www.freepascal.org/mantis/view.php?id=10364> <http://www.freepascal.org/mantis/view.php?id=10365>

and a private discussion about them with Marco van de Voort.

Marco asked how I ran into the bugs. Well, I used

- target win32
- the external linker
- USES JwaPsApi, JwaTlHelp32

With this setup, the application no longer starts up for reasons reported (and many others not reported).

My questions are
- has this always been the case with the external linker ?
- can this be fixed in FPC ?
- if not, do we have to conditionalize for various versions of Windows ? or use static linking only for routines that are common to the various (supported) versions of Windows ?

Regards,

Adriaan van Os

Adriaan van Os wrote on do, 13 dec 2007:

Maybe the internal linker uses smart linking by default, while the external one doesn't? What happens if you use -XX? (the makefiles should compile those units always into smartlinkable versions regardless of which linker you use, check your svn compilation log files to ensure they are built with -CX)

Jonas

---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

Adding -XX has no effect. Neither has adding CREATESMART=1 and LINKSMART=1 to the svn build (which adds -CX and -XX). I am testing this with a win32 targeted crosscompiler on i386-darwin. However, Marco mentioned that he could reproduce the problem on native win32. So, this is unlikely a fault in my svn build setup.

Regards,

Adriaan van Os