[M3devel] More MxConfig

[Dragiša Durić]

New auto-configuring cm3.cfg stuff is all ok. Great!

I don't see importance of "moveable around" in that. Only "no need for
cminstall and markers". "moveable around" is good when building from
source using some kind of cm3-min. 

While at that, cm3-supermin with only cm3 binary and config files
(probably cm3cg) would be supersmart feature. I am curently using
cm3-min as a bootstraping device, and first thing I do is making libm3
and m3core over from supplied source.

"Moveable around" is probably good, but if a chunk of compiler
infrastructure included in any program reading those variables is price
- I think it's good point to reconsider goals and ways.

On Mon, 2009-08-03 at 08:42 +0000, Jay K wrote:
> 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.
-- 
Dragiša Durić <dragisha at m3w.org>