I am having trouble with includes & macros written in C. I would like to see how the proprocessor code expands.
I am using xtool 2.x. It's old, so I'll take whatever generic help you may offer.
I would like the preprocessor/compiler to generate the preprocess output and continue with the complile.
Robert
When you say xtool, do you mean Xcode? I don't have access to Xcode 2, but in Xcode 3 you can choose Build > Preprocess to generate the preprocessor output. I would assume Xcode had a similar menu item, but the Build menu might have a different name, such as Run or Project.
xcode. I got that confused :-(
Seems to have the options, but it is greyed out. Do I need to change some setting?
Robert
It appeared all of a sudden. !!!
click build>preprocessor
screen flashes by but where is the output?
I read about cpp Guess I'll have to figure it out.
Try opening the build results window. Your screenshot shows how to access it. The editor at the bottom of the build results window should show the output.
I am a rank beginner at using xcode & programming in C. I can edit .h & .c files just fine. I didn't see any new files in the folder when I did it earlier. This is what I got:
Xcode is not going to create a new file in your project folder with the preprocessed output. Try selecting a .c file from the Groups and Files list before choosing Build > Preprocess. When I do this with a C++ file, I get preprocessed output where it says No Editor in your screenshot. I also get preprocessed output in the editor that is attached to the project window. If you don't see the editor, drag the separator at the bottom of the project window to show the editor.
That worked! Thanks.
For what it is worth, I had to select the .c file in the middle of the screen.
Thanks for your presistance.
--------------------------------------------------------------
I found some open source code that I'm in the process of updating. First, I got to understand it.
I was getting errors on the macro generation which motivated me in asking the question. The macro output without Macro names that look like function names helps me sort out the code. This provides another angle on the code. ( I know do a global search. )
Another quaint thing is the code doesn't have any comments ... well it does have the open source declarations. Pointer use is rampant. The three part if in the middle of a print statement is a little surprising to me. cpp does a nice job of formating the print statement which I can follow.
And I rather code in python.
Robert
show C preprocessor output
