<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
> Please try out on macOS and Linux.<div><br></div><div>Ah, I forgot that the Linux test needs to wait until we merge "fix_include_order". I will update that soon-ish to Eliot's most recent commits from yesterday.</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;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 16.07.2021 16:18:14 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">
It's ready: <span style="font-size: 10pt"><a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/573">https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/573</a></span><div><br></div><div>Please try out on macOS and Linux. Because CI is currently working only for Windows.</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;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 14.07.2021 07:57:54 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">
Looks like FAT32 is still the least common denominator for features we can rely on in a file system. :-)<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;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 13.07.2021 18:51:46 schrieb tim Rowledge <tim@rowledge.org>:</p><div style='font-family:Arial,Helvetica,sans-serif'> <br><br><br>> On 2021-07-13, at 9:04 AM, Eliot Miranda <eliot.miranda@gmail.com> wrote:<br>> <br>> <br>> <br>>> On Jul 13, 2021, at 1:53 AM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br>>> <br>>> <br>>> 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....<br>> <br>> 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.<br><br>Damn, that's annoying. Links are such a nice solution to this kind of thing when used well. I would *love* to see a directory like 'RISC OS' that contained all the files needed to build that platform; local files for the platform and links to all the 'shared' files. It makes it so much easier to understand what files you need to look at when working. Yet again, Windows buggers things up - when I wrote the first versions of VMMaker it had to be warped to cope with Windows and Andreas' 'interesting' views on code arrangements.<br><br>But yeah, make variables can kinda handle it tolerably well within the make world.<br><br>tim<br>--<br>tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>The past, present, and future walked into a bar. It was tense.<br><br></marcel.taeumel@hpi.de></eliot.miranda@gmail.com></div></blockquote>
</div></div></blockquote>
</div></div></blockquote>
</div></body>