The attached file loads stuff for a plethora of apps that I use, not
just wsjt-x.
Lately I've been checking new verions of Fedora Rawhide every several days.
Gnuradio, wspr, wsjt-x, are part of my test suite for new Linux builds.
On 03/06/2014 02:22 PM, Bill Somerville wrote:
Hi Chuck,
tried replying to you off list but your mail server bounced my message.
a couple of suggestions:
I got wsjtx 3842 running on Fedora Rawhide with the following procedure.
1. Install needed software and libraries. The attached file
downloads the lot.
All you should need for a build are the following packages:
svn
cmake
gcc (4.8.x preferred)
gfortran (again 4.8.x preferred)
binutils
Qt5
Qt5Multimedia
Hamlib-1.2.15.3
fftw-3 (single precision libfftwf-3)
pulseaudio and its prerequisites
If you are on a 64-it Linux machine then you will need 32-bit libc and
compiler support for kvasd. On Debian base systems this is obtained by
installing the libgfortran:i686 package, Fedora repos will have the same
or your distro will have them installed by default, YMMV.
2. svn co svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx
3. cd to the wsjtx directory
I find it best to keep build and source directories completely separate.
Changing things in the build tree will potentially break future builds.
If you are worried about space usage then do:
cmake --build . --target clean
after the install target has been built and tested.
4. make a bin subdirectory, cd to it, cmake .., make (same procedure
used for gnuradio)
a better name for the build directory is 'build' or better still
'build/release' if you plan to make debug builds which would then go to
'build/debug'
Running from the build directory is not recommended. The CMake script
attempts to gather all the required files for a runnable installation
using the 'install' target. With CMake you set the install location by
setting the CMAKE_INSTALL_PREFIX variable at configure time.
I am aware that the install target is not yet complete, more to come
soon, but it is a lot better than building a runnable tree by hand.
By doing this you keep source, build and, run trees completely separate.
For example:
mkdir -p ~/build/wsjtx/release
cd ~/build/wsjtx/release
cmake -D CMAKE_INSTALL_PREFIX=~/test-install/wsjtx/release
<path-to-source-directory>
cmake --build . --target install -- -j
a runnable result will be placed in ~/test-install/wsjtx/release/bin
If you are developing or updating the source then only the last command
needs repeating for a new build.
for a debug build:
mkdir -p ~/build/wsjtx/debug
cd ~/build/wsjtx/debug
cmake -D CMAKE_INSTALL_PREFIX=~/test-install/wsjtx/debug -D
CMAKE_BUILD_TYPE=Debug <path-to-source-directory>
cmake --build . --target install -- -j
a runnable and debuggable result will be placed in
~/test-install/wsjtx/debug/bin
5. link jt9 in bin/lib to bin directory
The install target handles this.
6. copy the Pallettes tree to the bin directory: find Pal*|cpio -pmdvl
bin
This too is done by the install target.
7. copy kvasd to the bin directory
This too is done by the install target.
8. set symbolic links to the log files
9. Run wsjtx, poke around until the correct sound card is discovered,
et al.
73
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
--
Chuck Forsberg WA7KGX [email protected] www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
