gstep-make 2.0 Re: gstep-base Re: [OGo-Developer] OGo Invoice Application

[Sebastian Reitenbach]

Hi,

developer@opengroupware.org wrote: 
> developer@opengroupware.org wrote: 
> > On 31.12.2007, at 02:43, Sebastian Reitenbach wrote:
> > >> Not sure what you mean by "hardcoded FHS stuff"?
> > > I just mean the hardwired pathes in the objective-c sources.
> > 
> > There are no hardwired pathes, there are just specific relative  
> > (subdir) names. And I fail to see how else this can be done?
> > Since there is just one (configurable) lib dir, do you want to put  
> > everything in a single place? Why would you want to do that instead of  
> > using subdirs?
> > Please enlighten me ...
> The hardcoded share/sope-.../dbadaptors 
> What if someone had the idea to rename sope for some reason, what if 
someone 
> has the idea trying to port the software to a not unix like operating 
> system? Maybe some standard will change over time, and someone decides to 
> start all directory names with an uppercase letter. Well, maybe not too 
> often, but having easy switchable configuration options would make life 
> easier in general, no matter whether compile time or runtime option.
> And with "hardcoded FHS stuff" I did not meant, that the GNUstep lookup 
path 
> stuff is not hardcoded too ;)
> 
> > 
> > > Only for -devel packages, the Headers are going into the GNUstep  
> > > Header
> > > dirs. As they are not needed for running sope/ogo I did not cared  
> > > about
> > > them.
> > 
> > This isn't the most important thing for me. Though its definitely un- 
> > Unixy ;-)
> but maybe NEXTish ;)
> > 
> > > For developing, a working gnustep environment is required too, I saw
> > > no point why they should not end up there.
> > 
> > Because for developing a GNUstep environment is NOT required, only for  
> > running.
> > How could it be required for compilation?
> Well, when you only want to compile from source and install, or develop, 
the 
> headers are needed in both cases.
> I just wanted to say that when you install from packages for your system, 
> and you only want to run OGo, then you do not need to care about the 
headers 
> files.
> 
> > 
> > > Further I don't have seen yet a variable or sth. that is intended to  
> > > install
> > > the headers outside the GNUstep header directories.
> > 
> > 
> > Too bad ... But probably you can do using GNUSTEP_HEADER_INSTALLDIR or  
> > something. Ask Nicola ;-)
> I've seen these <Instance>_HEADER_FILES_INSTALL_DIR, but these are 
defining 
> relative pathes, beginning from the Header dir, defined in GNUstep 
> Environment.
> I'll need to check whether there is a variable, but would it really be a 
big 
> problem if the Header files would not end up in e.g. 
> $FHS_INSTALL_ROOT/include?

I've just came across this line in Makefiles/Instance/Shared/headers.make:
HEADER_FILES_INSTALL_DIR = $($(GNUSTEP_INSTANCE)_HEADER_FILES_INSTALL_DIR)

I think that looks promising do the trick.

Sebastian