running from build dir

[Christian Stimming]

Actually I'm running the CVS HEAD branch directly from the build directory 
simply by modifying the src/bin/overrides/gnucash script as below and then 
calling it directy from the src/bin/overrides by ./gnucash . This works quite 
fine and it is extremely convenient to only run "make" in those directories 
where the source has been modified.

Christian

chs at ckiste:~/org/gnucash/gnucash-1.9/src/bin/overrides> cvs diff
Index: gnucash
===================================================================
RCS file: /home/cvs/cvsroot/gnucash/src/bin/overrides/gnucash,v
retrieving revision 1.2
diff -r1.2 gnucash
2c2
< exec gnucash-env guile -e main -s "$0" "$@"
---
> exec ./gnucash-build-env guile -e main -s "$0" "$@"


Am Mittwoch, 22. Dezember 2004 00:56 schrieb Chris Shoemaker:
> I found that some instructions in HACKING for running gnucash from the
> build dir didn't quite work.  Since ./src/bin/overrides/gnucash*
> expect that $PATH is already setup, they do stuff like 'exec
> gnucash-env ...'.  But, ./src/bin/overrides/ (where gnucash-build-env
> lives) is not in $PATH, so one solution is to specific the relative
> path from the build root.  That seems to be how e.g. gnucash-valgrind
> works.  OTOH, this seems kind of limiting, since CWD must now always
> be the build root dir.
>
> I'm still grokking all the startup scripts, but here's my initial
> impression: There are two conflicting designs here.  One, you want to
> "magically" find the right executables, even if the path isn't set
> correctly, hence generate-gnc-script forces all the paths and wraps
> every executable.  But two, it would be nice to run from the build dir
> -- IOW, to do precisely what # one is trying to prevent.  :(
>
> Would these two interests be compatible if the implementation were
> different? or is it better to just 'make install' after every compile?
>
> Perhaps the forcing of full pathnames can be delayed until 'make
> install'.  That way the scripts that live in the build dir could also
> run in the build dir.
>
> -chris