-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2005-03-21 23:32:53 +0000 Nicola Pero <[EMAIL PROTECTED]> wrote:
Unfortunately Windows (and other platforms I think) requires all symbols in a bundle to be resolved when the bundle is linked. So having the bundle depend on symbols in the application which is supposed to be loading them is not a particularly good way of helping the building process.
I think perhaps you have been concentrating a bit too much on windows ... if you take a mental step back and think about what bundles are for, I think you will see that this is a case where windows and the build system need to be made to accomodate bundle usage rather than the other way round. Bundles are used to provide plugin features for applications and libraries ... so it's only reasonable for them to use the symbols of the application they are going to be plugged in to. Forcing the developer to put anything a bundle might need in an externals library might get cleaner code, but would be a burden on them. Also it would mean that you have to provide that external library for them to link against, rather than providing just the header file detailing the API the bundle may use in the application, and the application binary itsself.
I suppose I could try to hack the building system to have the application's symbols exported etc ... (did I remember correctly that someone did an attempt at that already ?)
That sounds like the right thing to do. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using the GPG bundle for GNUMail
iD8DBQFCP78lE6AJp3nmKIkRAn10AJ9QXTQhzAexnDDSnXwNtDLOPe+9ZwCgxhUX abKXdNPzDDJdmRU6cOOR34w= =VezK -----END PGP SIGNATURE-----
_______________________________________________ Gnustep-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnustep-dev
