Updated Xcode project for macOS #72
Conversation
add missing sources switch to a modern toolchain - LLVM Clang amd64 i386 libc++ - use tbd over dylib - no fixed SKD but always deploy for 10.10+ automate the dependency build mechanism - wxWidgets 3.0 (with the flag to fix the build in Sierra) - CryptoPP (always from the git master) - pUPnP 1.6 (you will need external autoconf, automake, libtool) - Boost ASIO sockets (currently broken)
|
As a general guide, we should support building on the widest range of OSes possible. That is, if your updated XCode project supports only 10.10, we need another way to build on older versions.
I would really appreciate if you could update them. However, by updating I mean fixing bugs and library references, but they should still work on older OSX versions.
I know someone on the forum was using it, I made some fixes to the packager script which I forgot to include in the release. You can find them here.
It would be nice to have these under platforms/MacOSX, if there isn't a strict requirement to have these files in the root (like with the debian folder). |
|
I'm currently testing the windows side, but after that, I'll try MacOS. Maybe just using cmake will make the xcode projects obsolete, too. |
|
As 10.10 is the oldest version I can even start on virtualbox, and the last update of this version is from 2015, I don't see it necessary to support older versions. Hell it's older than oldstable debian. And the most recent statistic I've found from late 2018 stated that 2.57% of the users is using something older than 10.10 So from my site, I'm fine for now. |
I don't know what's your stand on
Actually they are broken as well
git rm -rfto this or another pr