You have several options to set up variables from outside your makefile: From environment – each environment variable is transformed into a makefile variable with the same name and value. You may also want to set -e option (aka –environments-override) on, and your environment variables will override assignments made into makefile (unless these assignments themselves … Read more
Just like any other simple command, [ … ] or test requires spaces between its arguments. if [ “$#” -ne 1 ]; then echo “Illegal number of parameters” fi Or if test “$#” -ne 1; then echo “Illegal number of parameters” fi Suggestions When in Bash, prefer using [[ ]] instead as it doesn’t do … Read more
I think a more canonical way to do this is via: command –feature and command –no-feature argparse supports this version nicely: Python 3.9+: parser.add_argument(‘–feature’, action=argparse.BooleanOptionalAction) Python < 3.9: parser.add_argument(‘–feature’, action=’store_true’) parser.add_argument(‘–no-feature’, dest=”feature”, action=’store_false’) parser.set_defaults(feature=True) Of course, if you really want the –arg <True|False> version, you could pass ast.literal_eval as the “type”, or a user defined … Read more
Use “$@” instead of plain $@ if you actually wish your parameters to be passed the same. Observe: $ cat no_quotes.sh #!/bin/bash echo_args.sh $@ $ cat quotes.sh #!/bin/bash echo_args.sh “$@” $ cat echo_args.sh #!/bin/bash echo Received: $1 echo Received: $2 echo Received: $3 echo Received: $4 $ ./no_quotes.sh first second Received: first Received: second Received: … Read more
You can specify formal arguments in rake by adding symbol arguments to the task call. For example: require ‘rake’ task :my_task, [:arg1, :arg2] do |t, args| puts “Args were: #{args} of class #{args.class}” puts “arg1 was: ‘#{args[:arg1]}’ of class #{args[:arg1].class}” puts “arg2 was: ‘#{args[:arg2]}’ of class #{args[:arg2].class}” end task :invoke_my_task do Rake.application.invoke_task(“my_task[1, 2]”) end # … Read more
Standard Method (no library) The arguments are stored in process.argv Here are the node docs on handling command line args: process.argv is an array containing the command line arguments. The first element will be ‘node’, the second element will be the name of the JavaScript file. The next elements will be any additional command line … Read more