Well, As soon as I will be at home at my desk, I could try what you say, Arkadiusz.
I continue to be surprised anchor about the necessity to do this change you speak about, since as I told, I always used the same procedure so far. If you compiled the source in your Linux, could you be so kind to show up the cmake sequence you used to build and to install the wsjtx binary into the target directory? TKS, best regards, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Arkadiusz Miśkiewicz via wsjt-devel <[email protected]> Sent: Thursday, September 18, 2025 9:26:38 AM To: [email protected] <[email protected]> Cc: Arkadiusz Miśkiewicz <[email protected]> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 On 18/09/2025 14:10, Marco Calistri via wsjt-devel wrote: > But this would be the very first time I had to do that way, Arkadiusz! > > Till version 2.7.0, I always used the same building script, which always > succeeded! > > Now such script stopped to work due to the new cmake release (4.1.1) > installed onto my Opensuse Tumbleweed. wsjtx source tarballs are packaged in really crazy way where main CMakeLists.txt unpacks actual source tarballs etc - indeed that could break with newer cmake. Anyway the real source is in src/wsjtx.tgz, so best is to use it directly and thus ignore wsjtx cmake unpacking hacks. > Regards, > > Inviato da Outlook per Android <https://aka.ms/AAb9ysg> -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
