[M3devel] More MxConfig

[Jay K]

ps: I should add that the way it was before was broken from
a certain legitimate point of view.
 
 
The M3Config paths were computed at build time, i.e. on Olaf's machine, i.e.
they would point into /tmp or /home/hudson/work/cm3-inst or such.
 
 
If you built things yourself, then ok, they worked.
 
 
cminstall did not handle this. They were just constant strings
in a generated M3Config.i3.
 
 
cminstall could only "fix" MxConfig.
 
 
I still think this is progress, though it would be nice if HOST worked
and I have to look into path().
 
 
 - Jay


----------------------------------------
> From: jay.krell at cornell.edu
> To: dragisha at m3w.org; m3devel at elegosoft.com
> Date: Mon, 3 Aug 2009 08:42:22 +0000
> Subject: Re: [M3devel] More MxConfig
>
>
> Do you want to be able to move your cm3 install around, without editing the config file?
> You know, "be relocatable without any fixup code"?
> That is the big question. That is what MxConfig buys.
> These "variables" are computed, by running quake code.
> They are in fact known at install time, unless you later move the install around,
> and require something (cminstall) to modify the config files at install time.
> If nobody cares about moving installs around without invalidating their config file,
> we could put it back to a bunch of string constants. And we'd have to put back
> the markers that trigger cminstall to replace stuff.
>
>
> BUILD_DIR is basically constant either way. But, do you care about profiling? I don't really.
> Actually probably none of the tools properly support profiling anyway, except cm3.
> They would have to accept a command line switch.
>
>
> Dragiša, do you have the symbolic HOST vs. actual string problem in cm3.cfg?
>
>
> A difference biting us is that cm3 does set a few values, such as PROFILING, SL, HOST.
>
>
> I haven't solved the path() problem yet that Randy reported.
>
>
> - Jay
>
>
>
> ----------------------------------------
>> From: dragisha at m3w.org
>> To: m3devel at elegosoft.com
>> Date: Mon, 3 Aug 2009 10:08:55 +0200
>> Subject: [M3devel] More MxConfig
>>
>> This MxConfig thing looks like a bloody mess.
>>
>> To access former M3Config data I must have cm3.cfg suite present (to
>> date I only had it in -devel packages, but ok...)
>>
>> Except cm3.cfg - ok, it's only set of text files, I must have sysutils,
>> m3middle and m3quake.... A chunk of compiler.
>>
>> All this to read three or five variables from system.
>>
>> Also, this:
>>
>> VAR
>> PKG_INSTALL := MxConfig.Get("PKG_INSTALL");
>> BUILD_DIR := MxConfig.Get("BUILD_DIR");
>>
>> PROCEDURE DoImportBase() =
>> BEGIN
>> EVAL DoImportFile(PKG_INSTALL & "/libm3/" & BUILD_DIR &
>> "/.M3WEB", TRUE);
>>
>> Fails on Concat in DoImportFile line - both variables NIL.
>>
>> Do I have some more voodoo to do to initialize MxConfig subsystem?
>>
>> --
>> Dragiša Durić
>>