external target, paths, and error reporting
external target, paths, and error reporting
- Subject: external target, paths, and error reporting
- From: Stephan Gehring <email@hidden>
- Date: Wed, 1 Dec 2004 21:59:07 -0800
Hi,
I am trying to build a cross-platform project on a remote unix box. I
created a local xcode project, added the remote source files (samba
mounted) to the project and defined an external target (with ssh
remotely activating the build tool).
The build executes properly and reports errors back in the build
results window. However, if I click on a error in the build results
window, it does not jump to the corresponding line in the source file.
I have tracked the problem down to a path problem but have been unable
to solve it so any help is appreciated!
The remote system reports errors with a path relative to the root of
the project, such as:
path/file.cpp:40: `x' undeclared (first use of this function)
If instead, the error were reported with an absolute path as
/Volumes/projectpath/path/file.cpp:40: `x' undeclared (first use of
this function)
Xcode would be able to locate the corresponding file [I verified this
by sending back fake error messages with an absolute path]
I've tried a bunch of things in xcode and suspect there is a simple
setting I have to do to make this work, but haven't been successful so
far.
Any help appreciated
Thanks, Stephan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden