Casing causes 'More than one build script specified.' message
See original GitHub issueI switched from windows (ps1) to mac (sh), and noticed that using commands such as -T
or -Target
on the shell script it causes the following issue More than one build script specified
. After a while I noticed it was just a casing issue -t
worked just fine. Is there anyway to get some better notification or just to ignore casing for this?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:13 (5 by maintainers)
Top Results From Across the Web
cakebuild - Pass multiple parameters/arguments to target
I am going to assume that you are using the latest bootstrapper file, which is available from here:.
Read more >Build Scripts - The Cargo Book
By default Cargo looks up for "build.rs" file in a package root (even if you do not specify a value for build )....
Read more >Cake v1.0.0 released
#1690 Casing causes 'More than one build script specified.' message. Bug. #3077 Regression: rc0003 outputs extra characters on OSX. #3072 ...
Read more >Build Script Basics
This chapter introduces you to the basics of writing Gradle build scripts. It uses toy examples to explain basic functionality of Gradle, which...
Read more >Common Build Problems
One possible cause for builds failing unexpectedly can be calling set -e (also known as set errexit ), either directly in your .travis.yml...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Able to reproduce this on
MacOS 10.14 (18A391)
with:Also tried
-t
,-target
,-T
,-Target
,--Target
, but they don’t work.Edit:
Had to use
=
like:I think part of the problem is the documentation is not clear, especially when running a Bash script as opposed to PowerShell. The doc page about running targets gives these examples:
./build.ps1 -Target Publish
./build.ps1 --target Publish --exclusive
If the tool is going to claim to be cross-platform like it does on the home page then the documentation should be cross-platform as well.