<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
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.<br>That is how make-dist.py works, for example.<br>And be sure the config files use path() to find themselves, instead of hardcoding their location.<br><br> - Jay<br><br>> To: rodney_bates@lcwb.coop<br>> Date: Mon, 28 Mar 2011 09:51:33 -0700<br>> From: mika@async.caltech.edu<br>> CC: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] How to install cm3 at a nonstandard location<br>> <br>> I think I pass the target directory to cminstall on the cmd. line, something like:<br>> <br>> ./cminstall /path/to/installation/root<br>> <br>> "Rodney M. Bates" writes:<br>> >I tried to build cm3 head and install at /usr/local/cm3-head.<br>> > From the installation notes, I set environment variable<br>> >CM3_INSTALL to this path. After fixing several failures<br>> >involving merges by cvs, I discovered it had been putting<br>> >things into /usr/local/cm3, where I have the latest cm3<br>> >release, giving me a mixture of stuff from the head and<br>> >the release, which I certainly don't trust.<br>> ><br>> >I was building instead of using cminstall, like the the install<br>> >notes were referring to. However, before I started, I found<br>> >code in scripts/sysinfo.sh setting up CM3_INSTALL to the default,<br>> >unless already set, which I took to mean this was the way to<br>> >do it when building too.<br>> ><br>> >I did double and triple check my spelling and value of<br>> >CM3_INSTALL, before and after the failed builds.<br>> ><br>> >So how do I get this to work?<br>> ><br>> >This was on LINUXLIBC6.<br>> ><br>> >Rodney Bates<br>> ><br> </body>
</html>