This is exactly what I do to build GIMP. It’s not easy and sometimes things fight against you. In order to lead a comfortable life, you should link against the 11 sdk as well. Otherwise it’s up to you to detect which sdk at runtime and gracefully degrade. This is possible for your own code but not going to work for most libraries. I think python does it but not much else that’s cross platform.
If you want to see how GIMP is doing it, it’s all available at https://gitlab.gnome.org/Infrastructure/gimp-macos-build On Sat, 19 Aug 2023 at 16:50, André-John Mas <andrejohn....@gmail.com> wrote: > I haven’t done this myself, but guessing it is easier to have macOS 11 > installed and do your work there. > > My fear of targeting macOS 11 from macOS 13 is that you get the false > security that things worked. > > André-John > > Sent from my phone. Envoyé depuis mon téléphone. > > > On 19 Aug 2023, at 10:11, Andreas Falkenhahn <andr...@falkenhahn.com> > wrote: > > > > Hi, > > > > I've installed MacPorts on a macOS 13 system but I'd like to build > programs > > that run on all systems that have at least macOS 11. That's why I run gcc > > with the -mmacosx-version-min=11.0 argument. This, however, leads to > warnings > > of the following kind during linking: > > > > ld: warning: dylib (/opt/local/lib/libfreetype.dylib) was built for > newer macOS version (13.0) than being linked (11.0) > > ...more similar warnings for other dylibs installed by MacPorts... > > > > Is there any way to install the dylibs for macOS 11.0 on a macOS 13 > system > > or how am I supposed to build MacPorts programs on macOS 13 that run on > older > > macOS versions as well? > > > > -- > > Best regards, > > Andreas Falkenhahn mailto: > andr...@falkenhahn.com > > >
