Jump to content
Sign in to follow this  
smkr

LNM on Raspberry Pi 4. How to compile.

Recommended Posts

Hi all

Raspberry Pi has now released a new version of Raspios, "Bullseye"

You can again use the official Raspios to compile LittleNavmap!

I have updated the Littlenavmap-inst-RPI4_64Bit.txt to use this version!

use the link above to get the file.

Enjoy!!

Sten

 

  • Like 1

Share this post


Link to post
Share on other sites

I have found that these very helpful instructions are fine for LNM versions up to .18, but I am having difficulties with either .19 or the Development version.  Everything appears to go OK until I get to the command  'make deploy' right at the end, ie

 

git clone --single-branch --branch release/2.6 https://github.com/albar965/littlenavmap.git
mkdir build-littlenavmap-release && cd build-littlenavmap-release
qmake  ../littlenavmap/littlenavmap.pro CONFIG+=release
make -j4
make copydata
make deploy

It throws up a number of errors when this command is made, and LNM cannot be run.

I can of course list the errors (it would be quite long to present here) but if anyone has been successful compiling .19 for Raspberry Pi (Bullseye) it would be very helpful to know what needs to be changed in the script.

 

Thanks very much.

Upkeep

 

 

Share this post


Link to post
Share on other sites

Hi Upkeep

 

I have not yet tried to compile the .19 version. I have no time until tomorrow night.( Europe)

 

Regarding the 2.7.10, I have not tried to compile that. There seems to be changes in both Atools LNM dayly.

I will wait until there comes a released version.

 

br.

Sten

Share this post


Link to post
Share on other sites

There are often changes between LNM and atools. LNM is coupled tightly to the library. Make sure to use the right branches (master or release/3.6 atools and release/2.6 lnm).
LNM 2.7.X.develop resides on master. Use atools master branch for this.

You also need to compile Marble from the latest lnm/1.1 branch for LNM branch master since there were some changes 2.7 (or LNM branch master) depends on.

I can upload my Marble binaries if needed. Just let me know which OS.

Alex

Share this post


Link to post
Share on other sites

Thank you both for the very quick reply. Much appreciated.

First, I am running  Raspberry OS Bullseye 64 bit on a Raspberry Pi 4. All dependencies installed as per the instructions.

To compile I used the 2.6.19 Release version, Source Code zip file for LNM.  Lower down that page is the Development version 2.7, which I also tried.

For Atoolls there appeared to be no release version, so I downloaded the master. I am not sure what version this was as I could not see anything giving a version number. The most recent update appears to be in the src section and was made yesterday, while the rest of the files are older.

I have not had to compile Marble again during previous updates (just atools and LNM), so I have not tried doing it all from scratch, ie Marble Atools and LNM. I will try to do this but I am not sure where the latest Marble is - the one I can google is under albar965/marble but is six years old.

A link to the latest Marble and Atools (if I have the wrong one) would be very helpful. 

 

Thanks again for your help

Best wishes

Upkeep

Share this post


Link to post
Share on other sites

The branch master in Marble is six years old. Don't be confused by this. Changes are done on branch lnm/1.1 which received updates a few weeks ago.
This Marble branch lnm/1.1 is good for all current LNM branches which are release/2.6 and master.

As mentioned above: You have to combine the right branches:

  • LNM 2.7.10.develop was built with: littlenavmap master, atools master and Marble lnm/1.1.
  • LNM 2.6.19 was built with: littlenavmap release/2.6, atools release/3.6 and Marble lnm/1.1.

All branches have Git tags along the line which define a public release.

Downloading the Zip is ok but select the right branch before. Sources are normally always compilable on Linux or Windows.

Sorry, I just noticed that I don't have a Marble or atools version around for Raspi.

Alex

 

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

The doc I made require to compile Marble and Atools for every new version.

 

Sten

Edited by smkr

Share this post


Link to post
Share on other sites

Once again, thank you both for your help. I have tried again, this time using the correct files Alex stated above, and it does compile with no problems. It took a while on the Pi but it worked fine.

So thanks again for your assistance. I will make sure in future I get the right files, and compile from scratch.

All the best

Upkeep

  • Like 1

Share this post


Link to post
Share on other sites

I tested both version tonight! both without any problems.

 

To compile the developing version 2.7.** You only need to change 2 lines:

Change the line:

git clone --single-branch --branch release/3.6 https://github.com/albar965/atools.git to

git clone --single-branch --branch master https://github.com/albar965/atools.git

and change

git clone --single-branch --branch release/2.6 https://github.com/albar965/littlenavmap.git  to

git clone --single-branch --branch master https://github.com/albar965/littlenavmap.git

 

This way You don't need to download zip-files

good luck

 

Sten

 

 

 

  • Like 1

Share this post


Link to post
Share on other sites

Many thanks Sten. I have amended the script as suggested and will try it for the next update.

Thanks again.

Best wishes

Upkeep

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...