nim-lang / csources_v2

CSources compiled from Nim version 2.

csources_v2

CSources compiled from Nim version 2. Based on https://github.com/nim-lang/Nim/commit/7f6681b4c4ccc0dc43fd256280be4c3ad3c773e5

csources_v2's Issues

Why aren't these repositories simply tags?

I maintain the script which builds docker containers of Nim given a version number. It would be much easier to grab the correct version of csources if they where simply kept in a single repository and tagged with which version to use for each Nim version. So e.g. there would be a series of tags for the v1 series pointing to the csources_v1 code, and now a new tag for the v2.0.0 release pointing to a commit with this code. Then to build version X of Nim it would be as simple as grabbing the csources repository at the tag X. The current system is prone to breaking and I constantly have to modify to keep up with various inconsistencies..

The linker command, for windows, is exceeding the maximum character length

I don't know if it's the final version, but if it is, it will be necessary to correct the names of the C files generated for windows. At the moment the command that calls the linker has almost 9000 characters, which exceeds the Windows limit of 8191. This is due to the stdlib file names being like this: @m..@[email protected]@stoolchains@snim-@hdevel[...]

For the other destinations the names are also like this.