Add interpreted languages to SCons #950
Conversation
|
If this is merged it brings us to 15/45 languages building. |
|
Viml (or rather VimL) is the Vim scripting language. I'll review this more carefully later, but it looks good to me right now. |
There was a problem hiding this comment.
I have an issue with renaming the files to the chapter name, as some projects have multiples files. Copying the files and keeping their original names should be sufficient.
We could also have a SConscript for those specific ones, but I feel it's not necessary since it's just copying files about.
|
Note: you can just grab the filenames like this: env.Copier(f'#/build/lang/{file.name}', str(file)) |
|
You're probably right, I'll fix that. I also realize that I've missed Javascript and Lisp, so I'll add those too. |
|
How does this work with #963? Should we merge one or the other first? |
|
I might have an issue, it seems we're only copying the files over, right? So that will always succeed even if the code has issues, no? |
PeanutbutterWarrior
force-pushed
the
add-interpreted-languages-to-scons
branch
from
19687b7 to
c29525b
Compare
|
If you find a way to compile interpreted files, you are welcome to tell us that way. However, it's basically the same thing as for the x86-64 implementation of the forward Euler method that segfaults... We can't do much more than copy files over (well, we could run them, but that's gonna add a lot of complexity and time) |
SConstruct
Outdated
| 'python': 'py', | ||
| 'ruby': 'rb', | ||
| 'rust': 'rs', | ||
| 'smalltalk': 'st', |
There was a problem hiding this comment.
There are Smalltalk compilers. Do we really want to require an interpreter?
|
Right I think I got mixed up with the code verification stuff. Thanks for the clear-up! |
Adds most of the interpreted languages to SCons. Their source files are simply copied to the build directory. The languages added are:
Viml might be a typo and supposed to be vim.
I've left matlab out as it currently isn't able to run in the Docker container and I don't know how it runs.
Scratch doesn't seem to have consistent files, as such I have left it out for now. It's common enough (6 uses) that we should work out how we are managing this.
Piet is made up of .png files and are in a directory so won't be noticed by SCons. Only euclidean formula has been written (drawn?) in Piet, so this isn't major.
Whitespace is also in directories and won't be noticed by SCons, but once again is only for euclidean formula.
I haven't checked that interpreters for these are in the Docker image, although I think that most of them are.