Skip to content
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

Add more languages to the build system #906

Open
18 of 45 tasks
Amaras opened this issue Oct 26, 2021 · 6 comments
Open
18 of 45 tasks

Add more languages to the build system #906

Amaras opened this issue Oct 26, 2021 · 6 comments
Labels
General Hacktoberfest The label for all Hacktoberfest related things! SCons For SCons-related matters

Comments

@Amaras
Copy link
Member

Amaras commented Oct 26, 2021

Feature Request

Add more language builders to the SCons-based build system.

Description

Since #885 was merged, we now have a build system that aims to provide a compilation framework for every compiled language. However, most of the work is currently not done yet.

Here are all the current languages in the AAA (in alphabetical order of the directory names). Each of the languages needs either a way to compile an executable in the build/ directory at the project root, copy the interpreted file to the correct folder, or prove that it is impossible to do.

If you want to provide compilation instructions, please follow the example provided in #885: a builder per language which has the name of the language which each leaf SConscript uses, and the list of the language's folders added to the language list in the root SConstruct file.

Additional context

Related to #870.
Don't hesitate to reach out to me (@Amaras on GitHub, and .amaras on Discord, formerly Amaras#8643) if you have questions.

@Amaras Amaras added General Hacktoberfest The label for all Hacktoberfest related things! labels Oct 26, 2021
@Amaras Amaras self-assigned this Oct 26, 2021
@Amaras Amaras removed their assignment Oct 26, 2021
@ShadowMitia
Copy link
Contributor

Most languages will add temporary files for build, .o are generated for C, but should we just add the minimal amount of files added by a scons build?
Or should we just add the whole list like the one generated by gitignore.io?

@Amaras
Copy link
Member Author

Amaras commented Nov 3, 2021

I think we only need to add the minimal amount of things to the .gitignore.
Right now, only the .o are annoyingly not in the correct directory, so I don't see any reason to add any other files.
I'm open to discussion, of course :)

@ShadowMitia
Copy link
Contributor

I don't really have a strong opinion on this^^
The other idea was to make sure everything is built out of the content directory.

@Amaras
Copy link
Member Author

Amaras commented Nov 3, 2021

Well there's a way to do that, but it adds complexity to the scripts

@Beliavsky
Copy link

The gfortran compiler is part of the Gnu Compiler Collection and works like the C compiler gcc. So

gfortran -o prog func.f90 main.f90

will produce executable prog. Are there obstacles to adding Fortran codes?

@ShadowMitia
Copy link
Contributor

@Beliavsky No obstacles to adding Fortran code, this is about adding an automated system to compile all the examples in the Archive.

@ntindle ntindle pinned this issue Nov 8, 2021
@Amaras Amaras added the SCons For SCons-related matters label Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
General Hacktoberfest The label for all Hacktoberfest related things! SCons For SCons-related matters
Projects
None yet
Development

No branches or pull requests

3 participants