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)
Fred Kiefer schrieb:
David Ayers wrote:
I think you should consider deprecating the automatic inclusion of
gui.make by:
- moving the current gui.make from Additional to Auxiliary
- having a new gui.make in Additional use the technique above to insure
backward compatibility for at least the
David Ayers wrote:
Nicola Pero schrieb:
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. :-)
Maybe a gnustep-make variable to switch from GUI bundles to non-GUI
But the SSL bundle still doesn't build, because it wants to link
with gnustep-gui, I see no reason in that. Additionally I
can't find any clue where these dependency comes from.
The 'dependency' (actually there is no real dependency on gui) will
be coming from the gnustep-make files
On 8 Feb 2008, at 13:39, Thomas Gamper wrote:
Hi!
I am currently trying to build gnustep from svn. There arose some
issues regarding the base library. First the SSL bundle needs a
rather new gnutls library, so I downloaded an actual version
(2.2.1), built and installed it. Still