You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to be a problem with paths. Gcc outputs relative paths with errors and warnings, because files were specified with relative paths in the compiler command line. Xcode therefore does not know where to search for the file.
The text was updated successfully, but these errors were encountered:
Pretty funny to find that almost 10 years later.
I'm commenting since there are not many references on the internet regarding this (surprise!).
The issue is that Xcode wants GCC to report errors with an absolute file path.
That does the trick.
I'm noch using CrossPack, but a simple self-made project, since I have specifically setup makefiles that should also run without Xcode as my project requires.
This seems to be a problem with paths. Gcc outputs relative paths with errors and warnings, because files were specified with relative paths in the compiler command line. Xcode therefore does not know where to search for the file.
The text was updated successfully, but these errors were encountered: