Re: dev environment for starters

My one recommendation is that compiled code should be built and
installed as a user and leave the base system intact. All of the build
dependencies can be installed in a different prefix.

2.2 I want to install all the development code in a separate prefix
inside my HOME directory. What environmental variables should I set to
be able to compile and run binaries and libraries from a different

For example, to install into $HOME/gnome you need to set :
export GNOME_PATH=$HOME/gnome
export PATH=$HOME/gnome/bin:$PATH
export PKG_CONFIG_PATH=$HOME/gnome/lib/pkgconfig

and autogen/configure the projects with --prefix=$HOME/gnome	

That info servers as good background on how things work, but jhbuild
makes this a lot easier this days, the README inside jhbuild will show
you how to use it. All I do right now on a clean install to set up the
dev environment is "jhbuild bootstrap" & "jhbuild build $foo".


On Tue, 2002-12-10 at 17:18, Neil Weisenfeld wrote:
> I'm just curious how people manage their development environment.  I'm
> interested in doing some hacking.  Right now I live off of Ximian
> snapshots, and presumably I'm better off building everything from CVS,
> rather than fighting random library incompatibilities by building things
> piecemeal.
> Here's the rub: I *live* in GNOME2.  Not in the Tron sense, but it's my
> daily desktop environment.  Is it maybe wise to install *releases* for
> general consumption and have a separate build area that's usually
> up-to-date w/ CVS HEAD for development?  Or do people tend to live daily
> w/ whatever is committed?
> Neil
> -- 
> Neil Weisenfeld
> Surgical Planning Laboratory
> Brigham and Women's Hospital
> neil bwh harvard edu
> weisen ai mit edu
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]