On 14.5.2023 18.15, Jim Shorney via wsjt-devel wrote:
Thanks Kari. That sounds like a viable option. Can you tell me how you did 
that? I'm not a code warrior. I am an old DOS/Windows guy. I can follow good 
instructions and do some logical troubleshooting but I'm not well versed in 
making the compiler do cool tricks. :)

73

-Jim
NU0C

Hi Jim,

I'm no code warrior either and this 'cmake' utility
goes well above my head and totally confuses me.

Maybe there is some 'magic swithc' that could be flipped
to exclude stuff from the build, but I'm not aware
if any such swithc exists or not.

So, after a good deal of head scratching and foul language
I finally came up with this:

1) Locate file 'CMakeLists.txt' in the source root directory
2) Edit that file and comment out line 1436

3) Save file and compile as usual

Now it is is that easy if you compile with the 'git clone' -method.

However, if you are using the 'wsjtx-2.7.0-rc1.tgz' tarball,
things get a bit tricky because you need to make the
change to 'CMakeLists.txt' that is packed inside the
'wsjtx.tgz' archive. This is how that goes:

1) Install 'archivemount' utility if not installed already
2) Since you have alredy tried to compile, you already have 'wsjtx.tgz' in some 
directory
3) Change to that directory: cd </path/to/your/compile>/wsjtx-2.7.0/src
4) Create a temporary directory: mkdir edit
5) Mount the tgz: archivemount wsjtx.tgz edit
6) Use good old vi editor and comment out line 1436: vi 
edit/wsjtx/CMakeLists.txt
7) Save the file, then unmount directory: sudo umount edit
8) Calculate md5sum for the modified archive: md5sum wsjtx.tgz
9) Update the new sum to file wsjtx.tgz.md5sum: vi wsjtx.tgz.md5sum

10) Compile as usual

Phew! Sure hope someone comes up with an easier procedure than that..

If these do not work for you, feel free to contact me off list.

73's de Kari, oh2gqc


On Sun, 14 May 2023 12:29:46 +0300
Kari Sillanmäki via wsjt-devel<wsjt-devel@lists.sourceforge.net>  wrote:

Hi Jim,

I encountered the same problem in my Ubuntu 18.04 system.

Since it's only the new "qmap" program that causes this issue, I
compiled WSJT-X without qmap.

I don't have any use for qmap anyway.

This way I can postpone the inevitable OS upgrade to some later time...

73's de Kari, oh2gqc

_______________________________________________
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