New assessment of this problem...

Xcode 7.2.1 is getting mixed up between the header files in /usr/include and 
those in /opt/local/include, and I can no longer build.

My commandline OS X project uses the most recent version of OpenCV installed in 
/opt/local. The problem is that OpenCV requires a newer version of ncurses than 
is in the OS X 10.11 SDK. So, system-wide there are two versions of ncurses: 
V5.7 installed in /usr/include, and V6.0 installed in /opt/local/include.

My Xcode header search paths setting:

HEADER_SEARCH_PATHS = $(inherited) /opt/local/include/opencv 
/opt/local/include/opencv2 /opt/local/include

It seems /usr/include is hardcoded somewhere in Xcode, because Xcode begins its 
parsing by loading up the *old* version of ncurses first:

In file included from 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/ncurses.h:141:

But when that ncurses.h does an #include <curses.h>, it seems to be loading up 
the *new* version, /opt/local/include/curses.h, which is incompatible, and 
generates a multitude of errors. 

How can I get Xcode to use the newer version installed in /opt/local/include, 
and not the older one in /usr/include?
-Carl


> On Jan 14, 2016, at 12:26 PM, Jens Alfke <j...@mooseyard.com> wrote:
> 
> Looks like you’ve got a header named unctrl.h in /opt/local/include that is 
> in the compiler’s header search path before the SDK header paths, so when the 
> standard ncurses.h includes unctrl.h it gets your local one instead of the 
> standard one. And then it appears that your local one is not compatible — 
> when I look at that header in the Mac OS SDK, there is no declaration like 
> the one quoted above.
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to