Xcode where is the executable

Either count the array or use CommandLine. Counter-intuitively, Xcode does not automatically quote the arguments for you. This produces five arguments, not three, or six if you include the command itself:. So Xcode provides a way to run those utilities in the terminal. Since you can change Xcode4's default build location preferences or right-click on the product and choose "Show in Finder" K T 's correct answer what difference does it make? Because it's buried.

And then I just spent another hour trying to figure out how to get a release build. How do you get one of those? They used to be there next to the release, created by default. In XCode 4, you choose "archive". What the heck! You may want to start your own thread to it can receive the unique attention it deserves and you can track easier, close if solved, etc. Just to build on K T's informative response, here's a step-by-step maybe obvious for Mac experts but I'm an old Linux guy In Project Navigator click the "file" icon at top left of Xcode window so that tree of files and folders are visible :.

Open the Products folder. Find the executable, which has the file name assigned in the project settings and a Terminal icon. Feb 18, AM. Feb 18, AM in response to blisterpeanuts In response to blisterpeanuts. Feb 18, AM in response to etresoft In response to etresoft. I've tried Archive, and it creates a new folder every time you run it, with a new timestamp.

I think the purpose of Archive is to archive, i. That's fine, but it's not what the OP asked for. Feb 18, PM in response to blisterpeanuts In response to blisterpeanuts. The short script would clone, build, and execute your package as a separate entity caching it of course.

But for users already familiar with the package manager, all you really have to do is make it obvious that you vend the tool as a Swift package. They will then be able to figure out countless ways of integrating it into their workflow just the way they want. They may use the package manager directly, or they may use some third party tool that further simplifies the process in some way there are many such tools and scripts out in the wild.

This is possible since executable targets in a package always build for macOS. Add the executable product from the package in the target dependency build phase. Then you should be able to find that executable in the built products directory using the available environment variables. This is not something I have tried with Xcode 11 yet. Where does Xcode save the program's executable files or equivalent files? Ask Question.

Asked 8 years, 11 months ago. Active 8 years, 11 months ago. Viewed 13k times. Improve this question. DrummerB 39k 12 12 gold badges silver badges bronze badges. Add a comment. Active Oldest Votes. Improve this answer.