flrig development version 2.0.05.77 posted at
Index of /alpha/flrigs
Tested with Icom 7300 and QRP L:abs QMX+ transceivers.
73, David,
W1HKJ
|
Hey everyone. I'm looking for help to fix a problem with fldigi on my Mac computer (v 12.7.5). I downloaded fldigi and it worked for a day or 2, but now every time I try to open it, it closes almost immediately. I'm not sure what the issue is or how to diagnose it. any help would be appreciated.
?
|
Re: fldigi 4.2.05.24 development version posted at
Hi.
AFIK, it's an OS imposed restriction, of the use of "Microphone" like unknown (to the OS dev's) devices (aka any audio input device) as a privacy thing.
Winders does much the same, but may be easier to tell that to let it run.
No such issues (that I've found yet) on any Linux.
(Currently, using LMDE6 here, or an old Linux Lite version, on an Acer One for /P use, mainly these days to receive the weekly SWRG broadcasts.? I have to drive for anything up to 20 minutes to find a HF quiet area, here in central UK!)
73.
Dave G0WBX
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: fldigi 4.2.05.24 development version posted at
No, sadly nothing new on this issue in this version.
I’m running??4.2.05.24 on a M2 MacBook Air (Sequoia 15.0.1) and confirm the "FLDigi would like to access the microphone” issue IS still present in this version.
It still takes *exactly* 43 (forty-three) clicks of the “Allow” button before the “microphone” (IC7300 in my case) is allowed access.
I wonder why it *always* works after the 43rd “Allow”??
Could that number be helpful in find the the cause of this issue?
toggle quoted message
Show quoted text
Anything new on the "FLDigi would like to access the microphone" problem?
|
Re: fldigi 4.2.05.24 development version posted at
Anything new on the "FLDigi would like to access the microphone" problem?
|
Re: fldigi 4.2.05.24 development version posted at
toggle quoted message
Show quoted text
On Oct 5, 2024, at 10:20?AM, Dave, W1HKJ via groups.io <w1hkj@...> wrote: ?
The latest OS that I build and
test on is Sonoma 14.6.1.
David
On 10/4/24 15:56, John T. Hoskins,
WA5NJG wrote:
Dave,
I have been using FLdigi-4.2.05.24 successfully for
several months now.?
I am going to have to upgrade my MacOS to the latest
and greatest (Sequoia 15.0.1) in the near future.
Have you done any testing with Sequoia?
73,
John WA5NJG
On May 29, 2024, at 2:25 PM, Dave, W1HKJ < w1hkj@...>
wrote:
Index of /alpha/fldigi
Author:
dave-w1hkj <w1hkj@...>
Date:?? Wed May 29 13:48:38 2024 -0500
??? Micro modems
?? ?
????? * change name to avoid double word parsing
issues with
??????? frequencies2.txt
Author: dave-w1hkj <w1hkj@...>
Date:?? Tue May 28 00:33:23 2024 -0500
??? colors and scheme
?? ?
????? * allow user to select default background and
foreground
??????? colors
??????? . supplements command line usage
...
see readme.txt for complete list of commits.
73, David, W1HKJ
|
Re: Guide to New Rig backend creation?
The comments / count reference
is for the coder's convenience.?
ls src/rigs/other
AOR5K.cxx???? PCR1000.cxx?? RAY152.cxx??? sunsdr2.cxx?
TMD710.cxx
FLEX1500.cxx? PowerSDR.cxx? SmartSDR.cxx? tcisdr.cxx??
trusdx.cxx
The PCR1000 is a pretty old Icom black box receiver that I once
owned.? The PCR1000.cxx code might be useful to you.
Dave
On 10/5/24 05:44, Dave, G?WBX via
groups.io wrote:
toggle quoted message
Show quoted text
Hi again.
Thanks for that info David.
Checking off what you described...
It was:-
??? src/rigs/rigs.cxx:???
&rig_ICR71,??? ??? // 63
That escaped my radar.? (Of course, I've used?
"&rig_ICR9000" .)
(Do I guess right, that the // 63 comment is just a human
convenience count reference?? At present, the R9000 is a the
bottom of the list sporting? // 111 after it.)
Anyway..? It now appears in the selection list and other than
errors when trying to initialise, it generates C-IV traffic that
currently is ignored by the R9000, so I should be good for some
late nights with the R9000 C-IV manual, and a warm computer, for a
while...
I think, the closest TRX, is the IC-781, from the same era as the
R9000.
Hamlib has both, so I'll be comparing stuff in the back-ends there
too.? I have found that Grig via Hamlip works with the R9000, but
there are some "funnies" with filter selections etc.?? Maybe the
two are not so similar.?? More to learn...
Best Regards David, your help is very much appreciated.
Oh, I'm doing all this with the sources for? flrig-2.0.05.75
73.
Dave G0WBX.
PS:??? The build warnings I see, are for a FT2000
rigs/yaesu/FT2000.cxx:
In member function ‘virtual void RIG_FT2000::set_rf_gain(int)’:
rigs/yaesu/FT2000.cxx:1124:52: warning: ‘%03d’ directive output
may be truncated writing between 3 and 9 bytes into a region of
size 5 [-Wformat-truncation=]
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd),
"RG0%03d;", val * 255 / 100);
????? |??????????????????????????????????????????????????? ^~~~
rigs/yaesu/FT2000.cxx:1124:48: note: directive argument in the
range [-21474836, 21474836]
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd),
"RG0%03d;", val * 255 / 100);
????? |???????????????????????????????????????????????
^~~~~~~~~~
rigs/yaesu/FT2000.cxx:1124:25: note: ‘snprintf’ output between 8
and 14 bytes into a destination of size 8
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd),
"RG0%03d;", val * 255 / 100);
????? |????????????????
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rigs/yaesu/FT2000.cxx:1119:52: warning: ‘%03d’ directive output
may be truncated writing between 3 and 9 bytes into a region of
size 5 [-Wformat-truncation=]
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd),
"RG1%03d;", val * 255 / 100);
????? |??????????????????????????????????????????????????? ^~~~
rigs/yaesu/FT2000.cxx:1119:48: note: directive argument in the
range [-21474836, 21474836]
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd),
"RG1%03d;", val * 255 / 100);
????? |???????????????????????????????????????????????
^~~~~~~~~~
rigs/yaesu/FT2000.cxx:1119:25: note: ‘snprintf’ output between 8
and 14 bytes into a destination of size 8
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd),
"RG1%03d;", val * 255 / 100);
????? |????????????????
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: fldigi 4.2.05.24 development version posted at
The latest OS that I build and
test on is Sonoma 14.6.1.
David
On 10/4/24 15:56, John T. Hoskins,
WA5NJG wrote:
toggle quoted message
Show quoted text
Dave,
I have been using FLdigi-4.2.05.24 successfully for
several months now.?
I am going to have to upgrade my MacOS to the latest
and greatest (Sequoia 15.0.1) in the near future.
Have you done any testing with Sequoia?
73,
John WA5NJG
On May 29, 2024, at 2:25 PM, Dave, W1HKJ < w1hkj@...>
wrote:
Index of /alpha/fldigi
Author:
dave-w1hkj <w1hkj@...>
Date:?? Wed May 29 13:48:38 2024 -0500
??? Micro modems
?? ?
????? * change name to avoid double word parsing
issues with
??????? frequencies2.txt
Author: dave-w1hkj <w1hkj@...>
Date:?? Tue May 28 00:33:23 2024 -0500
??? colors and scheme
?? ?
????? * allow user to select default background and
foreground
??????? colors
??????? . supplements command line usage
...
see readme.txt for complete list of commits.
73, David, W1HKJ
|
Re: Guide to New Rig backend creation?
Hi again.
Thanks for that info David.
Checking off what you described...
It was:-
??? src/rigs/rigs.cxx:??? &rig_ICR71,???
??? // 63
That escaped my radar.? (Of course, I've used?
"&rig_ICR9000" .)
(Do I guess right, that the // 63 comment is just a human
convenience count reference?? At present, the R9000 is a the bottom
of the list sporting? // 111 after it.)
Anyway..? It now appears in the selection list and other than errors
when trying to initialise, it generates C-IV traffic that currently
is ignored by the R9000, so I should be good for some late nights
with the R9000 C-IV manual, and a warm computer, for a while...
I think, the closest TRX, is the IC-781, from the same era as the
R9000.
Hamlib has both, so I'll be comparing stuff in the back-ends there
too.? I have found that Grig via Hamlip works with the R9000, but
there are some "funnies" with filter selections etc.?? Maybe the two
are not so similar.?? More to learn...
Best Regards David, your help is very much appreciated.
Oh, I'm doing all this with the sources for? flrig-2.0.05.75
73.
Dave G0WBX.
PS:??? The build warnings I see, are for a FT2000
rigs/yaesu/FT2000.cxx:
In member function ‘virtual void RIG_FT2000::set_rf_gain(int)’:
rigs/yaesu/FT2000.cxx:1124:52: warning: ‘%03d’ directive output
may be truncated writing between 3 and 9 bytes into a region of
size 5 [-Wformat-truncation=]
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG0%03d;",
val * 255 / 100);
????? |??????????????????????????????????????????????????? ^~~~
rigs/yaesu/FT2000.cxx:1124:48: note: directive argument in the
range [-21474836, 21474836]
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG0%03d;",
val * 255 / 100);
????? |??????????????????????????????????????????????? ^~~~~~~~~~
rigs/yaesu/FT2000.cxx:1124:25: note: ‘snprintf’ output between 8
and 14 bytes into a destination of size 8
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG0%03d;",
val * 255 / 100);
????? |????????????????
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rigs/yaesu/FT2000.cxx:1119:52: warning: ‘%03d’ directive output
may be truncated writing between 3 and 9 bytes into a region of
size 5 [-Wformat-truncation=]
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG1%03d;",
val * 255 / 100);
????? |??????????????????????????????????????????????????? ^~~~
rigs/yaesu/FT2000.cxx:1119:48: note: directive argument in the
range [-21474836, 21474836]
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG1%03d;",
val * 255 / 100);
????? |??????????????????????????????????????????????? ^~~~~~~~~~
rigs/yaesu/FT2000.cxx:1119:25: note: ‘snprintf’ output between 8
and 14 bytes into a destination of size 8
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG1%03d;",
val * 255 / 100);
????? |????????????????
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: fldigi 4.2.05.24 development version posted at
Greetings, I am contemplating buying a iMac with M3. I’ve always used Easy Digi with my Toshiba Satelite with Win 7. Works great on BPSK31 that I operate 90% of my QSO’s. Is there an Easy Digi product that Clifford is selling, that will provide easy connectivity using the 2024 iMac M3. All comments are greatly appreciated. 73, Ron Speer W6RRS
toggle quoted message
Show quoted text
On Oct 4, 2024, at 4:56?PM, John T. Hoskins, WA5NJG via groups.io <jt-hoskins@...> wrote: ? Dave,
I have been using FLdigi-4.2.05.24 successfully for several months now.?
I am going to have to upgrade my MacOS to the latest and greatest (Sequoia 15.0.1) in the near future.
Have you done any testing with Sequoia?
73,
John WA5NJG
On May 29, 2024, at 2:25 PM, Dave, W1HKJ < w1hkj@...> wrote:
Index of /alpha/fldigi
Author: dave-w1hkj
<w1hkj@...>
Date:?? Wed May 29 13:48:38 2024 -0500
??? Micro modems
?? ?
????? * change name to avoid double word parsing issues with
??????? frequencies2.txt
Author: dave-w1hkj <w1hkj@...>
Date:?? Tue May 28 00:33:23 2024 -0500
??? colors and scheme
?? ?
????? * allow user to select default background and foreground
??????? colors
??????? . supplements command line usage
... see readme.txt for complete list of commits. 73, David, W1HKJ
|
Re: fldigi 4.2.05.24 development version posted at
Dave,
I have been using FLdigi-4.2.05.24 successfully for several months now.?
I am going to have to upgrade my MacOS to the latest and greatest (Sequoia 15.0.1) in the near future.
Have you done any testing with Sequoia?
73,
John WA5NJG
toggle quoted message
Show quoted text
On May 29, 2024, at 2:25 PM, Dave, W1HKJ < w1hkj@...> wrote:
Index of /alpha/fldigi
Author: dave-w1hkj
<w1hkj@...>
Date:?? Wed May 29 13:48:38 2024 -0500
??? Micro modems
?? ?
????? * change name to avoid double word parsing issues with
??????? frequencies2.txt
Author: dave-w1hkj <w1hkj@...>
Date:?? Tue May 28 00:33:23 2024 -0500
??? colors and scheme
?? ?
????? * allow user to select default background and foreground
??????? colors
??????? . supplements command line usage
... see readme.txt for complete list of commits. 73, David, W1HKJ
|
Re: Guide to New Rig backend creation?
Do a grep for R71 and you will
find these line items that are critical to getting a new rig
registered:
src/Makefile.am:??? rigs/icom/ICR71.cxx \
src/Makefile.am:??? include/icom/ICR71.h \
src/rigs/icom/ICR71.cxx:#include "icom/ICR71.h"
src/rigs/icom/ICR71.cxx:const char ICR71name_[] = "IC-R71";
src/rigs/rigs.cxx:RIG_ICR71??? ??? rig_ICR71;
src/rigs/rigs.cxx:??? &rig_ICR71,??? ??? // 63
src/include/rigs.h:#include "icom/ICR71.h"
src/include/rigs.h:extern RIG_ICR71??? ??? rig_ICR71;??? ??? //
63
You should have similar for the R9000.
David
|
Re: Guide to New Rig backend creation?
Hello again David (W1HKJ)
OK.
Following your last, I now have some code (copied from the IC-R71 files, changing ALL instances of "R71" to "R9000") that appears to build OK without errors.
I don't expect it to work the R9000, as the functional code is still for a R71, but I'd expect I think, for it to create some serial CI-V port traffic (even if the R9000 ignores it due to the wrong address being used.)
The .o (and .Po) files are created, the build process completes OK (some warnings for a Yaesu backend) and ./src/flrig launches just fine from the project root directory as expected.
But, there is no IC-R9000 option listed in the Transceiver setup Rig drop-down select tool.
I'm guessing I've missed a step somewhere, to include the new rig in the list, but what and where?
Progress at least, I think, but still an extra step to take.
All the best.
Dave G0WBX.
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: Guide to New Rig backend creation?
Thanks David.
I was looking in the makefile.am file in the project's root director, not the src directory!
Hence the confusion...
Thanks again.
73.
??? Dave G0WBX.
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable
#flrig
Yes, the CAT commands can be confusing. I was looking at byte 0 for the filter width, but byte 7 is correct.
?
I changed the code to use names like your code and also fixed the vfo-b modes.
?
I found that flrig was again not setting the vfo-b frequency. The op code was wrong and should be the same as the vfo-a procedure.
In set_vfoB I changed
? ? cmd += 0x8A;
to
? ? cmd += 0x0A; // Not 0x8A, as it is the same as vfo-a
?
I still need to do more testing, but I'm out of time for now.
?
----Steve
|
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable
#flrig
Thanks Steve.? Very confusing
CAT commands.
David
On 10/3/24 03:07, Steve, KB5AW wrote:
toggle quoted message
Show quoted text
I tried your changes.
It seems to revert to the incorrect operation before the
changes I submitted.
I don't see how your case statement can work for the modes.
The only valid numbers in byte 6 are 0, 1, 2, 3, 4.
You use case numbers based on byte 6 ranging from 0 to 7 which
correspond to the menu, but doesn't correspond to the data
from the rig on byte 6.
For example, CW is 2 whether or not it is wide or narrow. In
the menu, the numbers are 2 and 3 respectively.
?
So, I reverted to my version of FT890.cxx which worked for
all of the non-narrow modes and added if statements to fix the
narrow modes.
vfo-a now works correctly on all modes. Maybe you can do it
in a better way or make any corrections.
I did not make the changes for vfo-b.
------------------------
? ? ? ? switch (replystr[6] & 0x07) {
? ? ? ? ? ? case 0: A.imode = ((replystr[6] & 0x40) ==
0x40) ? 1 : 0; break; // LSB
? ? ? ? ? ? case 1: A.imode = ((replystr[6] & 0x40) ==
0x40) ? 3 : 1; break; // USB
? ? ? ? ? ? case 2: A.imode = ((replystr[6] & 0x80) ==
0x80) ? 5 : 2; break; // CW
? ? ? ? ? ? case 3: A.imode = ((replystr[6] & 0x80) ==
0x80) ? 7 : 4; break; // AM
? ? ? ? ? ? case 4: A.imode = ((replystr[6] & 0x80) ==
0x80) ? 9 : 6; break; // FM
? ? ? ? ? ? default: A.imode = 0;
? ? ? ? }
?
// After the base mode has been determined, we need to
check for the narrow filters.
// We need to verify the base mode, as the narrow mode bits
remain on until changed.
?
? ? ? ? if (((replystr[8] & 0x80) == 0x80) &&
(A.imode == 2)) {
? ? ? ? ? ? A.imode = 3; // CW-N
? ? ? ? }
? ? ? ? if (((replystr[8] & 0x40) == 0x40) &&
(A.imode == 4)) {
? ? ? ? ? ? A.imode = 5; // AM-N
? ? ? ? }
------------------------
|
Re: Guide to New Rig backend creation?
Dave,
Look at src/Makefile.am
# Sources that we build. It is OK to have headers here.
flrig_SOURCES += \
??????? rigs/rigbase.cxx \
??????? rigs/rigs.cxx \
??????? rigs/elad/FDMDUO.cxx \
??????? rigs/elecraft/K2.cxx \
??????? rigs/elecraft/K3.cxx \
??????? rigs/elecraft/KX3.cxx \
??????? rigs/elecraft/K4.cxx \
??????? rigs/icom/ICbase.cxx \
...
David
On 10/2/24 12:01, Dave, G?WBX via
groups.io wrote:
toggle quoted message
Show quoted text
Hi again.
Looking into this now.? But...
These steps mentioned by Dave 'HKJ...
How to add a new transceiver to flrig
(A)
? Two new files will need to be added:
??? . src/include/RIGFAMILY/NEWRIG.h
??? . src/rigs/RIGFAMILY/NEWRIG.cxx
Done OK.? (Blank for now...)
(B)
? Three files will need to be modified:
??? . Makefile.am
?????? add the references to the two new files
Unable to even find references to any existing rig files,
so at a loss what to add here.
(C)
??? . src/include/rigs.h
??? . src/rigs/rigs.cxx
?????? add the references to the new rig
Done, referencing the new rig's files created as the first
step(A)
? RIGFAMILY might be icom, yaesu, elad, etc.
? NEWRIG might be IC-9999, FT-9999, etc.
Understood, but see above.
Suggest using an existing rig (.cxx, .h) files as
a template for
the new rig.? Choose a file that will use similar CAT
commands.
After the new files have been added and the three files
updated
you will need to recreate the build scripts.? From the top
level
flrig directory:
? $ autoreconf
? $ ./configure
? $ make
David
What exactly do I add to makefile.am?? As above,
there is nothing there I can see, that references other rig files
in an obvious way.
All that is in there at present, is :-
ACLOCAL_AMFLAGS = -I m4
SUBDIRS = src
if DARWIN
appbundle:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif
if HAVE_NSIS
nsisinst:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif
#EXTRA_DIST = build-aux/config.rpath
That to me, looks more like what platform to build
for, not what sources to build from..
Or (again) have I missed something?
73.
Dave G0WBX.
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable
#flrig
I tried your changes.
It seems to revert to the incorrect operation before the changes I submitted.
I don't see how your case statement can work for the modes. The only valid numbers in byte 6 are 0, 1, 2, 3, 4.
You use case numbers based on byte 6 ranging from 0 to 7 which correspond to the menu, but doesn't correspond to the data from the rig on byte 6.
For example, CW is 2 whether or not it is wide or narrow. In the menu, the numbers are 2 and 3 respectively.
?
So, I reverted to my version of FT890.cxx which worked for all of the non-narrow modes and added if statements to fix the narrow modes.
vfo-a now works correctly on all modes. Maybe you can do it in a better way or make any corrections.
I did not make the changes for vfo-b.
------------------------
? ? ? ? switch (replystr[6] & 0x07) {
? ? ? ? ? ? case 0: A.imode = ((replystr[6] & 0x40) == 0x40) ? 1 : 0; break; // LSB
? ? ? ? ? ? case 1: A.imode = ((replystr[6] & 0x40) == 0x40) ? 3 : 1; break; // USB
? ? ? ? ? ? case 2: A.imode = ((replystr[6] & 0x80) == 0x80) ? 5 : 2; break; // CW
? ? ? ? ? ? case 3: A.imode = ((replystr[6] & 0x80) == 0x80) ? 7 : 4; break; // AM
? ? ? ? ? ? case 4: A.imode = ((replystr[6] & 0x80) == 0x80) ? 9 : 6; break; // FM
? ? ? ? ? ? default: A.imode = 0;
? ? ? ? }
?
// After the base mode has been determined, we need to check for the narrow filters.
// We need to verify the base mode, as the narrow mode bits remain on until changed.
?
? ? ? ? if (((replystr[8] & 0x80) == 0x80) && (A.imode == 2)) {
? ? ? ? ? ? A.imode = 3; // CW-N
? ? ? ? }
? ? ? ? if (((replystr[8] & 0x40) == 0x40) && (A.imode == 4)) {
? ? ? ? ? ? A.imode = 5; // AM-N
? ? ? ? }
------------------------
|
Re: Guide to New Rig backend creation?
Hi again.
Looking into this now.? But...
These steps mentioned by Dave 'HKJ...
How to add a new transceiver to flrig
(A)
? Two new files will need to be added:
??? . src/include/RIGFAMILY/NEWRIG.h
??? . src/rigs/RIGFAMILY/NEWRIG.cxx
Done OK. ? (Blank for now...)
(B)
? Three files will need to be modified:
??? . Makefile.am
?????? add the references to the two new files
Unable to even find references to any existing rig files, so
at a loss what to add here.
(C)
??? . src/include/rigs.h
??? . src/rigs/rigs.cxx
?????? add the references to the new rig
Done, referencing the new rig's files created as the first
step(A)
? RIGFAMILY might be icom, yaesu, elad, etc.
? NEWRIG might be IC-9999, FT-9999, etc.
Understood, but see above.
Suggest using an existing rig (.cxx, .h) files as a
template for
the new rig.? Choose a file that will use similar CAT commands.
After the new files have been added and the three files updated
you will need to recreate the build scripts.? From the top level
flrig directory:
? $ autoreconf
? $ ./configure
? $ make
David
What exactly do I add to makefile.am?? As above,
there is nothing there I can see, that references other rig files in
an obvious way.
All that is in there at present, is :-
ACLOCAL_AMFLAGS = -I m4
SUBDIRS = src
if DARWIN
appbundle:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif
if HAVE_NSIS
nsisinst:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif
#EXTRA_DIST = build-aux/config.rpath
That to me, looks more like what platform to build
for, not what sources to build from..
Or (again) have I missed something?
73.
Dave G0WBX.
--
Created on and sent from a Unix like PC running and using open source software:
|
Andy's Ham Radio Linux: v26b-beta has been RELEASED!
Hi Everybody,
There has been a LOT of interest in these most recent versions of AHRL.? Thank you for your support!
v26b-beta is out.? I've added a bunch of programs for the ARRL Teachers Institute, including their own menu.? Those programs also appear in other menus as appropriate.? Many of those programs are SDR related.? They work for me but please try them and let me know.
I've tested this on several flavors of Ubuntu Linux 24.04.1 as well as Debian 12.7.0 (XFCE) and Linux Mint 22 (Cinnamon).
WORKAROUND: for some reason, the audio occasionally gets into a state where only the Dummy Output appears.? I've seen a LOT of postings about this for various flavors of Ubuntu Linux.? I'm pretty confident that this is not specific to AHRL.? If this happens, I've created a script to workaround the issue.? /usr/local/bin/fix_sound OR look in the Workarounds menu.? If somebody finds a definitive fix, please let me know.
Here's the link:
Don't forget to read the GETTING_STARTED document.? :-)
Have fun and 73,
Andy
KB1OIQ ..
|
Dave, W1HKJ