search

wb2osz / direwolf

Dire Wolf is a software "soundcard" AX.25 packet modem/TNC and APRS encoder/decoder. It can be used stand-alone to observe APRS traffic, as a tracker, digipeater, APRStt gateway, or Internet Gateway (IGate). For more information, look at the bottom 1/4 of this page and in https://github.com/wb2osz/direwolf/blob/dev/doc/README.md
GNU General Public License v2.0
1.56k stars 305 forks source link

need CMakeLists.txt for version 1.5 #449

Closed wf5w closed 1 year ago

wf5w commented 1 year ago

I read somewhere there might be a bug in 1.6 for the problem I am having.

I am on Linux Mint 21, using a digirig [logic levels] ( a CM108 device )

I am in the following groups: groups=4(adm),5(tty),8(mail),20(dialout),21(fax),24(cdrom),27(sudo),29(audio),30(dip),46(plugdev),112(lpadmin),115(ssh),128(sambashare),131(vboxusers)

from the arecord -l, and using dmesg --follow

I have direwolf.conf appropriately configured as ADEVICE=plughw:3,0 PTT /dev/ttyUSB0 RTS

When running direwolf -p I get device or resource busy.

I went into alsamixer, chose my device, changed output to about 40, and mic to about 40 and found out there is also a L R Capture too (which I set to about 40 just to make sure)

Anyway, I stumbled on somebody who said it worked in 1.5 but doesn't in 1.6, so I thought I'd revert to 1.5 and try that out.

So I cloned Did a $ git reset --hard '1.5' Did a mkdir build && cd build Did a cmake .. (no CMakeLists.txt) So I reverted the head back to current version, copied out the the CMakeLists.txt from there, redid the 1.5, copied the CMakeLists.txt back in. And this time got errors

I would like to test 1.5, so where is the CMakeLists that works with tag 1.5?

Or am I doing this ALL wrong!

Jerry

wb2osz commented 1 year ago

Version 1.5 used multiple target specific manually constructed makefiles. Version 1.6 started using CMake to make multiple platforms easier.

There is no reason to go back to an earlier version that I know of. You can use the default 1.6 or the "dev" development branch which has many improvements.

There was recently someone using Linux Mint who found out that using a USB3 port was unreliable but a USB2 port was fine. Watch out for that.

What is the context of the "device or resource busy" error?

wb2osz commented 1 year ago

No response from originator for a couple months. Closing.