I obtained pulled into a type of conversations the place I find yourself saying, “Wonderful, I’ll put up a submit about it” and that is the submit. Sure, you can check and run command-line apps instantly from Xcode however I just about by no means do. It’s a ache with few advantages. That mentioned, right here’s the way you do it.
Arguments
Let’s say you want arguments. Open your scheme (⌘<) and choose the Run > Arguments tab. Add the arguments you need to go on launch one after the other. Double-click to edit any argument:
The arguments are vended byCommandLine.arguments. Both depend the array or use CommandLine.argc to learn the way many arguments you’re coping with.
print(CommandLine.arguments) print(CommandLine.argc)
Counter-intuitively, Xcode doesn’t routinely quote the arguments for you. This produces 5 arguments, not three, or six in the event you embody the command itself:
["/Users/ericasadun/Library/Developer/Xcode/DerivedData/Test-gwehknnihlcsiucsovtbnlrdtfun/Build/Products/Debug/Test", "first", "second", "third", "fourth", "fifth"] 6
And what do you anticipate from the next?
You get this in the event you run instantly in Xcode’s console:
["/Users/ericasadun/Library/Developer/Xcode/DerivedData/Test-gwehknnihlcsiucsovtbnlrdtfun/Build/Products/Debug/Test", "first", "several items at once", "third"] 4 Program ended with exit code: 0
However in the event you set your code to execute utilizing Terminal:
Launching: '/Customers/ericasadun/Library/Developer/Xcode/DerivedData/Check-gwehknnihlcsiucsovtbnlrdtfun/Construct/Merchandise/Debug/Check' Working listing: '/Customers/ericasadun/Library/Developer/Xcode/DerivedData/Check-gwehknnihlcsiucsovtbnlrdtfun/Construct/Merchandise/Debug' 3 arguments: argv[0] = '/Customers/ericasadun/Library/Developer/Xcode/DerivedData/Check-gwehknnihlcsiucsovtbnlrdtfun/Construct/Merchandise/Debug/Check' argv[1] = 'first' argv[2] = 'a number of' ["/Users/ericasadun/Library/Developer/Xcode/DerivedData/Test-gwehknnihlcsiucsovtbnlrdtfun/Build/Products/Debug/Test", "first", "several"] 3
Xcode’s Loopy Terminal Possibility
When you’re working something with direct key enter (utilizing POSIX termios/uncooked mode) or curses, working within the console doesn’t work. So Xcode offers a solution to run these utilities within the terminal. Go to Run > Choices and scroll all the best way down.
This function is buggy as hell, produces ridiculous quantities of extra textual content (see this), can take a big time to launch, and much more time for Xcode to appreciate the method has completed. It’s not possible to make use of with paths that use areas (“warning: working listing does not exist: '/Volumes/Kiku/Xcode/Derived'“).
I don’t prefer it. I don’t use it. However it exists.
Sane Command-Line Execution
Except you’re coping with issues like automation and such, you possibly can check out your compiled command-line apps by dragging your executable from the Merchandise group onto the terminal. This locations the trail to your construct on the immediate. Sort out your arguments and press return:
Nevertheless, I favor to make use of a Copy File construct part. Choose your Goal > Construct Phases, click on plus (+) and add the executable. (I take advantage of absolute path and disable “solely when putting in”.) This allows you to set up on to commonplace areas like /usr/native/bin or ~/bin, or in the event you don’t need to place it there till it’s steady and prepared for deployment, you need to use a growth folder:
Assuming your vacation spot is in your shell’s path, begin a brand new shell for the executable to be picked up the primary time. After that, you possibly can compile and run as you want.
