Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

LNM on Raspberry Pi 4. How to compile.

Featured Replies

I'll see if I can make the OpenSSL part a bit simpler. Maybe add a configurable path.
You can check in the "About Little Navmap" dialog which versions are used. It won't work if the library is a OpenSSL version 3.

OpenSSL is included successfully if weather and map tile downloads work.

Alex

  • Replies 44
  • Views 17.2k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Very pleased to get it working.  I should have studied more carefully your original suggestion that I looked at the build release coding from the link you provided. So it is me who should apologise 🙂

  • Hi all   I have now uploadet a new version of how to compile and use Little Navmap on Raspberry Pi 4b! Because of the library change  It is not (yet) possible use the Raspberry pi 64 bi

  • 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

Thanks Alex. 'About Little Navmap' opens OK and I can see the references to OpenSSL. The Map Tiles also work. As far as simplifying OpenSSL is concerned, please don't do this just for me! I can easily make the changes you suggested each time I update.

Thanks again for your help.

Best wishes

Upkeep

  • Author

Hi

I have uploaded a new txt-document about this issue.

 

/Sten

 

2 hours ago, smkr said:

I have uploaded a new txt-document about this issue.

Where? I changed the *.pro file to use the SSL only if found (not committed yet):

  exists(/usr/lib/x86_64-linux-gnu/libssl.so.1.1) : deploy.commands += cp -vfaL /usr/lib/x86_64-linux-gnu/libssl.so.1.1 $$DEPLOY_DIR_LIB &&
  exists(/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1) : deploy.commands += cp -vfaL /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 $$DEPLOY_DIR_LIB &&

Alex

  • Author

 

I changed it to reflect this:

On 1/20/2023 at 4:43 PM, albar965 said:

You can also change the file littlenavmap.pro and remove the two lines:


  deploy.commands += cp -vfaL /usr/lib/x86_64-linux-gnu/libssl.so.1.1 $$DEPLOY_DIR_LIB &&
  deploy.commands += cp -vfaL /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 $$DEPLOY_DIR_LIB &&

In that case Qt will load any available SSL library version from the system.

/Sten

  • 1 month later...
  • Author

LNM 2.8.9 compiled and deployed without any trouble!

The txt file is slightly updated.

 

/Sten

  • 1 year later...

Having difficulty compiling the latest version of Little Nav Map for my Raspberry Pi 64 bit. All previous versions compiled OK on the Pi (using instructions posted below in this forum). Marble and Atools compilation went as planned, but during LVM compilation I get the following message:

make: *** No rule to make target '/xxxxx/xxxxxx/projects/littlenavmap/../build-atools-release/libatools.a', needed by 'littlenavmap'.  Stop.

Would be very grateful for some help or advice. Thanks very much for your help.

Best wishes Upkeep

 

3 hours ago, Upkeep said:

Having difficulty compiling the latest version of Little Nav Map for my Raspberry Pi 64 bit. All previous versions compiled OK on the Pi (using instructions posted below in this forum). Marble and Atools compilation went as planned, but during LVM compilation I get the following message:

make: *** No rule to make target '/xxxxx/xxxxxx/projects/littlenavmap/../build-atools-release/libatools.a', needed by 'littlenavmap'.  Stop.

Would be very grateful for some help or advice. Thanks very much for your help.

Is the file really missing? Hard to say. I'd need a full log file to see.

Have a look at the build scripts I use to make the releases: https://github.com/albar965/littlenavmap/tree/release/3.0/build/linux especially build_release.sh

There are a few environment variables which can be used to override paths in the script here: https://github.com/albar965/littlenavmap/blob/acbb2c54d05ee7209dfbde0797e456f5e8e78bf7/build/linux/build_release.sh#L26-L54
Also ignore the build part for Xpconnect later since this needs a static Qt build.

Alex

 

Thanks very much for the quick response, Alex. I will investigate further based on your reply. Will report back later.

 

many thanks for your help

I have now completed as number of attempts to compile but with no success. I think the problem for me lies with the compilation of Atools. I have tried both the Master and 4.0. I could not get 4.0 to complete compilation and the Master compiled fine but produced a file of around 50MB, when the previous one I used with the last LNM update was around 80MB (I think that was 3.8).

Anyway the result was when I tried to compile LNM itself after Atools it failed to comply because of missing files (presumably derived from a successful and full compilation of atools). I have tried cloning LNM, downloading the source code from the releases page (3.0.11), tried the main code page and downloaded release-3.0, but none worked. Again, I assume a Atools problem.

If it helps I can provide more detail on what the Terminal shows when compiling Atools 4.0 which I assume is the one to use.

I assume the correct files to compile LNM are Atools 4.0 and littlenavmap-release-3.0?

 

1 hour ago, Upkeep said:

I have now completed as number of attempts to compile but with no success. I think the problem for me lies with the compilation of Atools. I have tried both the Master and 4.0. I could not get 4.0 to complete compilation and the Master compiled fine but produced a file of around 50MB, when the previous one I used with the last LNM update was around 80MB (I think that was 3.8).

I'd need a log file of the compilation. Linux is normally the easiest to compile.

Alex

1 hour ago, Upkeep said:

Anyway the result was when I tried to compile LNM itself after Atools it failed to comply because of missing files (presumably derived from a successful and full compilation of atools). I have tried cloning LNM, downloading the source code from the releases page (3.0.11), tried the main code page and downloaded release-3.0, but none worked. Again, I assume a Atools problem.

If it helps I can provide more detail on what the Terminal shows when compiling Atools 4.0 which I assume is the one to use.

I assume the correct files to compile LNM are Atools 4.0 and littlenavmap-release-3.0?

The branches atools release/4.0 and littlenavmap release/3.0 are the right ones. 

You can send me an email with the log: https://albar965.github.io/contact.html
Alex

 

Thanks for your notes, Alex.

I tried it on a different Raspberry Pi with the same result. Atools 4.0 will not compile for me.

It stops during the process with the message:

../atools/src/util/crashhandler.cpp:45:10: fatal error: cpptrace/cpptrace.hpp: No such file or directory
   45 | #include <cpptrace/cpptrace.hpp>
      |          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:2583: crashhandler.o] Error 1
make: *** Waiting for unfinished jobs....

I am not sure where to find the log file you mention. I have tried /var/log but cannot see anything relevant.

Thanks again for your help

 

 

15 minutes ago, Upkeep said:

../atools/src/util/crashhandler.cpp:45:10: fatal error: cpptrace/cpptrace.hpp: No such file or directory
   45 | #include <cpptrace/cpptrace.hpp>
      |          ^~~~~~~~~~~~~~~~~~~~~~~

Set the environment variable ATOOLS_NO_CRASHHANDLER to "true" or install cpptrace.

Alex

Thank you Alex.  You have been very patient with me.

cpptrace does not seem to be available for a Pi. i have tried to work out how to set the environment variable you suggest but not sure how to. I am pretty much a beginner with this sort of stuff

At the moment I am using the following to compile:

cd $APROJECTS
mkdir build-atools-release && cd build-atools-release
qmake ../atools/atools.pro CONFIG+=release

make -j4

I have looked at the file atools.pro, but not sure how to change ATOOLS_NO_CRASHHANDLER=TRUE

Sorry to trouble you with such basic questions and thanks again for all your help

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.