- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 359
Scons compilation examples #863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hum... I think I branched off a PR branch... I'll try to get it correct later or reopen the PR branching off The point still stands, as there should not be a problem with that (especially since the SCons PR should be merged after the C++ flood fill one) |
Are we doing it this way as opposed to @stormofice 's implementation |
This is one way to do it. I'm not sure if it's the best way. |
Does SCons work with every language? Regardless of that, I don't see why this would interfere with the verifier, as better compilation/running instructions would just simplify the language configuration files. |
Out of the box, SCons works with C/C++, Fortran, D, TeX/LaTeX, Java, some Assembler languages, and some other languages. We'd probably need to provide Builders to ensure consistent compilation for Rust, Scala, etc. |
I think this is fine and if it makes things easier for @stormofice, then let's do it! I will say that we probably don't need the flood fill example in this PR, though |
Yeah, I'm not exactly sure how to remove the flood fill thingy, properly :/ |
4435203
to
597adc8
Compare
I'm not sure if I removed the previous branch commits properly, but it should be okay. |
Because we chose to go with the single |
This PR aims to provide examples on how to create compilation (and run) instructions with SCons, as per #691.
As this is currently the only effort to provide concrete examples of compilation instructions, I highly encourage others to open their own draft PRs with their own compilation instructions, until we decide what system to use.
I'd like to give the systems a fair comparison, so try to provide them for the same chapter(s) as I did (in other words, please don't get too ahead of me.)
Below is a basic instruction manual for the Barnsley Fern chapter
How to use (e.g. create the
out.dat
orbarnsley.dat
file)scons out.dat
orscons barnsley.dat
(depending on the implementation)scons -c .
to remove all the intermediate and final files.Note: if you want to only clean the
out.dat
file and keep the executables/classes (and so on) files, you can runscons -c out.dat