It's not really an SDK issue but a minimum target system. Even recent SDKs allow for building for 10.7, BUT (and this is the big but), some frameworks, etc are deprecated when using these newer SDKs (ie: newer Xcodes). Plus, each SDK use a different version of clang, which also factors in. And finally, you have older versions of the C++ lib to worry about (this was a major change with 10.8 -> 10.9 targets)...
So simply saying "use the latest SDK" implies a lack of understanding of the complexities in building such a complex beast for macOS platforms, esp when one considers that 4.20.x contains updated and upgraded code that breaks things as well and how each OS target version and each SDK and each version of Xcode all mangles together. And the real issue in this regards is about our complimentary community provided builds not about building it "in general"... > On Jan 8, 2019, at 11:38 AM, [email protected] wrote: > > I am not sure what you mean. > We should update to use the latest SDK. > According to Apple it is still posible to build for 10.7 with it. > Maybe that would be better approach? > > I think you have also to look into available flags since there is a lot of > change in the last 10 years in compiler terms. > See mechtildes post and my older post to build on Arch linux. > So you might well run into different issues with the approach. > > Maybe also posting the issued might help. Maybe they are not that bad. > > I am sorry that the mac buildbot isnt ready. I could use some help there. > If anyone has time. > We currently need to define the brew commands in order to install all the > tools we need. Then we can try to build. And the result is public. Which > would make it easy for others to check on their work. > > Am Dienstag, 8. Januar 2019 schrieb Jim Jagielski: >> One option we have is that we drop support for macOS 10.7 and older for >> 4.20.x... this MIGHT help. >> >> I can/will test that assumption. >> >>> On Jan 8, 2019, at 9:54 AM, Jim Jagielski <[email protected]> wrote: >>> >>> I've started playing around w/ getting 4.2.0-HEAD to build; as expected, so >>> real issues w/ Ubuntu or CentOS7 but macOS is causing problems, what with >>> the migration to gbuild for various modules and how these migrations >>> constantly break macOS. I'll try to start hammering fixing/working-around >>> these, but my recommendation would be that instead of migrating to gbuild >>> willy-nilly, we only do so on (1) modules that NEED it, due to new versions >>> or (2) are so easy and basic that the risk that it breaks other platforms >>> is pretty much nil. >>> >>> Does that make sense? >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > -- > Gesendet von meinem Sailfish-Gerät. > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
