Uh yeah, It depends on your goal. If the goal is to make it compile and run as built from upstream then yes, bashing the upstream stuff together can make it work and it will live in its own little world.
If the goal is to have an actual port, then the upstream build process is just crazy. Here is a list of some of the dependencies it duplicates: aprutil-1 apr-1 curl idn pcre srtp speex speexdsp iconv intl natpmp miniupnpc spandsp I keep having to make actual money doing other stuff and get distracted from my little fs on openbsd project but the direction I was going is the right one in my opinion. -----Original Message----- From: Chris Cappuccio [mailto:[email protected]] Sent: November 22, 2013 5:10 PM To: James Turner Cc: [email protected]; Sergey Bronnikov; Ted Bullock Subject: Re: Freeswitch James Turner [[email protected]] wrote: > On Fri, Nov 22, 2013 at 03:50:25PM -0800, Chris Cappuccio wrote: > > Does Freeswitch compile and run on OpenBSD? I thought it was already > > done, but just noticed it isn't in the official ports tree yet. > > > > There seems to be a port in openbsd-wip [0]. > > [0] > https://github.com/jasperla/openbsd-wip/tree/master/telephony/freeswit > ch > I noticed that and also this: https://github.com/tbullock/freeswitch-openbsd http://tbullock.comlore.com/2013/03/freeswitch-on-openbsd.html Seems to me that the SQLite problem is resolved by simply using the freeswitch version of it. Chris
