Menu
▾
▴
wsjt-devel — WSJT software development
You can subscribe to this list here.
| 2007 |
Jan
(30) |
Feb
|
Mar
(10) |
Apr
(60) |
May
(62) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(10) |
Oct
(17) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(21) |
Mar
(4) |
Apr
(15) |
May
(37) |
Jun
(98) |
Jul
(120) |
Aug
(1) |
Sep
(14) |
Oct
|
Nov
(31) |
Dec
(8) |
| 2009 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(25) |
May
(88) |
Jun
(5) |
Jul
(31) |
Aug
(25) |
Sep
(4) |
Oct
(19) |
Nov
(119) |
Dec
(11) |
| 2010 |
Jan
(3) |
Feb
(19) |
Mar
(4) |
Apr
|
May
(7) |
Jun
(17) |
Jul
|
Aug
(4) |
Sep
(20) |
Oct
(3) |
Nov
(29) |
Dec
(86) |
| 2011 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(9) |
Aug
(4) |
Sep
(7) |
Oct
(9) |
Nov
|
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(5) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(10) |
Feb
(7) |
Mar
(4) |
Apr
(76) |
May
(66) |
Jun
(101) |
Jul
(210) |
Aug
(255) |
Sep
(83) |
Oct
(18) |
Nov
(3) |
Dec
(3) |
| 2014 |
Jan
(187) |
Feb
(139) |
Mar
(99) |
Apr
(173) |
May
(106) |
Jun
(61) |
Jul
(50) |
Aug
(66) |
Sep
(342) |
Oct
(238) |
Nov
(251) |
Dec
(189) |
| 2015 |
Jan
(96) |
Feb
(295) |
Mar
(260) |
Apr
(271) |
May
(358) |
Jun
(531) |
Jul
(311) |
Aug
(231) |
Sep
(267) |
Oct
(219) |
Nov
(452) |
Dec
(390) |
| 2016 |
Jan
(367) |
Feb
(128) |
Mar
(208) |
Apr
(308) |
May
(237) |
Jun
(272) |
Jul
(90) |
Aug
(289) |
Sep
(153) |
Oct
(214) |
Nov
(167) |
Dec
(282) |
| 2017 |
Jan
(194) |
Feb
(173) |
Mar
(267) |
Apr
(102) |
May
(39) |
Jun
(201) |
Jul
(1064) |
Aug
(363) |
Sep
(383) |
Oct
(289) |
Nov
(237) |
Dec
(185) |
| 2018 |
Jan
(175) |
Feb
(198) |
Mar
(489) |
Apr
(222) |
May
(414) |
Jun
(297) |
Jul
(329) |
Aug
(136) |
Sep
(383) |
Oct
(590) |
Nov
(834) |
Dec
(1114) |
| 2019 |
Jan
(425) |
Feb
(177) |
Mar
(319) |
Apr
(515) |
May
(337) |
Jun
(447) |
Jul
(525) |
Aug
(252) |
Sep
(119) |
Oct
(108) |
Nov
(211) |
Dec
(228) |
| 2020 |
Jan
(158) |
Feb
(141) |
Mar
(94) |
Apr
(99) |
May
(545) |
Jun
(470) |
Jul
(211) |
Aug
(142) |
Sep
(181) |
Oct
(128) |
Nov
(219) |
Dec
(213) |
| 2021 |
Jan
(243) |
Feb
(514) |
Mar
(279) |
Apr
(101) |
May
(97) |
Jun
(259) |
Jul
(164) |
Aug
(205) |
Sep
(149) |
Oct
(301) |
Nov
(139) |
Dec
(159) |
| 2022 |
Jan
(116) |
Feb
(70) |
Mar
(63) |
Apr
(46) |
May
(50) |
Jun
(114) |
Jul
(173) |
Aug
(106) |
Sep
(127) |
Oct
(65) |
Nov
(117) |
Dec
(102) |
| 2023 |
Jan
(139) |
Feb
(99) |
Mar
(52) |
Apr
(132) |
May
(238) |
Jun
(75) |
Jul
(91) |
Aug
(25) |
Sep
(36) |
Oct
(64) |
Nov
(45) |
Dec
(91) |
| 2024 |
Jan
(156) |
Feb
(56) |
Mar
(30) |
Apr
(16) |
May
(40) |
Jun
(53) |
Jul
(327) |
Aug
(171) |
Sep
(67) |
Oct
(53) |
Nov
(43) |
Dec
(78) |
| 2025 |
Jan
(112) |
Feb
(27) |
Mar
(46) |
Apr
(49) |
May
(58) |
Jun
(54) |
Jul
(42) |
Aug
(11) |
Sep
(92) |
Oct
(45) |
Nov
(33) |
Dec
(2) |
|
From: Joseph T. <jo...@Pr...> - 2025-09-19 21:05:07
|
Andy -- Sorry to hear that you had trouble using WSJT-X 3.0.0-rc1. You appear to be an outlier: well over 2500 people are using 3.0.0-rc1 with good results. I have been unable to reproduce your reported symptoms here. What have you already done to diagnose your problem, or to help Uwe (or any of us) to diagnose it for you? -- 73, Joe, K1JT ________________________________ From: Andy Durbin via wsjt-devel <wsj...@li...> Sent: Thursday, September 18, 2025 7:00 PM To: WSJT software development <wsj...@li...> Cc: Andy Durbin <a.d...@ms...> Subject: [wsjt-devel] v3.0.0.0 rc 1 report Installed 64 bit version on my Win 8.1 PC. This version is advertised as compatible with Win 7 and later. TS-590S with Rig OmniRig. Mode None, Split Rig. PTT CAT. (all unchanged from working 2.7.1 rc8 Improved Plus) Main window Tune did not key rig. File / Settings / Radio Test CAT - green test pass File / Settings / Radio Test CAT Test PTT - Rig keyed Close settings Click Tune - Rig keyed and modulated. Stop tune - rig remains keyed but modulation stops. Unusable. Reverted to 2.7.1 rc8 Andy, k3wyc (WSJT-X user since before release of ver 1.0) |
|
From: Bob L. <bob...@sb...> - 2025-09-19 20:16:26
|
Thank you, guys, for your support of the WSJT-X suite of signal processing programs. I am a big fan of FT8 and FT4 and my observations are based upon early use of 3.0.0-rc1. 1.None of the "Settings" windows have a scroll bar so I can't scroll to the bottom to hit "OK." 2. The font for decoded signals won't change. It is shown as a blank box at the top. When I select (one of very few choices), the box shows the size oif the font. Leaving Settings and coming back in and the font, number one did not change on teh screen for decoded signals and number 2 the Size box is again empty. "Also, why are there so few choices in font size? 3. The font for the layout changes show in the size box but seem to be lost if I close the WXJT-X application and start it again. The font defaults to the previous setting before the change. 4, The "Erase" function works backwards from the earlier versions of WSJT-X. The Band Activity window erases first then with a second click on "Erase" the RX Freq erases. This is just the opposite of all previous versions. 5. The large font and the extra line for the band buttons makes the decode windows rather skinny so that I see only 5 to 6 decodes out of a long string on active bands. 6. When I close the application and relaunch it, the "COM" port for CAT control changes to one that is not useful, so I get an error message. Note that my CODEC audio for RX and TX is on the COM port that the program seems to want to assign to the CAT control port. Don't ask me why this is happening although I now notice that same thing happening with the 2.6.1 version of the WSJT-X program. I have no idea why all of a sudden two different COM ports are assigned with, one to CAT and the other to the CODEC audios. 2.6.1 does the same thing as 3.0.0, assigning the CODEC COM port to the CAT port after a restart of the program. 7. You've probably heard of this before, but it is worth repeating: Version 2.7.0 would not allow TX Enable by double clicking on an exchange as follows: (callsign 1) RR73; (call2) (DX call) signal report. This works on version 2.6.1 but is missing with 2.7.0. It is annoying. Thank you for considering my observations. Respectfully submitted, Bob Loving K9JU Maryville, TN |
|
From: Marco C. <PY...@ou...> - 2025-09-19 02:40:46
|
Arkadiusz, Your suggestion has not worked here! In order to resolve my problem, I had to install the older cmake version to succeed with WSJTX source code compilation. /*sudo zypper in --oldpackage cmake3-3.31.8-2.8.x86_64.rpm */ IMHO it's unpleasant that a software update (in this case cmake) could broke the way we were using to do a particular thing! It should be nice if the WSJTX Dev team, could find a solution so that CMakeLists.txt, or maybe (additional source files) being compliant with newest building software as cmake. Regards, P.S. Thanks to the several OM which provided me answers about this issue! --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** Il 18/09/25 15:12, Marco Calistri via wsjt-devel ha scritto: > Thank you a lot for your time! > > I tried something similar yesterday night and I get the code was > building correctly, but then it failed when I attempted to install, > using my usual method with --target install. > > In any case, I was really tired of the too many attempts, then it's > possible I did something wrong. > > So I will try again. > > Regards, > > Inviato da Outlook per Android <https://aka.ms/AAb9ysg> > ------------------------------------------------------------------------ > *From:* Arkadiusz Miśkiewicz via wsjt-devel > <wsj...@li...> > *Sent:* Thursday, September 18, 2025 2:57:03 PM > *To:* wsj...@li... <wsj...@li...> > *Cc:* Arkadiusz Miśkiewicz <ar...@ma...> > *Subject:* Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 > On 18/09/2025 18:45, Marco Calistri via wsjt-devel wrote: > > This is the main reason, since apparently cmake 4.1.1 has changed some > > requirements. > > Looked at this: > > CMake Error at CMakeLists.txt:199 (add_custom_target): > The target name "install" is reserved or not valid for certain CMake > features, such as generator expressions, and may result in undefined > behavior. > > change > > > diff --git a/CMakeLists.txt b/CMakeLists.txt > index bc179d8..93011e2 100755 > --- a/CMakeLists.txt > +++ b/CMakeLists.txt > @@ -196,7 +196,7 @@ add_dependencies (wsjtx-package hamlib-install) > > # export traditional targets > add_custom_target (build ALL DEPENDS wsjtx-build) > -add_custom_target (install DEPENDS wsjtx-install) > +add_custom_target (pkginstall DEPENDS wsjtx-install) > add_custom_target (package DEPENDS wsjtx-package) > > and it should work with your procedure > plus -DCMAKE_POLICY_VERSION_MINIMUM=3.5 > > -- > Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) > > > _______________________________________________ |
|
From: Andy D. <a.d...@ms...> - 2025-09-19 01:33:45
|
Installed 64 bit version on my Win 8.1 PC. This version is advertised as compatible with Win 7 and later. TS-590S with Rig OmniRig. Mode None, Split Rig. PTT CAT. (all unchanged from working 2.7.1 rc8 Improved Plus) Main window Tune did not key rig. File / Settings / Radio Test CAT - green test pass File / Settings / Radio Test CAT Test PTT - Rig keyed Close settings Click Tune - Rig keyed and modulated. Stop tune - rig remains keyed but modulation stops. Unusable. Reverted to 2.7.1 rc8 Andy, k3wyc (WSJT-X user since before release of ver 1.0) |
|
From: Marco C. <PY...@ou...> - 2025-09-18 18:12:51
|
Thank you a lot for your time! I tried something similar yesterday night and I get the code was building correctly, but then it failed when I attempted to install, using my usual method with --target install. In any case, I was really tired of the too many attempts, then it's possible I did something wrong. So I will try again. Regards, Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Arkadiusz Miśkiewicz via wsjt-devel <wsj...@li...> Sent: Thursday, September 18, 2025 2:57:03 PM To: wsj...@li... <wsj...@li...> Cc: Arkadiusz Miśkiewicz <ar...@ma...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 On 18/09/2025 18:45, Marco Calistri via wsjt-devel wrote: > This is the main reason, since apparently cmake 4.1.1 has changed some > requirements. Looked at this: CMake Error at CMakeLists.txt:199 (add_custom_target): The target name "install" is reserved or not valid for certain CMake features, such as generator expressions, and may result in undefined behavior. change diff --git a/CMakeLists.txt b/CMakeLists.txt index bc179d8..93011e2 100755 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -196,7 +196,7 @@ add_dependencies (wsjtx-package hamlib-install) # export traditional targets add_custom_target (build ALL DEPENDS wsjtx-build) -add_custom_target (install DEPENDS wsjtx-install) +add_custom_target (pkginstall DEPENDS wsjtx-install) add_custom_target (package DEPENDS wsjtx-package) and it should work with your procedure plus -DCMAKE_POLICY_VERSION_MINIMUM=3.5 -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Arkadiusz M. <ar...@ma...> - 2025-09-18 17:57:18
|
On 18/09/2025 18:45, Marco Calistri via wsjt-devel wrote: > This is the main reason, since apparently cmake 4.1.1 has changed some > requirements. Looked at this: CMake Error at CMakeLists.txt:199 (add_custom_target): The target name "install" is reserved or not valid for certain CMake features, such as generator expressions, and may result in undefined behavior. change diff --git a/CMakeLists.txt b/CMakeLists.txt index bc179d8..93011e2 100755 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -196,7 +196,7 @@ add_dependencies (wsjtx-package hamlib-install) # export traditional targets add_custom_target (build ALL DEPENDS wsjtx-build) -add_custom_target (install DEPENDS wsjtx-install) +add_custom_target (pkginstall DEPENDS wsjtx-install) add_custom_target (package DEPENDS wsjtx-package) and it should work with your procedure plus -DCMAKE_POLICY_VERSION_MINIMUM=3.5 -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) |
|
From: Marco C. <PY...@ou...> - 2025-09-18 16:47:27
|
Thank you! Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Arkadiusz Miśkiewicz via wsjt-devel <wsj...@li...> Sent: Thursday, September 18, 2025 1:36:59 PM To: wsj...@li... <wsj...@li...> Cc: Arkadiusz Miśkiewicz <ar...@ma...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 On 18/09/2025 15:34, Marco Calistri via wsjt-devel wrote: > 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. That procedure will need fixes in main CMakeLists.txt to work with cmake 4.1.1. > > 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? I'm building it on macos, cmake 4.1.1 BUT I'm building only wsjtx (not bundled hamlib and wsjtx), so unpacking that src/wsjtx.tgz to src dir and mkdir build cd build sed -i -e '#CMAKE_OSX_DEPLOYMENT_TARGET#XNOT_NEEDEDX#g' src/CMakeLists.txt cmake -DCMAKE_CXX_FLAGS="-std=c++17" -DCMAKE_PREFIX_PATH="~/test/hamlib-prefix" -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_OSX_DEPLOYMENT_TARGET=15.0 ../src make -j cp -a jt9 wsjtx.app/Contents/MacOS/jt9 (last command because I run wsjtx from inside of build tree) > > TKS, best regards, > > Marco PY1ZRJ -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Marco C. <PY...@ou...> - 2025-09-18 16:46:03
|
This is the main reason, since apparently cmake 4.1.1 has changed some requirements. Tnx! Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: jarmo <oh...@ni...> Sent: Thursday, September 18, 2025 11:15:27 AM To: Marco Calistri <PY...@ou...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 Thu, 18 Sep 2025 09:09:24 +0000 Marco Calistri <PY...@ou...> kirjoitti: > Jarmo, > > Which is the cmake version on your Fedora? > > Inviato da Outlook per Android<https://aka.ms/AAb9ysg> cmake-3.31.6-2.fc42.x86_64 Jarmo |
|
From: Arkadiusz M. <ar...@ma...> - 2025-09-18 16:37:15
|
On 18/09/2025 15:34, Marco Calistri via wsjt-devel wrote: > 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. That procedure will need fixes in main CMakeLists.txt to work with cmake 4.1.1. > > 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? I'm building it on macos, cmake 4.1.1 BUT I'm building only wsjtx (not bundled hamlib and wsjtx), so unpacking that src/wsjtx.tgz to src dir and mkdir build cd build sed -i -e '#CMAKE_OSX_DEPLOYMENT_TARGET#XNOT_NEEDEDX#g' src/CMakeLists.txt cmake -DCMAKE_CXX_FLAGS="-std=c++17" -DCMAKE_PREFIX_PATH="~/test/hamlib-prefix" -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_OSX_DEPLOYMENT_TARGET=15.0 ../src make -j cp -a jt9 wsjtx.app/Contents/MacOS/jt9 (last command because I run wsjtx from inside of build tree) > > TKS, best regards, > > Marco PY1ZRJ -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) |
|
From: CLOVIS R. D. V. <py...@ya...> - 2025-09-18 14:35:22
|
Greetings, When I set 'My Call' (only this option seted) with Audio Alerts enabled, on WSJT-X 3.0 RC1, I do not receive the Alert when my call signal is called. I use different sound cards from the default for the digital modes. 73, Clovis- PY3OG |
|
From: Alex L. <al...@fo...> - 2025-09-18 14:26:53
|
If you can list out the main accessibility features you need, I can take a look at adding them. I have plenty of experience adding accessibility to Mac apps. Ultimately those additions will need to be approved by the developers but I’m sure they would welcome such changes. best, alex K6LOT > On Sep 18, 2025, at 6:29 AM, Justin Mann via wsjt-devel <wsj...@li...> wrote: > > Folks, > Can anybody tell me what Libraries are used in WSJTX to render graphics? I’d love to see how the mac version can be made more accessible. It’s almost there, but there are a couple of things that I think could be improved. I know that there is an accesible windows client that works for blind people, but it does not work with an emulator over Mac OS. WSJTX almost works, but there are a few things that need to be exposed to the UI_accessibility API that would make it even better. I’d love to assist if I can be put in touch with some one who works with this end of the project. > Thanks, > Justin-ai5os > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Marco C. <PY...@ou...> - 2025-09-18 13:34:45
|
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 <wsj...@li...> Sent: Thursday, September 18, 2025 9:26:38 AM To: wsj...@li... <wsj...@li...> Cc: Arkadiusz Miśkiewicz <ar...@ma...> 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 wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Justin M. <w9...@me...> - 2025-09-18 13:28:40
|
Folks, Can anybody tell me what Libraries are used in WSJTX to render graphics? I’d love to see how the mac version can be made more accessible. It’s almost there, but there are a couple of things that I think could be improved. I know that there is an accesible windows client that works for blind people, but it does not work with an emulator over Mac OS. WSJTX almost works, but there are a few things that need to be exposed to the UI_accessibility API that would make it even better. I’d love to assist if I can be put in touch with some one who works with this end of the project. Thanks, Justin-ai5os |
|
From: Arkadiusz M. <ar...@ma...> - 2025-09-18 12:26:52
|
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 ) |
|
From: Marco C. <PY...@ou...> - 2025-09-18 12:10:54
|
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. Regards, Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ Da: Arkadiusz Miśkiewicz via wsjt-devel <wsj...@li...> Inviato: Giovedì, Settembre 18, 2025 8:23:22 AM A: wsj...@li... <wsj...@li...> Cc: Arkadiusz Miśkiewicz <ar...@ma...> Oggetto: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 On 17/09/2025 02:58, Marco Calistri via wsjt-devel wrote: > Hello, > > I attempted to compile the new source WSJTX 3.0.0-rc1 code as always I > did so far, but now cmake is giving an error. > > This is the sequence of commands I alway launch (in this specific case I > added the POLICY_VERSION=3.5): > > tar -xzvf /home/marco/Scaricati/wsjtx-3.0.0-rc1.tgz -C /home/marco/WSJT- > X_build/build/ > cd /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/ That dir doesn't contain wsjtx sources directly. You need to unpack src/wsjtx.tgz - that's where actual source is. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Adrian <vk...@gm...> - 2025-09-18 11:30:17
|
The cmake compile working directory will show ; 73 vk4tux On 18/9/25 21:18, Arkadiusz Miśkiewicz via wsjt-devel wrote: > On 17/09/2025 02:58, Marco Calistri via wsjt-devel wrote: >> Hello, >> >> I attempted to compile the new source WSJTX 3.0.0-rc1 code as always >> I did so far, but now cmake is giving an error. >> >> This is the sequence of commands I alway launch (in this specific >> case I added the POLICY_VERSION=3.5): >> >> tar -xzvf /home/marco/Scaricati/wsjtx-3.0.0-rc1.tgz -C >> /home/marco/WSJT- X_build/build/ >> cd /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/ > > That dir doesn't contain wsjtx sources directly. You need to unpack > src/wsjtx.tgz - that's where actual source is. > |
|
From: Arkadiusz M. <ar...@ma...> - 2025-09-18 11:18:20
|
On 17/09/2025 02:58, Marco Calistri via wsjt-devel wrote: > Hello, > > I attempted to compile the new source WSJTX 3.0.0-rc1 code as always I > did so far, but now cmake is giving an error. > > This is the sequence of commands I alway launch (in this specific case I > added the POLICY_VERSION=3.5): > > tar -xzvf /home/marco/Scaricati/wsjtx-3.0.0-rc1.tgz -C /home/marco/WSJT- > X_build/build/ > cd /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/ That dir doesn't contain wsjtx sources directly. You need to unpack src/wsjtx.tgz - that's where actual source is. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) |
|
From: Marco C. <PY...@ou...> - 2025-09-18 09:09:37
|
Jarmo, Which is the cmake version on your Fedora? Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ Da: jarmo via wsjt-devel <wsj...@li...> Inviato: Giovedì, Settembre 18, 2025 12:43:17 AM A: wsj...@li... <wsj...@li...> Cc: jarmo <oh...@ni...> Oggetto: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 Wed, 17 Sep 2025 14:56:40 +0000 Marco Calistri via wsjt-devel <wsj...@li...> kirjoitti: > Good day! > > Anybody succeeded to compile WSJTX 3.0 on Linux? > > I've tried also the Uwe Enhanced version, but the cmake error has > been the same. > > May be just Windows and prepackaged Linux versions are being useable > so far...(?). > > 73, Marco PY1ZRJ > In my Fedora 42 varsion, all went smoothly and haven't noticed yet any hickups.. Jarmo, oh1mrr _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Marco C. <PY...@ou...> - 2025-09-18 09:07:53
|
With cmake version 4.1.1 it's not working, unluckily. Tried to install older cmake version without success due to required packages that I have not found. Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Marco Calistri via wsjt-devel <wsj...@li...> Sent: Thursday, September 18, 2025 1:07:59 AM To: wsj...@li... <wsj...@li...> Cc: Marco Calistri <PY...@ou...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 Good to know! Il 18/09/25 00:12, jarmo via wsjt-devel ha scritto: Wed, 17 Sep 2025 14:56:40 +0000 Marco Calistri via wsjt-devel <wsj...@li...><mailto:wsj...@li...> kirjoitti: Good day! Anybody succeeded to compile WSJTX 3.0 on Linux? I've tried also the Uwe Enhanced version, but the cmake error has been the same. May be just Windows and prepackaged Linux versions are being useable so far...(?). 73, Marco PY1ZRJ In my Fedora 42 varsion, all went smoothly and haven't noticed yet any hickups.. Jarmo, oh1mrr _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- 73 de Marco, PY1ZRJ (former IK5BCU) [cid:par...@ou...] |
|
From: Marco C. <PY...@ou...> - 2025-09-18 04:08:18
|
Good to know! Il 18/09/25 00:12, jarmo via wsjt-devel ha scritto: > Wed, 17 Sep 2025 14:56:40 +0000 > Marco Calistri via wsjt-devel<wsj...@li...> > kirjoitti: > >> Good day! >> >> Anybody succeeded to compile WSJTX 3.0 on Linux? >> >> I've tried also the Uwe Enhanced version, but the cmake error has >> been the same. >> >> May be just Windows and prepackaged Linux versions are being useable >> so far...(?). >> >> 73, Marco PY1ZRJ >> > In my Fedora 42 varsion, all went smoothly and > haven't noticed yet any hickups.. > > Jarmo, oh1mrr > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: jarmo <oh...@ni...> - 2025-09-18 03:37:54
|
Wed, 17 Sep 2025 14:56:40 +0000 Marco Calistri via wsjt-devel <wsj...@li...> kirjoitti: > Good day! > > Anybody succeeded to compile WSJTX 3.0 on Linux? > > I've tried also the Uwe Enhanced version, but the cmake error has > been the same. > > May be just Windows and prepackaged Linux versions are being useable > so far...(?). > > 73, Marco PY1ZRJ > In my Fedora 42 varsion, all went smoothly and haven't noticed yet any hickups.. Jarmo, oh1mrr |
|
From: Marco C. <PY...@ou...> - 2025-09-18 01:29:18
|
Smart and logic! I've been able to complete the build now, but failing to install since there is not a rule for --target install and my skill with compiling code is quite limited. So I have all build done but I don't know how to install! Regards PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Alex Lelievre <al...@fo...> Sent: Wednesday, September 17, 2025 9:58:09 PM To: PY...@ou... <PY...@ou...>; software development WSJT <wsj...@li...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 Have you considered just using an older version of Cmake? I must have three versions on my machine! best, alex K6LOT On Sep 17, 2025, at 3:27 PM, Marco Calistri via wsjt-devel <wsj...@li...> wrote: Sorry to be filling the mailing list with my personal issue! I tried to use the definition -DCMAKE_POLICY_VERSION_MINIMUM=3.5...3.11 \ but the error continues: CMake Error at CMakeLists.txt:199 (add_custom_target): The target name "install" is reserved or not valid for certain CMake features, such as generator expressions, and may result in undefined behavior. Then I get stuck. Regards, PY1ZRJ Il 17/09/25 16:22, George Baltz ha scritto: I'm using 4.1.1; I set the max to 3.11 to avoid the changes to the 'install' target. On 9/17/25 3:18 PM, Marco Calistri wrote: Based on cmake documentation, I found the following rule: Changed in version 4.0: Compatibility with versions of CMake older than 3.5 is removed. Calls to cmake_minimum_required(VERSION) or cmake_policy(VERSION) that do not specify at least 3.5 as their policy version (optionally via ...<max>) will produce an error in CMake 4.0 and above. Then, since my installed cmake version is the 4.1, how do I set the variable? (VERSION 3.5...4.1) ??? I'm a bit confused about that. Regards, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Marco Calistri via wsjt-devel <wsj...@li...><mailto:wsj...@li...> Sent: Wednesday, September 17, 2025 2:35:57 PM To: WSJT software development <wsj...@li...><mailto:wsj...@li...> Cc: Marco Calistri <PY...@ou...><mailto:PY...@ou...>; George Baltz <Geo...@gm...><mailto:Geo...@gm...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 Will try that George, Thanks for the heads-up! 73s PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: George Baltz via wsjt-devel <wsj...@li...><mailto:wsj...@li...> Sent: Wednesday, September 17, 2025 2:19:57 PM To: wsj...@li...<mailto:wsj...@li...> <wsj...@li...><mailto:wsj...@li...> Cc: George Baltz <Geo...@gm...><mailto:Geo...@gm...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 Add the max version to the same addition - -DCMAKE_POLICY_VERSION_MINIMUM=3.5...3.11 On 9/16/25 20:58, Marco Calistri via wsjt-devel wrote: > Hello, > > I attempted to compile the new source WSJTX 3.0.0-rc1 code as always I > did so far, but now cmake is giving an error. > > This is the sequence of commands I alway launch (in this specific case I > added the POLICY_VERSION=3.5): > > tar -xzvf /home/marco/Scaricati/wsjtx-3.0.0-rc1.tgz -C /home/marco/WSJT- > X_build/build/ > cd /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/ > /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/usr/local/include \ > -Dhamlib_LIBRARIES=/usr/local/lib64/libhamlib.so \ > -Dhamlib_LIBRARY_DIRS=/usr/local/lib64 \ > -DWSJT_GENERATE_DOCS=OFF \ > -DWSJT_SKIP_MANPAGES=ON \ > -DWSJT_QMAP=NO \ > -Werror=deprecated-declarations \ > -Wno-error \ > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 > -DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx . > > This is the answer of cmake: > > CMake Warning: > No source or binary directory provided. Both will be assumed to be the > same as the current working directory, but note that this warning will > become a fatal error in future CMake releases. > > > CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): > Compatibility with CMake < 3.10 will be removed from a future version of > CMake. > > Update the VERSION argument <min> value. Or, use the <min>...<max> > syntax > to tell CMake that the project requires at least <min> but has been > updated > to work with policies introduced by <max> or earlier. > > > -- The C compiler identification is GNU 15.2.0 > -- The CXX compiler identification is GNU 15.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Found Git: /usr/bin/git (found version "2.51.0") > CMake Warning (dev) at /usr/share/cmake/Modules/ExternalProject/ > shared_internal_commands.cmake:1261 (message): > The DOWNLOAD_EXTRACT_TIMESTAMP option was not given and policy CMP0135 is > not set. The policy's OLD behavior will be used. When using a URL > download, the timestamps of extracted files should preferably be that of > the time of extraction, otherwise code that depends on the extracted > contents might not be rebuilt if the URL changes. The OLD behavior > preserves the timestamps from the archive instead, but this is > usually not > what you want. Update your project to the NEW behavior or specify the > DOWNLOAD_EXTRACT_TIMESTAMP option with a value of true to avoid this > robustness issue. > Call Stack (most recent call first): > /usr/share/cmake/Modules/ExternalProject.cmake:3080 > (_ep_add_download_command) > CMakeLists.txt:112 (ExternalProject_Add) > This warning is for project developers. Use -Wno-dev to suppress it. > > CMake Warning (dev) at /usr/share/cmake/Modules/ExternalProject/ > shared_internal_commands.cmake:1261 (message): > The DOWNLOAD_EXTRACT_TIMESTAMP option was not given and policy CMP0135 is > not set. The policy's OLD behavior will be used. When using a URL > download, the timestamps of extracted files should preferably be that of > the time of extraction, otherwise code that depends on the extracted > contents might not be rebuilt if the URL changes. The OLD behavior > preserves the timestamps from the archive instead, but this is > usually not > what you want. Update your project to the NEW behavior or specify the > DOWNLOAD_EXTRACT_TIMESTAMP option with a value of true to avoid this > robustness issue. > Call Stack (most recent call first): > /usr/share/cmake/Modules/ExternalProject.cmake:3080 > (_ep_add_download_command) > CMakeLists.txt:165 (ExternalProject_Add) > This warning is for project developers. Use -Wno-dev to suppress it. > > CMake Error at CMakeLists.txt:199 (add_custom_target): > The target name "install" is reserved or not valid for certain CMake > features, such as generator expressions, and may result in undefined > behavior. > > > -- Configuring incomplete, errors occurred! > marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1<mailto:marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1>> - > DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx . > > > Could someone kindly clarify to me what I need to change, in order the > code being compiled without error, please? > Note: marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1<mailto:marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1>> cmake > --version > cmake version 4.1.1 > > TNX! > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > > > > Il 15/09/25 11:02, Joseph Taylor via wsjt-devel ha scritto: _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- 73 de Marco, PY1ZRJ (former IK5BCU) <Uc7xIyLqOTEc0ZKZ.jpeg> <OpenPGP_0x38215F3BB231677C.asc> _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Alex L. <al...@fo...> - 2025-09-18 01:13:58
|
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Have you considered just using an older version of Cmake? I must have three versions on my machine!<br id="lineBreakAtBeginningOfSignature"><div dir="ltr">best,<div>alex K6LOT<div><br class="webkit-block-placeholder"></div></div></div><div dir="ltr"><br><blockquote type="cite">On Sep 17, 2025, at 3:27 PM, Marco Calistri via wsjt-devel <wsj...@li...> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Sorry to be filling the mailing list with my personal issue!<br>
<br>
I tried to use the definition
-DCMAKE_POLICY_VERSION_MINIMUM=3.5...3.11 \ <br>
but the error continues:<br>
<br>
<i>CMake Error at CMakeLists.txt:199 (add_custom_target):<br>
The target name "install" is reserved or not valid for certain
CMake<br>
features, such as generator expressions, and may result in
undefined<br>
behavior.</i><br>
<br>
Then I get stuck.<br>
Regards,<br>
<br>
PY1ZRJ<br>
<br>
<br>
<div class="moz-cite-prefix">Il 17/09/25 16:22, George Baltz ha
scritto:<br>
</div>
<blockquote type="cite" cite="mid:eca...@gm...">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>I'm using 4.1.1; I set the max to 3.11 to avoid the changes to
the 'install' target.</p>
<div class="moz-cite-prefix">On 9/17/25 3:18 PM, Marco Calistri
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CH2...@CH...">
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Based on cmake documentation, I found the following rule:</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Changed in version 4.0: Compatibility with versions of CMake
older than 3.5 is removed. Calls to
cmake_minimum_required(VERSION) or cmake_policy(VERSION) that
do not specify at least 3.5 as their policy version
(optionally via ...<max>) will produce an error in CMake
4.0 and above.</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Then, since my installed cmake version is the 4.1, how do I
set the variable?</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
(VERSION 3.5...4.1) ???</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
I'm a bit confused about that.</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Regards,</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Marco PY1ZRJ </div>
<div id="ms-outlook-mobile-body-separator-line" data-applydefaultfontstyles="true" dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
</div>
<div dir="auto" style="font-family:Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif;font-size:12pt" id="ms-outlook-mobile-signature"> <span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">Inviato
da <a href="https://aka.ms/AAb9ysg" moz-do-not-send="true">Outlook
per Android</a></span></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Marco Calistri via wsjt-devel <a class="moz-txt-link-rfc2396E" href="mailto:wsj...@li..." moz-do-not-send="true"><wsj...@li...></a><br>
<b>Sent:</b> Wednesday, September 17, 2025 2:35:57 PM<br>
<b>To:</b> WSJT software development <a class="moz-txt-link-rfc2396E" href="mailto:wsj...@li..." moz-do-not-send="true"><wsj...@li...></a><br>
<b>Cc:</b> Marco Calistri <a class="moz-txt-link-rfc2396E" href="mailto:PY...@ou..." moz-do-not-send="true"><PY...@ou...></a>;
George Baltz <a class="moz-txt-link-rfc2396E" href="mailto:Geo...@gm..." moz-do-not-send="true"><Geo...@gm...></a><br>
<b>Subject:</b> Re: [wsjt-devel] Candidate Release WSJT-X
3.0.0-rc1</font>
<div> </div>
</div>
<div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">
Will try that George,</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">
Thanks for the heads-up!</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">
<br>
</div>
<div dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">
73s PY1ZRJ </div>
<div id="x_ms-outlook-mobile-body-separator-line" data-applydefaultfontstyles="true" dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">
<div style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">
<br>
</div>
</div>
<div id="x_ms-outlook-mobile-signature" dir="auto" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">
<span style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt">Inviato
da </span><a href="https://aka.ms/AAb9ysg" style="font-family:Aptos,Aptos_MSFontService,-apple-system,Roboto,Arial,Helvetica,sans-serif; font-size:12pt" moz-do-not-send="true">Outlook per Android</a></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> George Baltz via
wsjt-devel <a class="moz-txt-link-rfc2396E" href="mailto:wsj...@li..." moz-do-not-send="true"><wsj...@li...></a><br>
<b>Sent:</b> Wednesday, September 17, 2025 2:19:57 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:wsj...@li..." moz-do-not-send="true">wsj...@li...</a>
<a class="moz-txt-link-rfc2396E" href="mailto:wsj...@li..." moz-do-not-send="true"><wsj...@li...></a><br>
<b>Cc:</b> George Baltz <a class="moz-txt-link-rfc2396E" href="mailto:Geo...@gm..." moz-do-not-send="true"><Geo...@gm...></a><br>
<b>Subject:</b> Re: [wsjt-devel] Candidate Release WSJT-X
3.0.0-rc1</font>
<div> </div>
</div>
<div class="x_BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="x_PlainText">Add the max version to the same
addition -<br>
-DCMAKE_POLICY_VERSION_MINIMUM=3.5...3.11<br>
<br>
On 9/16/25 20:58, Marco Calistri via wsjt-devel wrote:<br>
> Hello,<br>
> <br>
> I attempted to compile the new source WSJTX
3.0.0-rc1 code as always I <br>
> did so far, but now cmake is giving an error.<br>
> <br>
> This is the sequence of commands I alway launch
(in this specific case I <br>
> added the POLICY_VERSION=3.5):<br>
> <br>
> tar -xzvf
/home/marco/Scaricati/wsjtx-3.0.0-rc1.tgz -C
/home/marco/WSJT- <br>
> X_build/build/<br>
> cd
/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/<br>
> /usr/bin/cmake
-Dhamlib_INCLUDE_DIRS=/usr/local/include \<br>
>
-Dhamlib_LIBRARIES=/usr/local/lib64/libhamlib.so \<br>
> -Dhamlib_LIBRARY_DIRS=/usr/local/lib64 \<br>
> -DWSJT_GENERATE_DOCS=OFF \<br>
> -DWSJT_SKIP_MANPAGES=ON \<br>
> -DWSJT_QMAP=NO \<br>
> -Werror=deprecated-declarations \<br>
> -Wno-error \<br>
> -DCMAKE_POLICY_VERSION_MINIMUM=3.5<br>
>
-DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx
.<br>
> <br>
> This is the answer of cmake:<br>
> <br>
> CMake Warning:<br>
> No source or binary directory provided. Both
will be assumed to be the<br>
> same as the current working directory, but
note that this warning will<br>
> become a fatal error in future CMake releases.<br>
> <br>
> <br>
> CMake Deprecation Warning at CMakeLists.txt:1
(cmake_minimum_required):<br>
> Compatibility with CMake < 3.10 will be
removed from a future version of<br>
> CMake.<br>
> <br>
> Update the VERSION argument <min>
value. Or, use the <min>...<max> <br>
> syntax<br>
> to tell CMake that the project requires at
least <min> but has been <br>
> updated<br>
> to work with policies introduced by
<max> or earlier.<br>
> <br>
> <br>
> -- The C compiler identification is GNU 15.2.0<br>
> -- The CXX compiler identification is GNU 15.2.0<br>
> -- Detecting C compiler ABI info<br>
> -- Detecting C compiler ABI info - done<br>
> -- Check for working C compiler: /usr/bin/cc -
skipped<br>
> -- Detecting C compile features<br>
> -- Detecting C compile features - done<br>
> -- Detecting CXX compiler ABI info<br>
> -- Detecting CXX compiler ABI info - done<br>
> -- Check for working CXX compiler: /usr/bin/c++ -
skipped<br>
> -- Detecting CXX compile features<br>
> -- Detecting CXX compile features - done<br>
> -- Found Git: /usr/bin/git (found version
"2.51.0")<br>
> CMake Warning (dev) at
/usr/share/cmake/Modules/ExternalProject/ <br>
> shared_internal_commands.cmake:1261 (message):<br>
> The DOWNLOAD_EXTRACT_TIMESTAMP option was not
given and policy CMP0135 is<br>
> not set. The policy's OLD behavior will be
used. When using a URL<br>
> download, the timestamps of extracted files
should preferably be that of<br>
> the time of extraction, otherwise code that
depends on the extracted<br>
> contents might not be rebuilt if the URL
changes. The OLD behavior<br>
> preserves the timestamps from the archive
instead, but this is <br>
> usually not<br>
> what you want. Update your project to the NEW
behavior or specify the<br>
> DOWNLOAD_EXTRACT_TIMESTAMP option with a value
of true to avoid this<br>
> robustness issue.<br>
> Call Stack (most recent call first):<br>
>
/usr/share/cmake/Modules/ExternalProject.cmake:3080 <br>
> (_ep_add_download_command)<br>
> CMakeLists.txt:112 (ExternalProject_Add)<br>
> This warning is for project developers. Use
-Wno-dev to suppress it.<br>
> <br>
> CMake Warning (dev) at
/usr/share/cmake/Modules/ExternalProject/ <br>
> shared_internal_commands.cmake:1261 (message):<br>
> The DOWNLOAD_EXTRACT_TIMESTAMP option was not
given and policy CMP0135 is<br>
> not set. The policy's OLD behavior will be
used. When using a URL<br>
> download, the timestamps of extracted files
should preferably be that of<br>
> the time of extraction, otherwise code that
depends on the extracted<br>
> contents might not be rebuilt if the URL
changes. The OLD behavior<br>
> preserves the timestamps from the archive
instead, but this is <br>
> usually not<br>
> what you want. Update your project to the NEW
behavior or specify the<br>
> DOWNLOAD_EXTRACT_TIMESTAMP option with a value
of true to avoid this<br>
> robustness issue.<br>
> Call Stack (most recent call first):<br>
>
/usr/share/cmake/Modules/ExternalProject.cmake:3080 <br>
> (_ep_add_download_command)<br>
> CMakeLists.txt:165 (ExternalProject_Add)<br>
> This warning is for project developers. Use
-Wno-dev to suppress it.<br>
> <br>
> CMake Error at CMakeLists.txt:199
(add_custom_target):<br>
> The target name "install" is reserved or not
valid for certain CMake<br>
> features, such as generator expressions, and
may result in undefined<br>
> behavior.<br>
> <br>
> <br>
> -- Configuring incomplete, errors occurred!<br>
> <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1" moz-do-not-send="true">marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1</a>>
- <br>
>
DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx
.<br>
> <br>
> <br>
> Could someone kindly clarify to me what I need to
change, in order the <br>
> code being compiled without error, please?<br>
> Note: <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1" moz-do-not-send="true">marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1</a>>
cmake <br>
> --version<br>
> cmake version 4.1.1<br>
> <br>
> TNX!<br>
> <br>
> ---<br>
> *73 de Marco, PY1ZRJ (former IK5BCU)*<br>
> **<br>
> <br>
> <br>
> <br>
> Il 15/09/25 11:02, Joseph Taylor via wsjt-devel
ha scritto:<br>
<br>
<br>
<br>
_______________________________________________<br>
wsjt-devel mailing list<br>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:wsj...@li..." moz-do-not-send="true">wsj...@li...</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel" moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a><br>
</div>
</span></font></div>
</div>
</blockquote>
</blockquote>
<br>
<br>
<div class="moz-signature" signature-switch-id="e31c2a88-22b6-40ba-8925-740a425c9714">---<br>
<b>73 de Marco, PY1ZRJ (former IK5BCU)<b><br>
<div><Uc7xIyLqOTEc0ZKZ.jpeg></div></b></b></div>
<div><OpenPGP_0x38215F3BB231677C.asc></div><span>_______________________________________________</span><br><span>wsjt-devel mailing list</span><br><span>wsj...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/wsjt-devel</span><br></div></blockquote></body></html> |
|
From: Marco C. <PY...@ou...> - 2025-09-17 22:25:42
|
Sorry to be filling the mailing list with my personal issue! I tried to use the definition -DCMAKE_POLICY_VERSION_MINIMUM=3.5...3.11 \ but the error continues: /CMake Error at CMakeLists.txt:199 (add_custom_target): The target name "install" is reserved or not valid for certain CMake features, such as generator expressions, and may result in undefined behavior./ Then I get stuck. Regards, PY1ZRJ Il 17/09/25 16:22, George Baltz ha scritto: > > I'm using 4.1.1; I set the max to 3.11 to avoid the changes to the > 'install' target. > > On 9/17/25 3:18 PM, Marco Calistri wrote: >> Based on cmake documentation, I found the following rule: >> >> Changed in version 4.0: Compatibility with versions of CMake older >> than 3.5 is removed. Calls to cmake_minimum_required(VERSION) or >> cmake_policy(VERSION) that do not specify at least 3.5 as their >> policy version (optionally via ...<max>) will produce an error in >> CMake 4.0 and above. >> >> Then, since my installed cmake version is the 4.1, how do I set the >> variable? >> >> (VERSION 3.5...4.1) ??? >> >> I'm a bit confused about that. >> >> Regards, >> >> Marco PY1ZRJ >> >> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >> ------------------------------------------------------------------------ >> *From:* Marco Calistri via wsjt-devel <wsj...@li...> >> *Sent:* Wednesday, September 17, 2025 2:35:57 PM >> *To:* WSJT software development <wsj...@li...> >> *Cc:* Marco Calistri <PY...@ou...>; George Baltz >> <Geo...@gm...> >> *Subject:* Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 >> Will try that George, >> >> Thanks for the heads-up! >> >> 73s PY1ZRJ >> >> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >> ------------------------------------------------------------------------ >> *From:* George Baltz via wsjt-devel <wsj...@li...> >> *Sent:* Wednesday, September 17, 2025 2:19:57 PM >> *To:* wsj...@li... <wsj...@li...> >> *Cc:* George Baltz <Geo...@gm...> >> *Subject:* Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 >> Add the max version to the same addition - >> -DCMAKE_POLICY_VERSION_MINIMUM=3.5...3.11 >> >> On 9/16/25 20:58, Marco Calistri via wsjt-devel wrote: >> > Hello, >> > >> > I attempted to compile the new source WSJTX 3.0.0-rc1 code as always I >> > did so far, but now cmake is giving an error. >> > >> > This is the sequence of commands I alway launch (in this specific >> case I >> > added the POLICY_VERSION=3.5): >> > >> > tar -xzvf /home/marco/Scaricati/wsjtx-3.0.0-rc1.tgz -C >> /home/marco/WSJT- >> > X_build/build/ >> > cd /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/ >> > /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/usr/local/include \ >> > -Dhamlib_LIBRARIES=/usr/local/lib64/libhamlib.so \ >> > -Dhamlib_LIBRARY_DIRS=/usr/local/lib64 \ >> > -DWSJT_GENERATE_DOCS=OFF \ >> > -DWSJT_SKIP_MANPAGES=ON \ >> > -DWSJT_QMAP=NO \ >> > -Werror=deprecated-declarations \ >> > -Wno-error \ >> > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 >> > -DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx . >> > >> > This is the answer of cmake: >> > >> > CMake Warning: >> > No source or binary directory provided. Both will be assumed to >> be the >> > same as the current working directory, but note that this >> warning will >> > become a fatal error in future CMake releases. >> > >> > >> > CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): >> > Compatibility with CMake < 3.10 will be removed from a future >> version of >> > CMake. >> > >> > Update the VERSION argument <min> value. Or, use the <min>...<max> >> > syntax >> > to tell CMake that the project requires at least <min> but has been >> > updated >> > to work with policies introduced by <max> or earlier. >> > >> > >> > -- The C compiler identification is GNU 15.2.0 >> > -- The CXX compiler identification is GNU 15.2.0 >> > -- Detecting C compiler ABI info >> > -- Detecting C compiler ABI info - done >> > -- Check for working C compiler: /usr/bin/cc - skipped >> > -- Detecting C compile features >> > -- Detecting C compile features - done >> > -- Detecting CXX compiler ABI info >> > -- Detecting CXX compiler ABI info - done >> > -- Check for working CXX compiler: /usr/bin/c++ - skipped >> > -- Detecting CXX compile features >> > -- Detecting CXX compile features - done >> > -- Found Git: /usr/bin/git (found version "2.51.0") >> > CMake Warning (dev) at /usr/share/cmake/Modules/ExternalProject/ >> > shared_internal_commands.cmake:1261 (message): >> > The DOWNLOAD_EXTRACT_TIMESTAMP option was not given and policy >> CMP0135 is >> > not set. The policy's OLD behavior will be used. When using a URL >> > download, the timestamps of extracted files should preferably be >> that of >> > the time of extraction, otherwise code that depends on the extracted >> > contents might not be rebuilt if the URL changes. The OLD behavior >> > preserves the timestamps from the archive instead, but this is >> > usually not >> > what you want. Update your project to the NEW behavior or >> specify the >> > DOWNLOAD_EXTRACT_TIMESTAMP option with a value of true to avoid this >> > robustness issue. >> > Call Stack (most recent call first): >> > /usr/share/cmake/Modules/ExternalProject.cmake:3080 >> > (_ep_add_download_command) >> > CMakeLists.txt:112 (ExternalProject_Add) >> > This warning is for project developers. Use -Wno-dev to suppress it. >> > >> > CMake Warning (dev) at /usr/share/cmake/Modules/ExternalProject/ >> > shared_internal_commands.cmake:1261 (message): >> > The DOWNLOAD_EXTRACT_TIMESTAMP option was not given and policy >> CMP0135 is >> > not set. The policy's OLD behavior will be used. When using a URL >> > download, the timestamps of extracted files should preferably be >> that of >> > the time of extraction, otherwise code that depends on the extracted >> > contents might not be rebuilt if the URL changes. The OLD behavior >> > preserves the timestamps from the archive instead, but this is >> > usually not >> > what you want. Update your project to the NEW behavior or >> specify the >> > DOWNLOAD_EXTRACT_TIMESTAMP option with a value of true to avoid this >> > robustness issue. >> > Call Stack (most recent call first): >> > /usr/share/cmake/Modules/ExternalProject.cmake:3080 >> > (_ep_add_download_command) >> > CMakeLists.txt:165 (ExternalProject_Add) >> > This warning is for project developers. Use -Wno-dev to suppress it. >> > >> > CMake Error at CMakeLists.txt:199 (add_custom_target): >> > The target name "install" is reserved or not valid for certain CMake >> > features, such as generator expressions, and may result in undefined >> > behavior. >> > >> > >> > -- Configuring incomplete, errors occurred! >> > marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> - >> > DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx . >> > >> > >> > Could someone kindly clarify to me what I need to change, in order the >> > code being compiled without error, please? >> > Note: marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> cmake >> > --version >> > cmake version 4.1.1 >> > >> > TNX! >> > >> > --- >> > *73 de Marco, PY1ZRJ (former IK5BCU)* >> > ** >> > >> > >> > >> > Il 15/09/25 11:02, Joseph Taylor via wsjt-devel ha scritto: >> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Marco C. <PY...@ou...> - 2025-09-17 19:27:49
|
To me it's odd to set max to a minor value, but I will try as you said. Tnx! Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ Da: George Baltz <geo...@gm...> Inviato: Mercoledì, Settembre 17, 2025 4:22:50 PM A: Marco Calistri <PY...@ou...>; WSJT software development <wsj...@li...> Oggetto: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 I'm using 4.1.1; I set the max to 3.11 to avoid the changes to the 'install' target. On 9/17/25 3:18 PM, Marco Calistri wrote: Based on cmake documentation, I found the following rule: Changed in version 4.0: Compatibility with versions of CMake older than 3.5 is removed. Calls to cmake_minimum_required(VERSION) or cmake_policy(VERSION) that do not specify at least 3.5 as their policy version (optionally via ...<max>) will produce an error in CMake 4.0 and above. Then, since my installed cmake version is the 4.1, how do I set the variable? (VERSION 3.5...4.1) ??? I'm a bit confused about that. Regards, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Marco Calistri via wsjt-devel <wsj...@li...><mailto:wsj...@li...> Sent: Wednesday, September 17, 2025 2:35:57 PM To: WSJT software development <wsj...@li...><mailto:wsj...@li...> Cc: Marco Calistri <PY...@ou...><mailto:PY...@ou...>; George Baltz <Geo...@gm...><mailto:Geo...@gm...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 Will try that George, Thanks for the heads-up! 73s PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: George Baltz via wsjt-devel <wsj...@li...><mailto:wsj...@li...> Sent: Wednesday, September 17, 2025 2:19:57 PM To: wsj...@li...<mailto:wsj...@li...> <wsj...@li...><mailto:wsj...@li...> Cc: George Baltz <Geo...@gm...><mailto:Geo...@gm...> Subject: Re: [wsjt-devel] Candidate Release WSJT-X 3.0.0-rc1 Add the max version to the same addition - -DCMAKE_POLICY_VERSION_MINIMUM=3.5...3.11 On 9/16/25 20:58, Marco Calistri via wsjt-devel wrote: > Hello, > > I attempted to compile the new source WSJTX 3.0.0-rc1 code as always I > did so far, but now cmake is giving an error. > > This is the sequence of commands I alway launch (in this specific case I > added the POLICY_VERSION=3.5): > > tar -xzvf /home/marco/Scaricati/wsjtx-3.0.0-rc1.tgz -C /home/marco/WSJT- > X_build/build/ > cd /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/ > /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/usr/local/include \ > -Dhamlib_LIBRARIES=/usr/local/lib64/libhamlib.so \ > -Dhamlib_LIBRARY_DIRS=/usr/local/lib64 \ > -DWSJT_GENERATE_DOCS=OFF \ > -DWSJT_SKIP_MANPAGES=ON \ > -DWSJT_QMAP=NO \ > -Werror=deprecated-declarations \ > -Wno-error \ > -DCMAKE_POLICY_VERSION_MINIMUM=3.5 > -DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx . > > This is the answer of cmake: > > CMake Warning: > No source or binary directory provided. Both will be assumed to be the > same as the current working directory, but note that this warning will > become a fatal error in future CMake releases. > > > CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): > Compatibility with CMake < 3.10 will be removed from a future version of > CMake. > > Update the VERSION argument <min> value. Or, use the <min>...<max> > syntax > to tell CMake that the project requires at least <min> but has been > updated > to work with policies introduced by <max> or earlier. > > > -- The C compiler identification is GNU 15.2.0 > -- The CXX compiler identification is GNU 15.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Found Git: /usr/bin/git (found version "2.51.0") > CMake Warning (dev) at /usr/share/cmake/Modules/ExternalProject/ > shared_internal_commands.cmake:1261 (message): > The DOWNLOAD_EXTRACT_TIMESTAMP option was not given and policy CMP0135 is > not set. The policy's OLD behavior will be used. When using a URL > download, the timestamps of extracted files should preferably be that of > the time of extraction, otherwise code that depends on the extracted > contents might not be rebuilt if the URL changes. The OLD behavior > preserves the timestamps from the archive instead, but this is > usually not > what you want. Update your project to the NEW behavior or specify the > DOWNLOAD_EXTRACT_TIMESTAMP option with a value of true to avoid this > robustness issue. > Call Stack (most recent call first): > /usr/share/cmake/Modules/ExternalProject.cmake:3080 > (_ep_add_download_command) > CMakeLists.txt:112 (ExternalProject_Add) > This warning is for project developers. Use -Wno-dev to suppress it. > > CMake Warning (dev) at /usr/share/cmake/Modules/ExternalProject/ > shared_internal_commands.cmake:1261 (message): > The DOWNLOAD_EXTRACT_TIMESTAMP option was not given and policy CMP0135 is > not set. The policy's OLD behavior will be used. When using a URL > download, the timestamps of extracted files should preferably be that of > the time of extraction, otherwise code that depends on the extracted > contents might not be rebuilt if the URL changes. The OLD behavior > preserves the timestamps from the archive instead, but this is > usually not > what you want. Update your project to the NEW behavior or specify the > DOWNLOAD_EXTRACT_TIMESTAMP option with a value of true to avoid this > robustness issue. > Call Stack (most recent call first): > /usr/share/cmake/Modules/ExternalProject.cmake:3080 > (_ep_add_download_command) > CMakeLists.txt:165 (ExternalProject_Add) > This warning is for project developers. Use -Wno-dev to suppress it. > > CMake Error at CMakeLists.txt:199 (add_custom_target): > The target name "install" is reserved or not valid for certain CMake > features, such as generator expressions, and may result in undefined > behavior. > > > -- Configuring incomplete, errors occurred! > marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1<mailto:marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1>> - > DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx . > > > Could someone kindly clarify to me what I need to change, in order the > code being compiled without error, please? > Note: marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1<mailto:marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1>> cmake > --version > cmake version 4.1.1 > > TNX! > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > > > > Il 15/09/25 11:02, Joseph Taylor via wsjt-devel ha scritto: _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
68 messages has been excluded from this view by a project administrator.
