Raspberry PI 4 and cqrlog

5 posts / 0 new
Last post
oh1kh
Raspberry PI 4 and cqrlog

Today I started my new rpi 4b for first time.

I downloaded Raspberry Pi OS with desktop Release date: January 11th 2021. This is the one with minimal setup with desktop.
After I got network up I opened command console and issued:
sudo apt-get update

When it was finished next command was:
sudo apt-get install cqrlog lazarus git
The "git" is already installed so it is actually not needed. Installing lazarus will add many other needed packages to install list.

Installation started from cqrlog and that was ready very quickly.
While the "lazarus"-part of apt-get was still running I started cqrlog from start menu. It started version 2.3.0 and said that it seems that I have not used cqrlog before and offered to use local machine for logs.I said "yes".
After a while log001 was ready and I opened it. Then DXCC and QSLmgr lists were updated.
Everything worked fine so far.

While "lazarus"-part of apt-get was still running I opened another command console and cloned cqrlog source from Petr's github with command:
git clone https://github.com/ok2cqr/cqrlog.git

After cloning was ready also apt-get finished.
I changed to cloned cqrlog directory with command:
cd cqrlog
Then I issued command to compile latest source:
make
After that it was time to install new cqrlog with command:
sudo make install

Then I2021-02-20 Ver:2.5.2(001)

I do not know what I am doing wrong but again this whole operation could not be any easier.
This rpi4 is really fast compared to my old rpi 1 model.

oh1kh
Raspberry PI 4 and cqrlog keeping up to date

Today I noticed that there were new commits in cqrlog source when visiting https://github.com/ok2cqr/cqrlog/commits/master

So it is time to put rpi4's cqrlog up to date.
From earlier message I did clone the source to folder cqrlog under my user folder /home/pi.

So I closed cqrlog, opened again user command console (it defaults to user home dir, in this case /home/pi ) changed directory:
cd cqrlog
Then issued command that gets new updates from git:
git pull
After that new compile must be done with command:
make
When compile was ready it was time to install new cqrlog:
sudo make install

And latest version of cqrlog was again ready for use.
This same procedure can be repeated every time there has been new commits for source code. You do not need to visit the GitHub web page, just open console and change to cqrlog directory and issue git pull command. It tells you "already up to date", or shows what changes it has loaded.
If "already up to date" there is no need to compile and install at that time and you can do new check some day later.

What I have written here about raspberry pi can be used also with other debian based linuxes.
Commands are just same with Ubuntu and Mint so this can be used as guide also for them.

There is no need to wait for package managers to make their new packages ready.

--
Saku
OH1KH

ik0dwj
ik0dwj's picture
Now I also know how to use "git".

Hi Saku!

Thank you very much for the information on using "git". It will be very useful.

--
Giuseppe
IKØDWJ

ik0dwj
ik0dwj's picture
The cqrlog.git is also designed to compile cqrlog in mode debian

The cqrlog.git clone is also designed by Petr to compile cqrlog in mode debian so the installation will be controllable from its management system packages.
This is a double benefit for me using debian because I also have the latest version with bug fixes before its official release.
I am very satisfied.

73

--
Giuseppe
IKØDWJ

oh1kh
Raspberry PI 4 and cqrlog keeping up to date

HI!

For those who do not want to compile I have added official version for Arm (RPi) to my Alpha test pages. This version is compiled directly from Petr's current source and do not have any alpha test additions.

Download, unzip and start "newupdate" from https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled and select #3 for Arm (Rpi) update.
Script was tested with my RPi4b and works.

With RPi it is good practise to duplicate SD card (as backup) before doing any changes.

Read and understand README.md from page before starting "newupdate" !!

--
Saku
OH1KH