Re: [wsjt-devel] How to set up for WSJT-X development?

2020-01-21 Thread Bill Somerville

On 21/01/2020 09:43, Alessandro Gorobey via wsjt-devel wrote:

please see https://sourceforge.net/p/wsjt/mailman/message/36884654/
Can be as my problem that Bill solve with the patch ?


Hi Sandro,

Paul's issue was with a broken Hamlib installation. We are not sure how 
but an old version was being used by the WSJT-X build. After some 
tidying of old Hamlib builds his build proceeded. I did pass on that 
patch and some suggestions to reduce build times by skipping unneeded 
documentation build steps. He now has a clean build on Linux.


73
Bill
G4WJS.



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


Re: [wsjt-devel] How to set up for WSJT-X development?

2020-01-21 Thread Alessandro Gorobey via wsjt-devel

Hi Paul, Bill,


Il 20/01/2020 21:23, Bill Somerville ha scritto:

On 20/01/2020 20:05, Paul Kube wrote:


$ mkdir -p ~/wsjtx-prefix/build
$ cd ~/wsjtx-prefix
$ git clone git://git.code.sf.net/p/wsjt/wsjtx
 src
$ cd ~/wsjtx-prefix/build
$ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix ../src
$ cmake --build .
$ cmake --build . --target install


The next to last line, cmake --build ., dies with those unresolved 
symbols in HamlibTransceiver.cpp. I've taken care not to have any 
other hamlib packages installed on this machine. So it seems to me 
that something in git://git.code.sf.net/u/bsomervi/hamlib 
 or 
git://git.code.sf.net/p/wsjt/wsjtx 
 is wrong.


73, Paul K6PO


Hi Paul,

something is amiss for sure. Can you reply with the file 
~/wsjtx-prefix/build/CMakeCache.txt please? You should probably send 
that to me direct rather than via the list.


73
Bill
G4WJS.


please see https://sourceforge.net/p/wsjt/mailman/message/36884654/
Can be as my problem that Bill solve with the patch ?

--
73
Sandro
IW3RAB


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


Re: [wsjt-devel] How to set up for WSJT-X development?

2020-01-20 Thread Bill Somerville

On 20/01/2020 20:05, Paul Kube wrote:


$ mkdir -p ~/wsjtx-prefix/build
$ cd ~/wsjtx-prefix
$ git clone git://git.code.sf.net/p/wsjt/wsjtx
 src
$ cd ~/wsjtx-prefix/build
$ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix ../src
$ cmake --build .
$ cmake --build . --target install


The next to last line, cmake --build ., dies with those unresolved 
symbols in HamlibTransceiver.cpp. I've taken care not to have any 
other hamlib packages installed on this machine. So it seems to me 
that something in  git://git.code.sf.net/u/bsomervi/hamlib 
 
or  git://git.code.sf.net/p/wsjt/wsjtx 
 is wrong.


73, Paul K6PO


Hi Paul,

something is amiss for sure. Can you reply with the file 
~/wsjtx-prefix/build/CMakeCache.txt please? You should probably send 
that to me direct rather than via the list.


73
Bill
G4WJS.

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


Re: [wsjt-devel] How to set up for WSJT-X development?

2020-01-20 Thread Paul Kube
Hi Bill --



On Mon, Jan 20, 2020 at 8:53 AM Bill Somerville 
wrote:

> You could use the tarball as a starting point for casual development but
> cloning the official public git repository is best for anything other than
> the simplest of development.
>

Sounds good to me, I'd like to get that working.

> The errors you show above are due to you not having a recent version of
> Hamlib built for use with WSJT-X, the versions of Hamlib in most (probably
> all) Linux repositiories are too old. You should be able to clone the
> official Hamlib git repo and build the master branch for use with WSJT-X.
> You should configure the Hamlib build to build a static library and its
> probably best to install that locally in your own directories using the
> --prefix option of configure. Once you have a locally installed Hamlib you
> can tell the WSJT-X CMake build script where to find it using the
> configuration variable CMAKE_PREFIX_PATH which should include the root
> directory of your locally install Hamlib package.
>
Bill, I did all that. As I said, I followed your
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/INSTALL. To wit:

$ mkdir ~/hamlib-prefix
> $ cd ~/hamlib-prefix
> $ git clone git://git.code.sf.net/u/bsomervi/hamlib src
> $ cd src
> $ git checkout integration
> $ ./bootstrap
> $ mkdir ../build
> $ cd ../build
> $ ../src/configure --prefix=$HOME/hamlib-prefix \
>--disable-shared --enable-static \
>--without-cxx-binding --disable-winradio \
>CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \
>LDFLAGS="-Wl,--gc-sections"
> $ make
> $ make install-strip
> $ mkdir -p ~/wsjtx-prefix/build
> $ cd ~/wsjtx-prefix
> $ git clone git://git.code.sf.net/p/wsjt/wsjtx src
> $ cd ~/wsjtx-prefix/build
> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix ../src
> $ cmake --build .
> $ cmake --build . --target install


The next to last line, cmake --build ., dies with those unresolved symbols
in HamlibTransceiver.cpp. I've taken care not to have any other hamlib
packages installed on this machine. So it seems to me that something
in  git://git.code.sf.net/u/bsomervi/hamlib or  git://
git.code.sf.net/p/wsjt/wsjtx is wrong.

73, Paul K6PO
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] How to set up for WSJT-X development?

2020-01-20 Thread Bill Somerville

