daniel
November 12, 2019, 9:39am
8
Yes, chiming in with a link I wished for a while ago, I would love to see two command line parameters, that lets the command line interface override the default file location of the global settings:
Projucer --settings myCIprojucer.settings --resave myProject.jucer
Projucer --ignore-global-settings --resave myProject.jucer
The second one would be synonymous of supplying an empty file.
While this fixes one particular case, would you consider adding a flag like
Projucer --settings MyProjucerSettings.settings
Projucer --ignore-global-settings
which allows to create build scripts on CI, that are independent from the world outside.
And you don’t need to delete the global settings file at each CI run, like suggested in another thread…
EDIT: just turned that into a feature request
Could there be two options added to the projucer commandline to override the global settings file with a separate one or by using no global settings at all?
This would be very useful for self contained projects, build scripts etc. especially on continuous integrations.
Projucer --settings myCIprojucer.settings --resave myProject.jucer
Projucer --ignore-global-settings --resave myProject.jucer
The second one would be synonymous of supplying an empty file.
And you don’t need to delete the glob…