<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br>> cm3 should process -D on command line earlier? <br><br>I want to be able to say in the config file:<br><br>if defined("cm3_verbose")<br> M3_FRONT_FLAGS += ["-v"]<br>end<br><br>if defined("cm3_verbose_version_stamps")<br> M3_FRONT_FLAGS += ["-vsdebug"]<br>end<br><br><br>this doesn't quite work because cm3 processes the -D on the command line fairly late -- after it reads "the config file" and before it reads "the m3makefile".<br>(Each of which can and often does include additional files.)<br><br><br><br>I'm working on this change.<br><br>Alternative a specific flag to cm3 for each frontend flag might be good.<br>I guess verbose is actually already handled.<br><br>Shall I just "pretend" they are the same?<br>Add frontend flags to cm3 and have cm3 pass them on?<br>i.e. specifically -vsdebug?<br><br><br>see <br>/cm3/m3-sys/m3front/src/misc/Host.m3 for possible frontend flags<br><br><br>Hm..the thing is, these are mostly meant to be pretty obscure.<br>Often-but-not-always target-specific, set by the config file, and not meant to be user-editable.<br>For example the C backend and NT386 backend have requirements around -inline_nested_procs vs. -unfold_nested_procs. Though really the C backend could easily be made to work either way, esp. at this point that it is many-pass.<br><br><br><br>Reasonable?<br><br><br>(I'm specifically wanting -vsdebug to track down what types the C backend is seemingly uninformed about...)<br><br><br> - Jay<br><br><br><br> </div></body>
</html>