Hi Tom,

In addition to what Bill has provided, and by Ubuntu LTE I am assuming 
you mean Ubuntu LTS (14.04), you can also use JTSDK for Nix.

Install Instructions can be found here (add the PPA and install):
https://launchpad.net/~ki7mt/+archive/ubuntu/jtsdk

The menu driven / canned build scripts are fairly generic, meaning, as a 
developer you may need / want to manually compile via the command line 
to enable / disable options, however, installing JTSDK will ensure you 
have all the needed development packages, and provide an easy method of 
building Hamlib3.

Using JTSDK, all the source, build and install locations are under one 
directory tree: ~/jtsdk/{src,hamlib3,wsjtx,wspr,wsjt, etc etc}. Each SVN 
revision is build and installed in it's own revision folder to allow 
testing against current and previous builds, for example:

~/jtsdk/wsjtx/1.6.0/{5950,5960,5970}
~/jtsdk/wsjtx/1.6.1/{5950,5960,5970}

The same is true for the WSJTX EXP branch, WSPR and WSJT. Compiling 
manually, of course, you can select whatever you like for SRC, Build and 
Install locations.

I test JTSDK for Nix on Ubuntu, Lubuntu, Xubuntu for versions 14.04, 
14.04, 15.10 and when 16.04 starts up, will add that as well.


73's
Greg, KI7MT

On 10/15/2015 17:03, Bill Somerville wrote:
> On 15/10/2015 23:47, Tomek wrote:
>> Hi!
> Hi Tom,
>>
>> My name is Tom, SQ5RIX, QTH Warsaw Poland
>>
>> I tried to comppile the latest version, unfortunately I stumbled upon an
>> error I cannot resolve:
>>
>> tom@A300:~/tmp/wsjtx$ cmake .
>> -- Building wsjtx-1.6.0-devel
>> -- ******************************************************
>> -- Building for for: Linux-x86_64
>> -- ******************************************************
>> -- Found hamlib
>> -- hamlib_INCLUDE_DIRS: /usr/local/include
>> -- hamlib_LIBRARY: /usr/local/lib/libhamlib.a
>> -- hamlib_LIBRARIES: /usr/local/lib/libhamlib.a;m;dl
>> -- hamlib_STATIC_LIBRARY: /usr/local/lib/libhamlib.a
>> -- hamlib_STATIC_LIBRARIES: /usr/local/lib/libhamlib.a;m;dl
>> CMake Error at CMakeLists.txt:735 (find_package):
>>      By not providing "FindQt5Multimedia.cmake" in CMAKE_MODULE_PATH this
>>      project has asked CMake to find a package configuration file provided by
>>      "Qt5Multimedia", but CMake did not find one.
>>
>>      Could not find a package configuration file provided by "Qt5Multimedia"
>>      (requested version 5) with any of the following names:
>>
>>        Qt5MultimediaConfig.cmake
>>        qt5multimedia-config.cmake
>>
>>      Add the installation prefix of "Qt5Multimedia" to CMAKE_PREFIX_PATH
>> or set
>>      "Qt5Multimedia_DIR" to a directory containing one of the above files.  
>> If
>>      "Qt5Multimedia" provides a separate development package or SDK, be
>> sure it
>>      has been installed.
>>
>>
>> -- Configuring incomplete, errors occurred!
>>
>> Could you please direct me how to get over it?
> Please review the instructions here:
>
> http://sourceforge.net/p/wsjt/wsjt/HEAD/tree/branches/wsjtx/INSTALL
>
> Ubuntu splits up the Qt development libraries, you will need to install
> the Qt Multimedia and SerialPort development packages. It also looks
> like you have not built my fork of Hamlib 3, without that you are
> unlikely to get a fully working Hamlib rig control functionality.
>>
>> I am on Ubuntu LTE...
>>
>> tom@A300:~/tmp/wsjtx$ uname -a
>> Linux A300 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015
>> x86_64 x86_64 x86_64 GNU/Linux
>>
>> I was able to compile wsprx latest development version. I have installed
>> Qt5 development files...
>>
>> 73 Tom
> 73
> Bill
> G4WJS.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to