How to use Xcode Tools with a Command Line Project

Question

Level 1

9 points

How to use Xcode Tools with a Command Line Project

I'm using Xcode 3.2.6, C compiler. I've had an application for years that is command-line on the terminal, compiling with a makefile. Now I want to actually use the performance tools included with Xcode, such as threads, time profiler, etc. How do I do this?

I created a project for it (never did that before), added source files, etc -- it seems to work. It created the application, which will run via the terminal like always. But whenver I try to use Run (inside Xcode), a window opens up saying "Stop Executable". I have to click OK and that's the end of it. Nothing has happened.

I found an old query on the web similar to this from 2008. The suggestion was to open the console. Still nothing. "Sync with Debugger" does no good. Please help!

PowerMac, OS X Mountain Lion (10.8.2)

Posted on May 28, 2014 8:29 AM

Reply

Answer 1

K T

Level 7

23,877 points

May 28, 2014 8:39 AM in response to rhhlewis

AFAIK, Xcode 3.2.6 is not suppored on 10.8.2.

Suggest you upgrade....Xcode 5.1.1 is latest

Reply

Answer 2

rhhlewis Author

Level 1

9 points

May 28, 2014 9:09 AM in response to K T

Thanks for answering. Certainly 3.2.6 has worked fine for what I've done up to now. Are you saying that there is some subtle problem with Run, consolde etc, so I should ugrade to 5.1?

Before I go to that trouble, I'd like to get an answer to my original question.

Reply

Answer 3

May 29, 2014 12:13 PM in response to rhhlewis

What type of project did you create? Without this information, no one will be able to help you.

You have two options to create a command-line app. The first option is to create an external build system project. You should use this option if you're using a makefile to build the project. The advantage of the external build system project is you can use your makefile to build the project. The downside of the external build system project is limited support for running the app inside Xcode, which is what you may be experiencing.

The second option is to create a command-line tool project. With a command-line tool project, you use Xcode instead of a makefile to build the project. But Xcode has better support for running your app inside Xcode if you use a command-line tool app.

What's more important to you: using a makefile or running your app in Xcode? If using a makefile is more important, create an external build system project and accept Xcode's limitations when running and debugging external build system projects. If running your app in Xcode is more important, create a command-line tool project.

Reply

Answer 4

May 29, 2014 1:17 PM in response to rhhlewis

When you run a command line tool in Xcode the console is shown at the bottom of the Xcode window

If that is not showing click

located at the top right of the Xcode widow to open it.

Message was edited by: Frank Caggiano - This is for Xcode 5 on Mavericks. It has been a long time since I ran 3 so I'm not 100% sure it was the same.

Reply

Answer 5

rhhlewis Author

Level 1

9 points

May 29, 2014 3:37 PM in response to Mark Szymczyk

It is an external system with a make file. I used the same makefile I have been using for years.

I was not aware of the second option, as an Xcode tool. Thanks for the info. Sounds the old days with MPW. I will look into it.

Reply

Answer 6

rhhlewis Author

Level 1

9 points

May 29, 2014 3:39 PM in response to Frank Caggiano

It's not a command-line tool. It's an external build system project. But thanks.

Reply

Answer 7

May 29, 2014 3:43 PM in response to rhhlewis

But whenver I try to use Run (inside Xcode), a window opens up saying "Stop Executable". I have to click OK and that's the end of it. Nothing has happened.

Looked like you were trying to run it in Xcode.

Reply

Answer 8

rhhlewis Author

Level 1

9 points

May 29, 2014 3:47 PM in response to Frank Caggiano

Yes I am. I'm trying to use the Xcode Run Performance Tools, especially to look at how the threads are working that I just added to the system.

Reply

Answer 9

May 29, 2014 3:49 PM in response to rhhlewis

If you're running it in Xcode then you will need to use Xcode's console window to interact with it.

Reply

Answer 10

rhhlewis Author

Level 1

9 points

May 29, 2014 3:56 PM in response to Frank Caggiano

That I understood. I did try Run > Console. Nothing intelligible happened. Then I synced with the debugger. he program is called fer64. I get this:

No executable file specified.

Use the "file" or "exec-file" command.

No executable file specified.

Use the "file" or "exec-file" command.

The program being debugged is not being run.

Not executing.

(gdb) r fer64

Data Formatters temporarily unavailable, will re-try after a 'continue'. (Unknown error loading shared library "/Developer/Applications/Xcode.app/Contents/PlugIns/GDBMIDebugging.xcplugin/Con tents/Resources/PBGDBIntrospectionSupport.A.dylib")

Starting program: fer64

Not executing.

Reply

Answer 11

May 29, 2014 4:40 PM in response to rhhlewis

Ah that's right Xcode 3 did things a lot differently. Sorry as I said it's been a while since I ran 3 and my memory of it is fuzzy.

While upgrading to 5 probably won't fix your problem it will get you better support, you're not going to find to many people still running 3. At least if you were using 5 we'd be talking the same language 😀

good luck

regards

Reply

Answer 12

rhhlewis Author

Level 1

9 points

May 29, 2014 5:20 PM in response to Frank Caggiano

Thanks for the advice.

Reply