search

tpoechtrager / osxcross

Mac OS X cross toolchain for Linux, FreeBSD, OpenBSD and Android (Termux)
GNU General Public License v2.0
2.85k stars 320 forks source link

Default to targeting the maximum supported macOS version #300

Open mcandre opened 2 years ago

mcandre commented 2 years ago

Could osxcross default to targeting the maximum supported macOS version? I think that could more closely match the behavior of Xcode. For example, C++17 support for standard features like std::filesystem::path should work out of the box.

I recognize that such a change would influence how backwards compatibility works. If a developer wishes to support older macOS versions, perhaps that could be implemented more explicitly, rather than relying on the compiler to default to legacy editions.

tpoechtrager commented 2 years ago

What does uname -a && echo "int main(){}"|xcrun clang -xc -v - print on your macOS system?

HinTak commented 2 years ago

I disagree. If somebody is bothered enough to do cross-compiling, he/she likely wants to support the widest outcome, ie the oldest macOS x version supported by the combination of sdk headers and compiler.

IanCollins commented 2 years ago

"If somebody is bothered enough to do cross-compiling, he/she likely wants to support the widest outcome" Some of us have to cross-compile and being restricted to older language versions is a major headache when the code base is cross-platform. The minimum supported version should be configurable.