Re: How ot build in separate directory

[Helge Hess]

Some side notes ;-):

Nicola Pero wrote:
> To build RPM package, the procedure is as follows -
>
>  - start with a clean system

You can do at least two things to make this easier
a) a change-root environment
b) a separate install-root with an own RPM database

Eg SuSE build each package in a freshly boostrapped chroot environment, 
therefore they are more or less guranteed to have proper dependencies.

For our pkgs we use b). We create a separate GNUSTEP_SYSTEM_ROOT, patch 
GNUstep.sh using sed to the location and build in there. After all 
GNUstep has some kind of "chroot" built-in :-)

Greetings
  Helge

>  - build the RPM package of gnustep-make (that will install it into
> something like /var/tmp/gnustep-make, then build the package from what was
> installed there)
>
>  - install the RPM package of gnustep-make (that will install it into the
> final location)
>
>  - source GNUstep.sh
>
>  - build the RPM package of gnustep-base (that will install it into
> something like /var/tmp/gnustep-base, then build the package from what was
> installed there)
>
>  - install the RPM package of gnustep-base (that will install it into the
> final location)
>
>  - build the RPM package of gnustep-gui
>
>  - install the RPM package of gnustep-gui
>
>  - etc
>  
>
> I'm not sure how your packages work, but I think it's very likely that you
> will need a similar setup - 
>
>  - start with a clean system
>
>
>  - build the gnustep-make package
>
>  - install it
>
>  - source GNUstep.sh
>
>
>  - build the gnustep-base package
>
>  - install it
>
>
>  - build the gnustep-gui package
>
>  - install it
>
>
>  - build the gnustep-back package
>
>  - install it
>
>
>  - etc etc etc
>
> Hope that helps.
>
>
> > i'm making packages for my own package manager, if it wasnt for that i'm 
> > sure i would be set.
> >
> > anyhow, i'm just gonna install it to it's "normal" spot then copy the 
> > pieces over to build the packages.  Its ugly but it'll work!
> >
> >
> >
> > Thanks!
> >
> > Chad
> >
> >
> >
> > On Sunday, June 30, 2002, at 11:51 PM, Nicola Pero wrote:
> >
> >
> > > > This has probably been discussed before so sorry.
> > > >
> > > > I've been trying to find this in the makefiles and the GNUstep.sh and I
> > > > can't find the proper way to build GNUstep binaries in different
> > > > directories than the installation directory (lke making an RPM)
> > >
> > > Hmmm ... Ok - I'm confused by your statement :-)
> > >
> > > Either you mean 'to build gnustep binaries in different directories than
> > > the _source_ directory' or maybe you rather mean 'to _install_ GNUstep
> > > binaries in different directories than the installation directory', 
> > > which
> > > would explain the 'like making an RPM' comment.
> > >
> > >
> > >
> > > > It was easy t do with GNUstep-make, the "special-prefix" variable made
> > > > this quite handy.  But how to do it with gui, base, etc?
> > >
> > > Because you're talking of special-prefix, I think what you really want 
> > > to
> > > do is relocate the whole installation into somewhere else - precisely 
> > > what
> > > is needed to build rpms.
> > >
> > > Something like -
> > >
> > > make INSTALL_ROOT_DIR=/var/tmp/package-build/ \
> > >     GNUSTEP_INSTALLATION_DIR=/var/tmp/package-
> > > build/usr/GNUstep/System \
> > >     install
> > >
> > > should do it then.
> > >
> > > [If you're building RPMs, you are certainly aware that gnustep-make can
> > > build that for you :-) have a look at core/make/Master/rpm.make.]
> >
> > http://www.sf.net/projects/simplygnustep
>
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://mail.gnu.org/mailman/listinfo/discuss-gnustep