Thanks for the clarification ~suv,
On Mon, Dec 7, 2009 at 11:49, ~suv <suv-sf@...58...> wrote:
Main goals of the current 'gimponosx' project afaiu are
- use as many system libraries as possible
- reduce the number of bundled MacPorts libraries
- don't use $DYLD_LIBRARY_PATH or rpath or rewriting the
install_dir with install_name_tool
These are all laudable goals that we should pursue also.
resulting in -among other things- these steps:
- use a 'private' MacPorts tree with a prefix that is a link in /tmp for
building all dependencies needed for GIMP
- use a local MacPorts repository provided by 'gimponosx' (for
portfiles, patches and some source tarballs)
- build GIMP using the same prefix, the link in /tmp will be recreated
on every system when launching GIMP.
but this looks like a clunky workaround and this is what I called "reinventing their own wheel". Of course, said like that it sounds a bit pejorative, but it is not, really ;). The reality is that, to make gimp or inkscape exactly how we would like them to be, the best solution would be to compile all dependencies manually ourselves, where we want them and how we want them. However, using macports is so much more practical that we currently leverage that. gimponosx places the trade off towards more control than we do. I would not object getting our build process a bit more complex if it resulted in better integration of Inkscape afterwards. I just don't have time to get involved in it.
You can browse the SVN repository and search for the changes to allow building a 64bit GIMP version on Snow Leopard: http://gimponosx.svn.sourceforge.net/viewvc/gimponosx/
and there are news about the recent builds for Snow Leopard on the projects website: http://gimp.lisanet.de/Website/News/News.html http://gimp.lisanet.de/Website/News/Eintrage/2009/11/7_64-bit_GIMP_version_is_out.html
thanks.
JiHO --- http://maururu.net