[M3devel] problems with cm3.cfg and MxConfig

[Jay K]

I will address #1 by changing the cm3.cfg files to say the actual target instead of depending on host.
I still have to look into #2, that's the first I heard of it, but it could be again some difference between cm3 and all the other m3quake users.
 
 - Jay



________________________________
> Date: Mon, 3 Aug 2009 00:52:45 -0400
> From: rcoleburn at scires.com
> To: m3devel at elegosoft.com
> Subject: [M3devel] problems with cm3.cfg and MxConfig
>
>
>
>
>
>
>
> I have been working on the problem of cm3ide not getting the BUILD_DIR from cm3.cfg. I've run across some perplexing test results.
>
>
>
> MxConfig.Get("BUILD_DIR") is returning NIL on Windows XP & Vista. I've tracked it down a bit further. There seem to be two issues that must be fixed to solve this problem:
>
>
>
> 1. HOST does not seem to be defined. In particular my "C:\cm3\bin\cm3.cfg" file appears as follows (this is the file Jay recommended):
>
> INSTALL_ROOT = path() & "/.."
>
> include (path() & "/config/" & HOST)
>
>
>
> Is HOST a variable? Or, was I supposed to replace it by "NT386"? If the latter, my bad on this one--I took Jay's message literally.
>
>
>
> 2. path() does not appear to always yield the path to the bin folder. In particular, it seems to work fine unless you invoke the program when the current directory is actually set to the bin folder, in which case path() seems to return the empty string.
>
>
>
> So, if Í%=C:\, and I run cm3ide, path() returns "C:\cm3\bin" as it should.
>
> But, if Í%=C:\cm3\bin, and I run cm3ide, path() returns "".
>
>
>
> So in the latter case, the include statement winds up trying to pull a file from the wrong place, e.g. "/config/NT386" rather than "C:\cm3\bin/config/NT386"
>
>
>
> Regards,
>
> Randy Coleburn