[M3devel] How to install cm3 at a nonstandard location

[Jay K]

Another approach is to copy a few things to the new location, e.g. config files, cm3, cm3cg, and then use those to build/ship.
That is how make-dist.py works, for example.
And be sure the config files use path() to find themselves, instead of hardcoding their location.

 - Jay

> To: rodney_bates at lcwb.coop
> Date: Mon, 28 Mar 2011 09:51:33 -0700
> From: mika at async.caltech.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] How to install cm3 at a nonstandard location
> 
> I think I pass the target directory to cminstall on the cmd. line, something like:
> 
> ./cminstall /path/to/installation/root
> 
> "Rodney M. Bates" writes:
> >I tried to build cm3 head and install at /usr/local/cm3-head.
> > From the installation notes, I set environment variable
> >CM3_INSTALL to this path.  After fixing several failures
> >involving merges by cvs, I discovered it had been putting
> >things into /usr/local/cm3, where I have the latest cm3
> >release, giving me a mixture of stuff from the head and
> >the release, which I certainly don't trust.
> >
> >I was building instead of using cminstall, like the the install
> >notes were referring to.  However, before I started, I found
> >code in scripts/sysinfo.sh setting up CM3_INSTALL to the default,
> >unless already set, which I took to mean this was the way to
> >do it when building too.
> >
> >I did double and triple check my spelling and value of
> >CM3_INSTALL, before and after the failed builds.
> >
> >So how do I get this to work?
> >
> >This was on LINUXLIBC6.
> >
> >Rodney Bates
> >
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20110329/c26447fc/attachment-0002.html>