[M3devel] compiler version number

Jay K jay.krell at cornell.edu
Wed Jul 21 22:31:42 CEST 2010


It's working on Windows.

jbook2:~ jay$ cat /dev2/cm3/scripts/version.quake 
CM3VERSION = "d5.8.2"
CM3VERSIONNUM = "050802"
CM3LASTCHANGED = "2009-07-15"

jbook2:~ jay$ cat /dev2/cm3/scripts/version
CM3VERSION d5.8.2
CM3VERSIONNUM 050802
CM3LASTCHANGED 2009-07-15

 - Jay

________________________________
> From: rcolebur at SCIRES.COM
> To: m3devel at elegosoft.com
> Date: Wed, 21 Jul 2010 14:52:05 -0400
> Subject: [M3devel] compiler version number
>
>
> I grabbed the minimal 5.8.6 archive for Windows.
>
>
>
> Using this archive, “cm3 –version” yields:
>
>
>
> Critical Mass Modula-3 version 5.8.6
>
> last updated: 2010-04-11
>
> compiled: 2010-07-12 21:11:13
>
> configuration: .\cm3.cfg
>
> host: NT386
>
> target: NT386
>
>
>
> But, when I use this edition to rebuild everything from the main trunk,
> “cm3 –version” now yields:
>
>
>
> Critical Mass Modula-3 version d5.8.2
>
> last updated: 2009-07-15
>
> compiled: 2010-07-21 17:29:53
>
> configuration: C:\cm3\bin\cm3.cfg
>
> host: NT386
>
> defaulting to native build: I386_NT
>
> target: I386_NT
>
>
>
> Can someone please explain how the version number and timestamp info
> get integrated into the compiler?
>
>
>
> If I can get a handle on the way it’s currently done, I’ll try to fix
> the problem I’m having on Windows with the info regressing.
>
>
>
> Regards,
>
> Randy Coleburn
>
>
 		 	   		  


More information about the M3devel mailing list