> It would be nice instead for the author of the bundle to be able to > control if gnustep-gui should be used when linking or not; ie, if > it's a "GUI bundle" or a "non-GUI bundle". :-)
OK - I implemented all that in trunk. xxx_NEEDS_GUI can be set to YES or NO to force linking (or not linking) against gnustep-gui. If nothing is specified, the traditional behaviour is followed: applications, bundles, frameworks, palettes and libraries link against the gui library (if available), all others do not. I recommend specifying xxx_NEEDS_GUI = YES/NO in all bundles, frameworks and libraries to make sure the right type of linking is always done. Older gnustep-make versions will ignore it; newer ones (well, from the next release) will use it to make sure the gui library is linked (or not) as required. That's good as it will prevent any of these "ghost dependencies" problems. So it should all be completely backwards-compatible. :-) Thanks _______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
