[M3commit] CVS Update: cm3

[Jay K]

ps: regarding environment variables, you can do something like:
 
if not equal($FOO, "")
 
Look for my uses of $OS for example, which is Windows_NT on NT.
 
That's been in quake "for as long as I've been paying close attention".
 
Possibly new feature SUbst_env("${foo}bar${foo}") is equivalent
to old feature $foo & "bar" & $foo
 
but I'm not certain.
 
Notice m3-sys/cminstall/src/config-no-install/cm3.cfg:
 
local readonly proc CM3TargetProbe() is
 
    if not equal($CM3_TARGET, "")
        TARGET = $CM3_TARGET
        return
    end
 
    if defined("TARGET")
        return
    end
 
    if defined("HOST")
        TARGET = HOST
        write("defaulting to native build: ", TARGET, EOL)
        return
    end
 
    if equal($OS, "Windows_NT")
        TARGET = "NT386"
        write("defaulting to native build: ", TARGET, EOL)
        return
    end
 
    error(
        "unable to determine target -- try setting the CM3_TARGET environment variable" & CR
        & "Possible values include FreeBSD4, I386_DARWIN, LINUXLIBC6, NetBSD2_i386, NT386, PPC_DARWIN, PPC_LINUX, SOLgnu, SPARC, SPARC32_LINUX, SPARC64_LINUX, AMD64_DARWIN, AMD64_LINUX"
        )
end

 
 - Jay



----------------------------------------
> From: jay.krell at cornell.edu
> To: wagner at elegosoft.com
> CC: m3commit at elegosoft.com
> Subject: RE: [M3commit] CVS Update: cm3
> Date: Fri, 24 Jul 2009 14:02:25 +0000
>
>
>> I'm going to setup a compilation job for m3cc on each platform,
>> and let that trigger the cm3 builds. Of course m3cc building is
>
> You mean clean builds, right?
> Changing m3cc triggers a clean build of everything else.
> But really this doesn't have to be separate. Up to you.
> (You could use its timestamp, in fact cm3 could check its own timestamp and cm3cg's timestamp, and the config files; the m3cc builder could just update cm3cg out from under cm3, retrying if it is busy.)
> You know..the usual dilemnas of proper incremental builds..
>
> - Jay