On 20/01/2020 08:24, Paul Kube wrote:
A simple question: Suppose I want to do a little WSJT-X development... 
experimenting with new features, bug fixing, submitting the occasional 
patch. I'll be coding on Linux, but will want to compile for Windows 
as well as Linux for testing. (Not particularly interested in building 
my own source tarball.) What's the best way to do this now?


I can build from 
https://sourceforge.net/projects/wsjt/files/wsjtx-2.1.2/wsjtx-2.1.2.tgz 
 just 
fine; but I've seen email saying the repository has moved to git, so 
I'm not sure that tarball is up to date. On the other hand, following 
the git-centric instructions at 
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/INSTALL, the 
build dies with errors like:


wsjtx-prefix/src/HamlibTransceiver.cpp:590:66: error: 
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
           rig_set_mode (rig_.data (), RIG_VFO_CURR, dummy_mode_, 
RIG_PASSBAND_NOCHANGE);


wsjtx-prefix/src/HamlibTransceiver.cpp:811:32: error: 
‘rig_set_split_freq_mode’ was not declared in this scope
                   error_check (rig_set_split_freq_mode (rig_.data (), 
RIG_VFO_CURR, tx, new_mode, RIG_PASSBAND_NOCHANGE), tr ("setting split 
TX frequency and mode"));



Hi Paul,

building on MS Windows is considerably more complicated than on Linux 
due to the lack of sensible third-party package management on that 
platform, if you are comfortable with working from a Linux terminal 
command line then that is probably your best choice for WSJT-X 
development. You only need install git and a program editor of your 
choice over and above the prerequisites for building WSJT-X and Hamlib 
from the official release tarball. You could use the tarball as a 
starting point for casual development but cloning the official public 
git repository is best for anything other than the simplest of development.


The errors you show above are due to you not having a recent version of 
Hamlib built for use with WSJT-X, the versions of Hamlib in most 
(probably all) Linux repositiories are too old. You should be able to 
clone the official Hamlib git repo and build the master branch for use 
with WSJT-X. You should configure the Hamlib build to build a static 
library and its probably best to install that locally in your own 
directories using the --prefix option of configure. Once you have a 
locally installed Hamlib you can tell the WSJT-X CMake build script 
where to find it using the configuration variable CMAKE_PREFIX_PATH 
which should include the root directory of your locally install Hamlib 
package.


73
Bill
G4WJS.

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


Re: [wsjt-devel] How to set up for WSJT-X development?

2020-01-20 Thread Joe Taylor

Hi Paul,

On 1/20/2020 3:24 AM, Paul Kube L6PO wrote:
A simple question: Suppose I want to do a little WSJT-X development... 
experimenting with new features, bug fixing, submitting the occasional 
patch. I'll be coding on Linux, but will want to compile for Windows as 
well as Linux for testing. (Not particularly interested in building my 
own source tarball.)  What's the best way to do this now?


I can build from 
https://sourceforge.net/projects/wsjt/files/wsjtx-2.1.2/wsjtx-2.1.2.tgz 
 just 
fine; but I've seen email saying the repository has moved to git, so I'm 
not sure that tarball is up to date. 


All new revisions of WSJT-X include a tarball including the code from 
which they were built.  The tarball posted at the SourceForge link you 
quote (and also on the WSJT web site here
http://physics.princeton.edu/pulsar/k1jt/wsjtx-2.1.2.tgz ) is, indeed, 
the latest source code that has been released.


In the past, experimental and developmental code that might (or might 
not) become part of a future release was also made publicly available. 
This led to significant problems: for example, another developer copying 
our work in progress and releasing it before it was finished.


You may confidently treat the published tarball as the latest 
source-code release.


-- 73, Joe, K1JT


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


[wsjt-devel] How to set up for WSJT-X development?

2020-01-20 Thread Paul Kube
A simple question: Suppose I want to do a little WSJT-X development...
experimenting with new features, bug fixing, submitting the occasional
patch. I'll be coding on Linux, but will want to compile for Windows as
well as Linux for testing. (Not particularly interested in building my own
source tarball.)  What's the best way to do this now?

I can build from
https://sourceforge.net/projects/wsjt/files/wsjtx-2.1.2/wsjtx-2.1.2.tgz

just
fine; but I've seen email saying the repository has moved to git, so I'm
not sure that tarball is up to date. On the other hand, following the
git-centric instructions at
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/INSTALL, the build dies
with errors like:

wsjtx-prefix/src/HamlibTransceiver.cpp:590:66: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
   rig_set_mode (rig_.data (), RIG_VFO_CURR, dummy_mode_,
RIG_PASSBAND_NOCHANGE);

wsjtx-prefix/src/HamlibTransceiver.cpp:811:32: error:
‘rig_set_split_freq_mode’ was not declared in this scope
   error_check (rig_set_split_freq_mode (rig_.data (),
RIG_VFO_CURR, tx, new_mode, RIG_PASSBAND_NOCHANGE), tr ("setting split TX
frequency and mode"));

[BTW: Attempting to answer my question with a web search turns up the
promising looking WSJT Developers Guide
https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/dev-guide-main.html,
but that begins with a notice that it's obsolete, and to use
https://sourceforge.net/projects/jtsdk/ instead. OK fine, I go there, and
from there to https://sourceforge.net/projects/jtsdk/files/linux/ for the
Linux version, which page tells me the repository has been moved to github
at https://github.com/KI7MT/jtsdk-nix. There I see the announcement that
"This project is no longer under active development", "Those wishing to use
JTSDK should follow the JTSDK .Net Core cross-patform project instead."
Right, OK, but the page https://github.com/KI7MT/jtsdk-tools for that
project only says "Linux - Coming Soon!" A dead end.]

Thanks for any help,

73, Paul K6PO
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel