I think that if you want to build on a generic Mac with Xcode, you need to
include all the libraries in the sources and have them build as part of the
project.
Bill
> On 19 Mar 2016, at 5:14 AM, Carl Hoefs wrote:
>
> Thanks for the very interesting info and
Have you set the “User Header Search Paths” with /opt/local/… and the “Always
search user paths” build settings? These set up the user header search paths
which get searched before any system paths, and the “Always search user paths”
essentially puts the user header search paths in front of
Xcode is designed to build projects for multiple OS architectures on multiple
processor types. So it does not use the host system headers and libraries,
because for many purposes like building TVOS apps they are inappropriate.
Welcome to the rabbit hole world of cross compilation.
This magic
Thanks for the very interesting info and idea. I might well be able to jury-rig
my project to get it to build my way on my Mac, but in the end the Xcode
project will have to be buildable on a generic Mac, so I'm bound by whatever
version of code Apple has included in their SDK. For the moment
That’s interesting! Works for me. I use updated libraries all the time.
Jonathan
> On Mar 18, 2016, at 6:25 PM, Carl Hoefs
> wrote:
>
> No change. The “Always search user paths” build setting seems to be a no-op.
> It still chokes parsing
No change. The “Always search user paths” build setting seems to be a no-op. It
still chokes parsing ../MacOSX10.11.sdk/usr/include/.. stuff, without
/usr/include specified anywhere.
-Carl
> On Mar 18, 2016, at 12:04 PM, Jonathan Prescott
> wrote:
>
> Have you set the