Sorry for top posting, I'm from my cellphone now!
Bill,
I followed your instructions and finally I obtained the expected wsjtx binary
file compiled by source.
For your and others knowledge it was not necessary to install any additional
package (dependency).
I think that the
On 14/11/2018 19:14, Marco Calistri via wsjt-devel wrote:
-- Build files have been written to:
/home/marco/WSJT-X_build/jtsource/wsjtx-2.0.0-rc4
Hi Marco,
this output is unexpected. I believe it may be due to the source
directory containing build files. I suggest that you remove the source
Maybe those will be helpful to find an issue.
Sometimes after e finished (and stored) QSO a new CQ still is present as new.
See here 9A2JK as example.
But in other cases it work correctly (here G6NHU).
I am using rc4 on Windows-10.
___
Il 14/11/18 15:45, Bill Somerville ha scritto:
> On 14/11/2018 17:17, Marco Calistri wrote:
>> **GOOD PROCEDURE***
>> cd jtsource/wsjtx-2.0.0-rc4/
>> /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/usr/include \
>> -Dhamlib_LIBRARIES=/usr/lib64/libhamlib.so \
>>
On 14/11/2018 17:17, Marco Calistri wrote:
**GOOD PROCEDURE***
cd jtsource/wsjtx-2.0.0-rc4/
/usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/usr/include \
-Dhamlib_LIBRARIES=/usr/lib64/libhamlib.so \
-Dhamlib_LIBRARY_DIRS=/usr/lib64 \
-DWSJT_GENERATE_DOCS=OFF \
Il 14/11/18 12:15, Bill Somerville ha scritto:
> On 14/11/2018 13:32, Marco Calistri via wsjt-devel wrote:
>> This is an example of "cmake sequence" commands I used:
>>
>> cmake -D CMAKE_CXX_COMPILER=/usr/bin/g++-8 \
>> -D CMAKE_Fortran_COMPILER=/usr/bin/gfortran-8 \
>> -D
>>
On 14/11/2018 13:32, Marco Calistri via wsjt-devel wrote:
This is an example of "cmake sequence" commands I used:
cmake -D CMAKE_CXX_COMPILER=/usr/bin/g++-8 \
-D CMAKE_Fortran_COMPILER=/usr/bin/gfortran-8 \
-D
Il 14/11/18 10:54, Bill Somerville ha scritto:
> On 14/11/2018 11:07, Marco Calistri via wsjt-devel wrote:
>> The fact WSJT-X being a 32-bit application could then explain my
>> repetitive failures during source compiling on my Linux 64-bit system?
>> Do I need to install all 32-bit dependencies
On 14/11/2018 11:07, Marco Calistri via wsjt-devel wrote:
The fact WSJT-X being a 32-bit application could then explain my
repetitive failures during source compiling on my Linux 64-bit system?
Do I need to install all 32-bit dependencies in order to succeed?
Thanks!
--
73 de Marco, PY1ZRJ
Hi Bill,
> Hi Mike,
>
> thanks for the ADIF record, clearly something is not right, looking
> into it right now.
>
> The reason the 32-bit version of the OpenSSL libraries are needed is
> because WSJT-X is a 32-bit application.
>
> 73
> Bill
> G4WJS.
>
The fact WSJT-X being a 32-bit application
On 13/11/2018 23:28, Mike wrote:
I don't think we can be much clearer. The Quick Start Guide has a
clickable link to the right version and it explicitly mentions that
the 32-bit version is the right version even if you are running a
64-bit version of Windows.
You can't be much clearer, but
Hello Bill,
On Tue, Nov 13, 2018 at 3:05 PM Bill Somerville
wrote:
>
> Your assessment is correct and it sounds like something is not right. Can
> you reply with the ADIF record from your wsjtx_log.adi file that you think
> should have disabled this new call highlighting for N2ADV on 20m?
>
Hi Mike,
comments below.
On 13/11/2018 20:43, Mike wrote:
Yes it was a different mode before but the highlight by mode is not
checked so shouldn't it just consider it a new call or not a new call
without regard to the mode? Perhaps I don't understand the logic yet
... can you explain it a
Yes it was a different mode before but the highlight by mode is not checked
so shouldn't it just consider it a new call or not a new call without
regard to the mode? Perhaps I don't understand the logic yet ... can you
explain it a little better or do you think it not working yet?
I had already
Hi Mike,
comments below.
On 13/11/2018 20:13, Mike wrote:
The "New Call" color annunciation is triggering falsely. It's claiming
N2ADV when he's calling CQ on 20 meters today is a new call, but the
contact is definitely still in the file as a contact from 2014.
Please double check the entry
The "New Call" color annunciation is triggering falsely. It's claiming
N2ADV when he's calling CQ on 20 meters today is a new call, but the
contact is definitely still in the file as a contact from 2014.
Also still getting the "Error loading LoTW Users data" error when starting
the program.
Wed, 17 Oct 2018 16:59:21 +0100
Bill Somerville kirjoitti:
> Hi Don and Jarmo,>
> looks like this is a defect, if you go to "Settings->Colors" do you
> see an empty box at the top of the panel? If so please report back
No, I have not that empty box, linux fedora 64 version
Jarmo
.
Don AA5AU
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Wednesday, October 17, 2018 10:59 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Colors
On 17/10/2018 16:54, Don Hill AA5AU wrote:
> The same here. Enabled "Show DXC
: [wsjt-devel] Colors
The same here. Enabled "Show DXCC... etc" and not getting colors. Restarted
and no help.
Don AA5AU
-Original Message-
From: jarmo [mailto:oh1...@nic.fi]
Sent: Wednesday, October 17, 2018 10:42 AM
To: WSJT software development
Subject: [wsjt-devel] Colors
Wsj
On 17/10/2018 16:54, Don Hill AA5AU wrote:
The same here. Enabled "Show DXCC... etc" and not getting colors. Restarted
and no help.
Don AA5AU
Hi Don and Jarmo,
looks like this is a defect, if you go to "Settings->Colors" do you see
an empty box at the top of the panel? If so please report
The same here. Enabled "Show DXCC... etc" and not getting colors. Restarted
and no help.
Don AA5AU
-Original Message-
From: jarmo [mailto:oh1...@nic.fi]
Sent: Wednesday, October 17, 2018 10:42 AM
To: WSJT software development
Subject: [wsjt-devel] Colors
Wsjt-x v2 rc3
Now t
Wsjt-x v2 rc3
Now took in use "Show DXCC, grid and worked before". No
colors seen. But now when double-click from cqrlog-monitor
window, all works.
Jarmo oh1mrr
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Hi Rudy,
On 4/3/2018 1:23 PM, on4...@telenet.be wrote:
I al using these WSJT-X version 1.9.0 rev3.
I have a question.
When it have a QSO, then the line color red with my call in it. The while
conversation the lines color red. But when it use the free msg line in the QSO
the line is not color
Hello,
I al using these WSJT-X version 1.9.0 rev3.
I have a question.
When it have a QSO, then the line color red with my call in it. The while
conversation the lines color red. But when it use the free msg line in the QSO
the line is not color red. So the other station don't know from who this
Hi Joe
Seems to be working fine, learning how to use it now.
Charlie
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: 02 July 2017 19:01
To: WSJT software development
Subject: Re: [wsjt-devel] Colors - FT8
Hi Kari,
> The 'worked before' feature is a
Hi Kari,
The 'worked before' feature is also not working with FT8.
I think this could be fixed by adding test for
FT8 on line 105 of "logbook/adif.cpp"
Thanks! I believe it's fixed in r.
-- Joe, K1JT
On 07/02/2017 06:14 PM, James Shaver (N2ADV) wrote:
Running r7775 (Win 7) I've noticed and others have brought to my attention that
the colors for new DXCC and new call aren't showing up in the RX window. CQ in
Message and My Call in message are working.
73,
Jim S.
N2ADV
The 'worked
Running r7775 (Win 7) I've noticed and others have brought to my attention that
the colors for new DXCC and new call aren't showing up in the RX window. CQ in
Message and My Call in message are working.
73,
Jim S.
N2ADV
28 matches
Mail list logo
