Rick, K9AO, sent some detailed instructions for building SVXlink, an open source Echolink client, under Linux, and we're including it in it's entirety here. As you may recall from episode 56, Russ had problems with compiling the program.Hi Russ,
I thought I'd send along the method that I have used to successfully build SVXlink under Mandriva 2010.2 and Ubuntu 10.10. I built the source on Ubuntu 10.10 late last year, so don't have access to that machine at the moment. I built SVXlink from the latest SVN checkout on this Mandriva box, but this method also works fine for the release tarball.
I don't know if you generally use SVN projects, but I'm thinking that you likely do if you are as interested in helping to shape the development of actively developed projects.
I create a directory called SVN in my home directory, and then do the SVN checkouts from there. Using the SVN checkout command below will create a subdirectory in the folder that you run it in, and then you can do the install from there. You likely are already familiar with this.
Here are the specifics:
--------------------
Get the source:
svn co https://svxlink.svn.sourceforge.net/svnroot/svxlink svxlink
cd to the below directory:
Build the source branch in /svxlink/trunk/src
From there:
make realclean
make
su to root
make install
--------------------
If there are any missing deps, these will show up as the compile progresses. As you already know I am sure, you need the devel packages to match the deps to build from source.
You will see errors, or what looks like errors as the build progresses after a realclean command. But if all of the needed libs and devels are there, the build process will create the necessary configs and then build the app. If you are concerned that the app might not have built correctly, doing another make will have the terminal scroll through the build process rapidly and then complete. If you get that far, do the root install. Then qtel from the terminal will bring up the client.
There are a number of branches of the source code for SVXlink in development. I recommend the above main trunk first.
There haven't been any changes in the Qtel client for a while, so if all you are after is the client part of SVXlink there is no advantage to using cutting-edge SVN. There has been quite a bit of development going on in the server part, so experimenting with the SVN and joining the SVXlink devel list might be a good idea.
Hope that helps, and keep up the good work.
Rick, K9AO