[M3devel] FW: winRes.tmpl/mingw/rc/windres/etc.

Jay jay.krell at cornell.edu
Wed Feb 18 12:40:54 CET 2009


[truncated..]

From: jay.krell at cornell.eduTo: m3devel at elegosoft.comSubject: FW: winRes.tmpl/mingw/rc/windres/etc.Date: Wed, 18 Feb 2009 11:27:23 +0000

I think this code should be moved into the config files. ?All non-Windows config files would just say: readonly proc WindowsResource (file) isendand then NT386.common would have the current content of winRes.tmpl. Thoughts? More so, cm3.exe should just implementproc WindowsResource (file) isendwithout readonly, and then NT386.common can replace it.The others can leave it alone. Thoughts? I'm not really sure what should be "core" vs. what should be "an extension".It is nice to have such an extensible system, but it can also be bad.  Besides that, Windows has a nice feature called "version resources".If nothing else, every .dll/.exe should have one.cm3 should give everyone some default.imho.  - Jay> Date: Wed, 18 Feb 2009 11:51:39 +0000> To: m3commit at elegosoft.com> From: jkrell at elego.de> Subject: [M3commit] CVS Update: cm3> > CVSROOT: /usr/cvs> Changes by: jkrell at birch. 09/02/18 11:51:39> > Modified files:> cm3/m3-sys/windowsResources/src/: winRes.tmpl > > Log message:> adapt to MinGW which has windres instead of rc with different command line usage; detect MinGW by checking if backend mode is integrated backend or not, not great..it should really be informed by a variable in the toplevel configuration -- CONFIG_HAS_RC and CONFIG_HAS_WINDRES?> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090218/5f9ddf0c/attachment-0002.html>


More information about the M3devel mailing list