On 01/27/2011 03:56 PM, Stephen Greenwalt wrote:
Boot Camp . . . good idea.  Docs . . . good idea.

Let the newbie's like me (coming out of boot camp) write some of the Docs.

Presently I have everything compiled and running under Ubuntu, and I am just reviewing the code to get some sort of context.

It is huge.  Incredible, actually.  Who wrote all of this?  Wow.

A few comments:

* It seems to work best to put the entire project (all source, and all build product) under a project folder in the Home directory.
For me, not at all.  I put the gimp trunk, the babl trunk, and the gegl trunk under /usr/local and they install into /usr/local/lib, /usr/local/include, and /usr/local/bin.  Since I have /usr/local/bin in my path first they're found first.  I have my ld.so.conf.d contain a file that puts /usr/local/lib into the ld.so configuration.
* If possible, that should include a copy of any external dependencies . . . with environment variables (etc) adjusted accordingly
* The project ought to be able to exist in a "bubble" . . . so as to avoid confusion . . . regarding copies of dependencies that might exist in the OS.
For me that bubble, is /usr/local
* Multiple different project versions ought to be able to exist on the same machine without stepping over each other.
I just use the trunk.

Note: I wrote a minimal bash script that duplicates (automates) the steps I took to get to the present state.  Maybe we could expand on that idea.
I just pull the sources down from git, configure and make babl, configure and make gegl, configure and make gimp.  All easy and automatic.  No script needed.

* If we do it right, compiling for Linux vs. Windows vs. OSx ought require no more than the flip of a switch.  The Blender folks, and others, are moving in that direction.
* Shouldn't we standardize on a common development IDE (like Eclipse)?  If I am missing something in that area . . . let me know.
I, and a lot of other geeks like me don't use IDEs.


Gimp-developer mailing list

Reply via email to