[M3devel] M3Config contains paths to installation directory.

[Jay K]

 The current layout is indeed:  
 
 
  installroot/bin/cm3  
  installroot/bin/cm3.cfg  
  installroot/bin/cm3cg  
  installroot/bin/config/*  
 
 
There are imho too many files in config to put them in bin.
 
 
  cm3.cfg is just a two line stub:  
    INSTALL_ROOT = path() & "/.."
    include(path() & "/config/" & HOST) 
 
 
 If you really want the files in, e.g. installroot/etc.: 
 
   INSTALL_ROOT = path() & "/.."   
   include(path() & "/../etc/" & HOST)   
 
 
or another example you could use is:
  cd $CVSROOT/m3-sys/cminstall/src/config-no-install 
  cp *.common  installroot/cm3/bin  
  cp target installroot/cm3/bin/cm3.cfg  
 
 
or what I use:  
  cd $CVSROOT/m3-sys/cminstall/src/config-no-install 
  cp cm3.cfg installroot/cm3/bin  
 
 
That cm3.cfg delegates out to CM3_ROOT/m3-sys/cminstall/src/config-no-install so that when I am editing in CM3_ROOT/m3-sys/cminstall/src/config-no-install, I don't have to keep copying the file around and never accidentally edit the copy and then wipe it out by recopying it.
 
 
It is an excellent model imho, but also not for everyone (ie. if you don't have the CVS tree!). 
 
 
It also provides for changing the TARGET somewhat on the fly on "multiarch" systems like NT386+Cygwin, SOLsun + SOLgnu, but I'm no longer liking that model and have started having /cm3, /cm3.cygwin, /cm3.interix on such systems instead.
 
 
 
 - Jay



----------------------------------------
> From: dragisha at m3w.org
> To: jay.krell at cornell.edu
> Date: Fri, 31 Jul 2009 10:00:11 +0200
> CC: m3devel at elegosoft.com; eiserlohpp at yahoo.com
> Subject: Re: [M3devel] M3Config contains paths to installation directory.
>
> My question was about location and names of secondary config files. Are
> these changed again? What would ne shipping procedure for compiler
> installation? Something new there?
>
> /cm3 is excellent idea, but on organized system (and if you package for
> general public) some standard location is preferred. I will change my
> locatio to /opt/cm3 now.
>
> dd
>
> On Fri, 2009-07-31 at 07:54 +0000, Jay K wrote:
>> sorry /usr/local/cm3/bin -- or wherever cm3 is installed.
>> I actually use just /cm3, but I often alter my examples to fit more common practise. Sometimes it helps confuse people less to use typical concrete paths instead of metata syntax. Esp. because puting less than and greater than around things causes hotmail to remove them, so lame, so tempting meta syntax doesn't work..
>>
>> Just as /tmp/foo can be replaced by anything.
>>
>> - Jay
>>
>>
>> ----------------------------------------
>>> From: dragisha at m3w.org
>>> To: jay.krell at cornell.edu
>>> Date: Fri, 31 Jul 2009 09:47:37 +0200
>>> CC: m3devel at elegosoft.com; eiserlohpp at yahoo.com
>>> Subject: Re: [M3devel] M3Config contains paths to installation directory.
>>>
>>> On Fri, 2009-07-31 at 07:06 +0000, Jay K wrote:
>>>> mkdir -p /tmp/foo/bin/config
>>>> cd /tmp/foo/bin
>>>> cp /usr/local/bin/cm3 .
>>>> cp /usr/local/bin/cm3.cfg .
>>>> cp /usr/local/bin/config/* config
>>>> export PATH=/tmp/foo/bin:$PATH
>>>
>>> Please tell me /usr/local/bin/config/* is mistake here...
>>> --
>>> Dragiša Durić
>>>
> --
> Dragiša Durić 
>