-
Notifications
You must be signed in to change notification settings - Fork 106
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
fpm fails at building projects with too many files #991
Comments
Windows has a hard limit of 32767 characters per command line that cannot be avoided. Instead, I think it would be viable to change the linking procedure according to the GCC guideline:
This would be suitable for all compilers and platforms. |
That looks like a good and quite simple idea to implement |
Are you sure the GCC toolchain doesn't support response files (the thread you linked is from 2009)? It appears in the man page: https://man7.org/linux/man-pages/man1/gcc.1.html The full entry in the
The NAG Fortran Compiler also has this option:
Also wanted to note that Ninja also uses response files on Windows for this purpose: https://ninja-build.org/manual.html (search for "rspfile") |
Description
The original issue appeared when building the project feq-parse with the following configuration
The test project has a quite large number of files (170), which results in a very long command line for the final linking. On Windows, command lines are limited in size and the present build exceeds the limit. This has been tested with
cmd
,msys2
andpowershell
without any difference.FWIW, Visual Studio creates temporary files (e.g. "RSP1.rsp") with the content of the command line and ifort is invoked as
ifort @".\RSP1.rsp
Expected Behaviour
The project should build on Windows without having to split the files to 2 or more subprojects.
Version of fpm
0.10.0, alpha
Platform and Architecture
Windows 10
Additional Information
The end of the build log is:
The text was updated successfully, but these errors were encountered: