When does Meson decide to use a response file? #13235
Replies: 2 comments 3 replies
-
I don't think this behaviour is documented. Nor is it anything more special than "use rsp files if the line is too long and we know the compiler supports it". This is problematic to support automatically, since some tools support rsp files and others don't. You also might need to do different quoting with the rsp files as they are nonstandard and so on. I guess a kwarg like |
Beta Was this translation helpful? Give feedback.
-
I did two attempts to allow the use of response files in custom_targets: #12272 and #11822. I'd be happy to rebase and finish one or the other, if I have somebody to review and merge it... |
Beta Was this translation helpful? Give feedback.
-
I am maintaining a project where we depend a lot on the specific ordering of files as an input to a particular tool for, e.g., bytecode generation, archive packing, etc. We currently are passing upwards of 500 files as command line arguments to our tools for these processes. Given the structure of our file tree, we worry about running into command line argument limits in the future.
To that end:
One solution that we have thought about to this problem is generating an input file for passage to our tools, ideally from a static list of files in the
meson.build
file. My solution to that was something like this:But this feels like it will still run into the command line argument limit in the future. Is there a similar procedure that Meson supports which would circumvent that limit?
Beta Was this translation helpful? Give feedback.
All reactions