You'll use "make install" when you want to do a normal FSSTND /usr/ or /usr/local style install where everything scatters across the filesystem in foo/gnucash/* directories. You'll use "make install-opt" when you want a /usr/local/opt/gnucash style install where everything just installs into local bin, doc, share, etc dirs. I couldn't think of a better way to handle this, or I would have used it. So the two most likely sets of build instructions would be as follows: For a full system install (gnucash is installed as part of the system): ./configure --prefix=/usr --sysconfdir=/etc make motif make install For an /opt style install ./configure --prefix=/usr/local/opt/gnucash make motif make install-opt ---------------- depending on your make target, you'll produce: gnucash.motif gnucash.motif.static gnucash.gnome gnucash.gnome.static gnucash.qt Whichever one you produce last ends up the target of a local gnucash.bin symlink, so that you can always run the local ./gnucash script to see the last flavor that you built. The ./gnucash script also handles making sure that you're using files from the source dir rather than an install tree just like the old ./xacc script did. Finally, I've re-worked things so that it's harder to accidentally install a binary that's stale with respect to your install destination, and I've eliminated the need for the wrapper script in the install tree. Unfortunately this did require that "make install*" re-build the binary during the install process because it can't know where the one startup file that it has to know about internally is going to be until you pick an install style. All this may not be perfect, but I think it's better than what we had before, and we can always improve it once we figure out something better. -- Rob Browning PGP=E80E0D04F521A094 532B97F5D64E3930 ----- %< -------------------------------------------- >% ------ The GnuCash / X-Accountant Mailing List To subscribe, send mail to majordomo@gnucash.org and put "subscribe gnucash-devel your@email.address" in the body