Re: Error and Warning verbosity in XCode/Gcc
Re: Error and Warning verbosity in XCode/Gcc
- Subject: Re: Error and Warning verbosity in XCode/Gcc
- From: Markus Hitter <email@hidden>
- Date: Tue, 23 Mar 2004 16:20:50 +0100
Am 23.03.2004 um 15:17 schrieb Motti Shneor:
2. Errors and Warning messages are *VERY* undescriptive (in comparison
with CodeWarrior compiler) and worse, they seem to be cut in the
middle many times.
Well, they are what gcc spits out. Perhaps it will take some time until
you are used to the "language" of gcc messages.
Double-clicking the messages to open them doesn't help.
Double-clicking the message should make you jump to the corresponding
source line.
The message strings are indeed cut.
Single-click (mark) it in the Detailed Build Results window, then drag
the split view up to see the full gcc message. The split view is all
down initially.
This is surely something which can be improved. Xcode seems to filter
out the message fine, just it isn't helpful to cut them off just to
make them fit into some particular view.
a matter of GCC verbosity flag? what flag?
There are a lot of flags, see man gcc or the Target Inspector/Build
panel. Each flag has a description there.
3. I have a small unix-standard-tool target I need to build and run as
a part of my build process. However I'm completely unfamiliar with
command line and shell scripts. The tool is a simple unix pipe that
converts some text file into a C header file needed for later stage.
It is run usually like this ".\conv <Text.txt > myHeader.h
That's a more tricky thing. A carefully positioned Shell Script Build
Phase shoud do it.
A. I cannot make the target place its executable tool in the right
directory (where the text file and header file are located).
There's no need to put the tool into a specific directory; ./conv
</path/to/Text.txt >/otherpath/to/myHeader.h should do it as well.
Setting the Installation path or a Copy Build Phase should help you to
get your tool into a specific directory. See Xcode's Build Settings
Release Notes (help menu) for a big bunch of variables which might be
helpful.
B I don't know how to establish the build-stage (is it a shell
script?) to run my tool as a preliminary part of my bigger FramerWork
build.
Again, you probably want a Shell Script Build Phase.
In the Target Info window / build settings there is a place to set up
"Installation Path". What is it used for,
This is where the final product is installed, relative to $(DSTROOT).
and when?
When doing a deployment build.
My builds always end up in the project/build directory. Am i missing
something?
You are doing a development build. Should be fine to run the tool from
there.
HTH,
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.