We’ll already look in the CFLAGS/LDFLAGS when passed. -- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED) On Mar 9, 2014, at 11:41 PM, Terry Barnum <terry@digital-outpost.com> wrote:
*using macports*.
Would it be possible to modify configure.in so that it doesn't fail if homebrew's openssl isn't present but instead uses the CFLAGS and LDFLAGS passed to it?
On the production Macs I manage, I personally find macports to be a simple and reliable package manager. Ports are self-contained and self-reliant in /opt/local and aren't affected by Apple updates. I might be wrong but I'd think that for a machine running freeswitch, stability is a primary concern and using another package manager that instead relies on OS components that Apple can and does change without warning would make it fragile.
For other Mac users who aren't already using a package manager and don't know the process to use macports, it's a simple download of the small binary installer <http://www.macports.org/install.php>, install XCode and the command line tools from Apple and then 'sudo port install <port name>'
There's a very active and responsive community and as of 2014-03-09 at 21:00:26 America/Los_Angeles, there are 18,237 ports.
-Terry