[Vm-dev] Proposal | Clean-up source tree's *src folders

tim Rowledge tim at rowledge.org
Tue Jul 13 16:51:36 UTC 2021



> On 2021-07-13, at 9:04 AM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> 
> 
> 
>> On Jul 13, 2021, at 1:53 AM, Marcel Taeumel <marcel.taeumel at hpi.de> wrote:
>> 
>> 
>> 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....
> 
> 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.

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.

But yeah, make variables can kinda handle it tolerably well within the make world.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
The past, present, and future walked into a bar. It was tense.



More information about the Vm-dev mailing list