<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
> As I stated before, it should be possible to write a perl/python/ <br>> whatever script which takes our module.mk files and some extra bits, <br>> and auto-generates all the vcproj files for all MSVC versions from it. <br>> Of course, "somebody" would have to code it.<br>> Actually, it might be easier not to use the module.mk files but rather <br>> simply use all *.cpp and *.h files found in each engines/ subdir, and <br>> just hardcode the mapping (inside the new tool) of directories <br>> (graphics, engines/FOO, sound, gui, ...) to subprojects and likewise <br>> hardcode the settings for each subproject (i.e. optimization settings, <br>> ENABLE_FOO flags, etc.).<br>> <br><br>The main problem is not with what source files are contained in the project<br>files of each engine - that's relatively straightforward. The problem lies with<br>compilation options and defines for each engine, which is what this<br>patch solves, by moving all compilation defines in one common file, and<br>leaving only the engine files in the project files of each engine.<br><br>Regards<br>Filippos<br><br><br /><hr />Windows Live™: Keep your life in sync. <a href='http://windowslive.com/explore?ocid=TXT_TAGLM_WL_BR_life_in_synch_062009' target='_new'>Check it out.</a></body>
</html>