Revisiting an older mail (every 12 months I guess I take the time to look at 
this)

I spent a bit of time this afternoon making my shallow fork of freeswitch 
compile, run and be able to load modules. Most importantly I've been spending 
the time to excise the internal dependencies and build against 'real ports' and 
base versions of thingies (like sqlite) instead of the bizarre bastardized 
kitchen sink style of dependencies in the upstream tree.

https://github.com/tbullock/freeswitch-openbsd

Some status:

- Somewhat older in tree version compared to upstream, but whatevs... don't be 
picky.
- Builds on -current with external dependencies instead of the built-ins
- Doesn't use the absurd upstream build script, just needs make as provided by 
base.
- Starts/doesn't segfault
- Loads modules (mod_console loads and does things successfully)
- Needs to be killed from outside (internal quit command isn't loaded just yet)
- Doesn't actually make telephone calls yet (again, whatevs... don't be picky)

Build instructions:

Run -current, don't be a scrub.

1. Checkout from git
2. Install relevant ports, see the readme. I think the names for some have 
changed since I last updated the readme but you should get the point.
3. make && sudo make install
4. Manually copy the ridiculous example configuration to /etc/freeswitch (I 
left a copy in the conf directory)
5. I called the binary 'fsd'. Run that. It should be installed to 
/usr/local/bin/fsd

If there is interest from 'out there', I am happy to keep working on this 
(until I get bored or a plastic bag floats by and distracts me).

-- 
Ted Bullock 
Scrublord

-----Original Message-----
From: Ted Bullock 
Sent: November 22, 2013 5:21 PM
To: 'Chris Cappuccio'; James Turner
Cc: [email protected]; Sergey Bronnikov
Subject: RE: Freeswitch

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

Reply via email to