Re: Application without GUI lib dependence?

[Nicola Pero]

On 6 Aug 2009, at 17:39, Martin Kalbfuß wrote:

> How can I tell the application project type in the makefile to  
> ignore the gui
> libs? I want to create my game as application type, not as tool,  
> because it
> isn't a tool.

This was added in 2.0.5.  You need to add xxx_NEEDS_GUI to your  
GNUmakefile, where xxx is your APP_NAME.  Eg.

-------

include $(GNUSTEP_MAKEFILES)/common.make

APP_NAME = Vanity
Vanity_OBJC_FILES = Vanity.m
Vanity_NEEDS_GUI = NO

include $(GNUSTEP_MAKEFILES)/application.make

--------

From the release notes --

`xxx_NEEDS_GUI'
     This new variable can be used to specify that a project needs to  
be
     linked against the gui library (or not).  If set to yes, the gui
     library will be linked; if set to no, the gui library will not be
     linked.  If unspecified, the generic variable NEEDS_GUI is used;  
if
     that is also unspecified, the behaviour depends on the project  
type
     (and is backwards-compatible): applications, bundles, frameworks,
     palettes and libraries link automatically against the gui library;
     other project types do not.  It is recommended that you set
     xxx_NEEDS_GUI for all bundles, frameworks and libraries to clarify
     how the linking should be done.

`NEEDS_GUI'
     This new variable can be used to specify that all projects built  
by
     this GNUmakefile need to be linked against the gui library (or
     not).  If set to yes, the gui library will be linked; if set to
     no, the gui library will not be linked.  This behaviour can be
     overridden for specific project targets by using the xxx_NEEDS_GUI
     variable (see above).

Thanks and sorry for the late reply