Re: CFBundleSupportedPlatforms issue

Thanks for all the help everyone. I’m still struggling here though. The binaries in my project are pre-compiled, so they are just under Resources. They are not targets and they are not being compiled in different projects. I thought -sectcreate was just a command-line tool but this seems to

Re: CFBundleSupportedPlatforms issue

> On Oct 7, 2015, at 4:42 PM, Rick C. wrote: > > Thanks for the help but there is only one OS X Deployment Target for my > entire app not one for each included binary. I really don’t see a place to > change any settings for the binaries? In the targets that build those binaries. Which might

Re: CFBundleSupportedPlatforms issue

Thanks for the help but there is only one OS X Deployment Target for my entire app not one for each included binary. I really don’t see a place to change any settings for the binaries? > On 7 Oct 2015, at 2:24 PM, Charles Srstka wrote: > >> On Oct 5, 2015, at 2:40 AM, Rick C. >

Re: CFBundleSupportedPlatforms issue

> On Oct 5, 2015, at 2:40 AM, Rick C. wrote: > > Couldn't find platform family in Info.plist CFBundleSupportedPlatforms or > Mach-O LC_VERSION_MIN for myBinary Actually reading this again, before you bother with the Info.plist suggestion I just sent, why don’t you check “OS X Deployment Target

Re: CFBundleSupportedPlatforms issue

> On Oct 5, 2015, at 2:40 AM, Rick C. wrote: > > I have 3 pre-complied binaries inside of my project. They do have their own > entitlements files and they are codesigned but they do not have their own > Info.plist. What happens if you give them one? You can embed an Info.plist inside a Mach-O

Re: CFBundleSupportedPlatforms issue

> Am 07.10.2015 um 13:34 schrieb Rick C. : > > Thanks for the help. But how would this work in the future at some point I > will need to use the latest SDK right? Sorry, I’m not an experienced XCoder … I do 4D usually ;-) Anyway, my guess would be, that the precompiled binaries you are using