One thing we've noticed is that Pd builds on my machine running 10.13 don't seems to work on 10.6-10.7 systems, so the deployment target is really a suggestion at best. You'll have to do some testing but it's hard to hit *everyone* and honestly the vast majority of users fall within the newest to maybe 3 versions before anyway (ie. 10.10 - 10.13 now).
For plain C/C++, you can have a relatively old deployment target. It's really more important for macOS app development using the Apple frameworks ie. stuff like the changes from QT to AVFoundation, etc.
The compiler builds for the current system by default. You have to set the min deployment target when building.
Add this flag to you makefile: --mmacosx-version-min=10.6
The current version for Pd is 10.6 which is the first version that supported i386 (ie. Intel processors).
From: Miller Puckette <msp@ucsd.edu>To: Alex <x37v.alex@gmail.com>Cc: pd-dev <pd-dev@lists.iem.at>Subject: Re: [PD-dev] Mac SDK version for externalsMessage-ID: <20180319015755.GY7620@elroy.localdomain>Content-Type: text/plain; charset=us-asciiThis is a very interesting and useful question.At the outset of PD I only worried about having it run on the "current"platforms: Redhat 5.2, Windows 95, and when it arrived, MacOS 10.2. Olderplatforms weren't important.Since then I've tried to keep back compatibility to whatever those bleeding-edgeOSes were, because I assume people can't always afford machine upgrades. ButI haven't tried to extend Pd (Or "extra" objects) backward past the originaldates.At the moment I can only compile back to OSX 10.5 (PPC) and Windows XP; Idon't have real or virtual machines that go back further.So my suggestion would be: make it work on today's OSes, and try to keep italive on them, but don't worry too hard about older ones. I don't think I'mever going to be tempted to compile Pd for Windows 3.1.cheersMiller