Startup script changes: what and why

[Mike Alexander]

--On April 7, 2010 10:37:37 AM -0400 Derek Atkins <warlord at MIT.EDU> 
wrote:

> Geert Janssens <janssens-geert at telenet.be> writes:
>
>> So you mean that in xcode you start gnucash-bin directly, which
>> works because  you have set the proper environment variables for it ?
>>
>> Would you mind sharing which environment variables you have set for
>> this to work ? I guess you had to add additional paths to some
>> parameters to pull this off as the scheme files are scattered
>> throughout the source code.
>
> I suspect he just duplicated the "gnucash-build-env" script within
> xcode.
>
> -derek

No, it's more complicated than that.  I wanted to use files from the 
build tree, not the install tree, when debugging.  That saves having to 
do a make install, and polluting the presumably working version of 
GnuCash.  So when debugging I do a make in the appropriate 
sub-directory of the build tree (usually from a shell, but this can be 
done for the top level directory from XCode itself) then start GnuCash. 
I haven't completely eliminated the use of the install tree when 
debugging, but it's pretty close.

If people think it makes sense I could check in the XCode project file 
and a default user config file.  They would be set up for my build 
configuration.  I build in a different directory than the source tree. 
That way I can blow away the entire build tree and start over without 
affecting the source tree.  The build tree (relative to the source 
tree) is "../build/darwin".  Before building in a directory for the 
first time, I use the lndir command to symlink the source directory 
into the build directory.  This isn't strictly necessary, but it makes 
some things easier.  If others set things up this way, I think they 
could use the XCode project directly without any changes.

        Mike