<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
I think this code should be moved into the config files. ?<BR>
All non-Windows config files would just say:<BR>
<BR> <BR>
readonly proc WindowsResource (file) is<BR>end<BR><BR><BR>and then NT386.common would have the current content of winRes.tmpl.<BR>
<BR>
Thoughts?<BR>
<BR>
More so, cm3.exe should just implement<BR>
proc WindowsResource (file) is<BR>end<BR><BR>
without readonly, and then NT386.common can replace it.<BR>
The others can leave it alone.<BR>
<BR>
Thoughts?<BR>
<BR>
I'm not really sure what should be "core" vs. what should be "an extension".<BR>
It is nice to have such an extensible system, but it can also be bad.<BR>
<BR>
<BR>
Besides that, Windows has a nice feature called "version resources".<BR>
If nothing else, every .dll/.exe should have one.<BR>
cm3 should give everyone some default.<BR>
imho.<BR>
<BR>
- Jay<BR><BR><BR>> Date: Wed, 18 Feb 2009 11:51:39 +0000<BR>> To: m3commit@elegosoft.com<BR>> From: jkrell@elego.de<BR>> Subject: [M3commit] CVS Update: cm3<BR>> <BR>> CVSROOT: /usr/cvs<BR>> Changes by: jkrell@birch. 09/02/18 11:51:39<BR>> <BR>> Modified files:<BR>> cm3/m3-sys/windowsResources/src/: winRes.tmpl <BR>> <BR>> Log message:<BR>> 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?<BR>> <BR><BR></body>
</html>