<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Should the mingwin/msys method just be a configuration of NT386?<BR>
A command line option to cm3 and/or an environment variable?<BR>
<BR>
The targets are nearly the same.<BR>
The difference just needs to be exposed somehow, so the config file can switch betwen two implementations of a few functions -- compile_c, m3_link, make_lib.<BR>
If Windows cminstall/src/config/NT386 and cminstall/src/config/NT386GNU, you see very very similar.<BR>
<BR>
Maybe they vary just in BUILD_DIR? Or does that break things?<BR>Profiling changes BUILD_DIR so I figure it might be ok.<BR>
I tried making BUILD_DIR not readonly and setting it with cm3 -D, doesn't work.<BR>
It can probably be set conditionally in the config file based on another variable though, I'd have to check.<BR>
<BR>
Besides, it might be nice for a notion of a set of build_dirs that are probed.<BR>
In particular, you might have some C or C++ code that uses GCC (or Microsoft) extensions.<BR>
That could also be handled by a different variable, like compile_with_gcc() and compile_with_msvc() in the m3makefile and then cm3 would switch between compile_gcc and compile_msvc instead of the usual compile_c functoin.<BR>
<BR>
There is a high degree of interoperabilty between these two or even all three platforms.<BR>
<BR>
Perhaps this is a can of worms though. Much potential utility but too complicated to think about?<BR>
<BR>
Perhaps I too desperate to have fewer platforms?<BR>
I do need multiple build_dirs, like three, that is certain.<BR>
<BR>
- Jay<BR><br /><hr />Helping your favorite cause is as easy as instant messaging. You IM, we give. <a href='http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join' target='_new'>Learn more.</a></body>
</html>