<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On Jul 13, 2021, at 1:53 AM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hmm... all of our build systems are able to create symlinks, right? Couldn't we just create that "src/vm" symlink to point to the particular flavor? Hmm....</div></span></div></blockquote><div><br></div>I would council against this. We’ve tried using symlinks in 3dicc builds abd have issues with git and Windows 10 that result in corrupted repositories. Let’s not rely on symlinks. Make has much better support for variables and substitutions than file systems.<div><br><blockquote type="cite"><div dir="ltr"><span><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr"><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 13.07.2021 09:38:36 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Ah, I noticed the pattern "../../platforms" (or similar). Well, by flattening the sources one level, that pattern would still work.<div><br></div><div><div><image.png></div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 13.07.2021 09:22:24 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Please find attached a change set for VMMaker and a screenshot of what the src folder would look like. A diff for all build files will follow soon here on this list.<div><br></div><div><div><image.png></div><br></div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 13.07.2021 08:49:24 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">Hi all!<div class="mb_sig"></div><div><br></div><div>I would like to clarify (or re-arrange) the structure of the source tree so that we can continue to work on existing and experiment on new flavors of the VM. They would then better match our build structure:</div><div><br></div><div>/src/plugins -> (same)</div><div><br></div><div>/src/vm -> /src/vm.32bit.cog.v3</div><div>/stacksrc/vm -> /src/vm.32bit.stack.v3</div><div><br></div><div><div>/spurstacksrc/vm -> /src/vm.32bit.stack.spur</div><div>/spurstack64src/vm -> /src/vm.64bit.stack.spur</div></div><div>/spursrc/vm -> /src/vm.32bit.cog.spur</div><div>/spur64src/vm -> /src/vm.64bit.cog.spur</div><div><div>/spursistasrc/vm -> /src/vm.32bit.sista.spur</div><div>/spursista64src/vm -> /src/vm.64bit.sista.spur</div><div><br></div></div><div><div>/nsspurstacksrc/vm -> /src/newspeak.vm.32bit.stack.spur</div><div>/nsspurstack64src/vm -> /src/newspeak.vm.64bit.stack.spur</div></div><div>/nsspursrc/vm -> /src/newspeak.vm.32bit.cog.spur</div><div>/nsspur64src/vm -> /src/newspeak.vm.64bit.cog.spur<br></div><div><br></div><div><div><div>/spurlowcodestacksrc/vm -> /src/lowcode.vm.32bit.stack.spur</div><div>/spurlowcodestack64src/vm -> /src/lowcode.vm.64bit.stack.spur<br></div><div><div>/spurlowcodesrc/vm -> /src/lowcode.vm.32bit.cog.spur</div><div>/spurlowcode64src/vm -> /src/lowcode.vm.64bit.cog.spur<br></div><div><br></div></div></div><div>This would make 15 different *src folders disappear from the source tree's toplevel. Flavor-specific plugin lists might be defined from within VMMaker and generated into their respective src folders.</div><div><br></div><div>Also<span style="font-size: 10pt">, there would be a clear place for /src/vm.32bit.interpreter.v3 too :-)</span></div></div><div><br></div><div>Thoughts? Opinions? Objections?</div><div><br></div><div>Best,</div><div>Marcel</div></div></div></blockquote></div></div></blockquote></div></div></blockquote>
</div></span></div></blockquote></div></body></html>