<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'><div>These messages:</div><div><br></div><div>***</div><div>*** runtime error:</div><div>*** <*ASSERT*> failed.</div><div>*** file "../src/convert/Convert.m3", line 47</div><div>***</div><div><br></div><div><br></div><div>1) It should really be a full path.</div><div><br></div><div>I know people will disagree with me.</div><div>You want more commonality across machines.</div><div>I'm not sure that is worth it.</div><div>In particular, debuggers always work more easily with full paths, <span style="font-size: 12pt;">for local private builds.</span></div><div>Hopefully for debugging someone else's, some search path</div><div>with "prefix replacement" is viable.</div><div>But debugging your own build is more common and ideally</div><div>no special setting is needed to make that work.</div><div><br></div><div>Yes, full paths could "leak" across machines but I think that is ok.</div><div><br></div><div>I did work on this long ago but people disagreed with at the time.</div><div><br></div><div><br></div><div>2) We could/should trim the root of the git checkout, so it says</div><div>e.g. m3-sys/m3front/src/convert/Convert.m3 i<span style="font-size: 12pt;">f that is easy.</span></div><div><br></div><div><br></div><div>Some C compilers have that feature, when people are concered</div><div>with cross machine consistency for the sake of caching and similar</div><div>build optimizations.</div><div><br></div><div><br></div><div>I still prefer #1.</div><div><br></div><div><br></div><div>3) Or at least m3front/src/convert/Convert.m3</div><div>3b) or ../../m3front/src/convert/Convert.m3</div><div><br></div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;">if we really want it to be a correct relative path from the target directory.</span></div><div><br></div><div><br></div><div>A big part of the problem is the build system is geared toward packages,</div><div>not multiple packages. I'd like to solve this problem too somehow someday.</div><div><br></div><div><br></div><div>Really -- #1 -- source paths should be full paths.</div><div><br></div><div>C compilers vary here btw, in terms of what __FILE__ is and what is</div><div>in debugging information.</div><div>Sometimes whatever is passed on the command line is used.</div><div>Sometimes full paths are computed by the compiler.</div><div><br></div><div><br></div><div> - Jay</div> </div></body>
</html>