Everything posted by Upkeep
-
New Maps for LNM (update #4)
Thanks Alex. I saw this but as you say it seems to refer to a just single layer map. The example dgml file they give in a link has a warning line about possible malicious code, so I avoided looking at it. I will keep experimenting! best wishes
-
New Maps for LNM (update #4)
I hope someone might be able to help me. I have some slippy tiles downloaded and zoom level 6 to 12. I would like to be able to display these on LNM as offline maps. Not online. I have created the appropriate folder to go in the map/earth folder - 0 folder, dgml file, icon. Have read the manual to get an idea of how to change it for offline but have failed to get a result. I have also looked at the ‘example’ in LNM map folder and have removed references to urls to get the map listed as offline in the LNM map menu. I cannot seem to amend the commands in the dgml file to accommodate an offline map. It is currently intended for downloading tiles online. Also I am not sure where to put the offline slippy tiles so LVM will find them. I was wondering if anyone had an example of an offline dgml file or could give advice on exactly how to change the online dgml file to get local slippy tiles displayed. many thanks.
-
LNM on Raspberry Pi 4. How to compile.
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 🙂 Thanks again. Best wishes
-
LNM on Raspberry Pi 4. How to compile.
Success! Have been able to compile it now. The answer was that instead of: export ATOOLS_NO_CRASHHANDLER=TRUE I used the command from your original build script: export ATOOLS_NO_CRASHHANDLER=${ATOOLS_NO_CRASHHANDLER:-"true"} I have no idea what the difference is between the two but this did work - before Atools and LNM as you mentioned. Thank you again for your help. Regards
-
LNM on Raspberry Pi 4. How to compile.
Thanks, Alex. Have now reverted to 3.0.8 on Pi which works perfectly. I notice there is no crashhandler files in the stools/Sri/utility directory for that version. Thanks for trying to sort things out Regards
-
LNM on Raspberry Pi 4. How to compile.
Sorry Alex. Missed your question. qmake version 3.1, qt version 5.15.8
-
LNM on Raspberry Pi 4. How to compile.
Thanks Alex. Tried again. So, I started with a different Raspberry Pi running standard 64 bit OS. I deleted the cache and deleted the build-atools-release folder from an earlier attempt. I downloaded a new version of Atools from the link you just sent and checked crashhandler file was the same. I then tried to compile starting with the export no crashhandler command first and then the usual commands Exactly the same problem. Would not compile. So went to atools/src/utils and changed the two crashhandler file names and re-ran commands. Again, no luck. I think that probably is the end of this exercise and I will therefore revert to earlier, non-crashhandler version for the Pi. I am very grateful for your help, but I do not want to annoy you by constantly coming back to you with queries! Thanks again. P:S: The latest version runs on Windows fine - so I will mostly use that going forward. It is such an excellent piece of software. Thank you.
-
LNM on Raspberry Pi 4. How to compile.
Thanks Alex. Removed line from .bashrc as suggested. Then ran the following in terminal: export ATOOLS_NO_CRASHHANDLER=TRUE echo command gives TRUE. So OK Then: cd $APROJECTS mkdir build-atools-release && cd build-atools-release qmake ../atools/atools.pro CONFIG+=release make -j4 This produced the same result - compiling failed, same reason given. So, attempted to rename cpptrace files in Atools but could only find two files in atools/src/utils. So I renamed them. Ran all the commands again and got the following during qmake: ...... Project MESSAGE: QT: core gui sql xml core network svg widgets Project MESSAGE: ----------------------------------- WARNING: Failure to find: src/util/crashhandler.cpp WARNING: Failure to find: src/util/crashhandler.h Continued with make -j4 command anyway: ............ Xml -I/usr/include/qt/QtNetwork -I/usr/include/qt/QtCore -I. -I. -I/usr/lib/qt/mkspecs/linux-g++ -o contextsaver.o ../atools/src/util/contextsaver.cpp make: *** No rule to make target 'src/util/crashhandler.cpp', needed by 'crashhandler.o'. Stop. make: *** Waiting for unfinished jobs.... I am grateful for your help, but I really don't want to take up all your time. It is not fair! Will understand if you want to close thread now. All the best
-
LNM on Raspberry Pi 4. How to compile.
Thanks again, Alex, for your help. And the very quick response. I tried what you sugggested and sadly Atools still did not compile. Same problem. This is what I did: 1. Inserted at the end of .bashrc file in the home folder export ATOOLS_NO_CRASHHANDLER=TRUE 2. Saved file and rebooted. 3. Typed following command in terminal: cd $APROJECTS mkdir build-atools-release && cd build-atools-release qmake ../atools/atools.pro CONFIG+=release make -j4 4. Compilation halted: ../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 I am grateful for your help and you have spent enough time trying to sort this. Maybe the new version of LNM will not longer work on the Pi and I will now revert to the old version. Thanks again.
-
LNM on Raspberry Pi 4. How to compile.
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
-
LNM on Raspberry Pi 4. How to compile.
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
-
LNM on Raspberry Pi 4. How to compile.
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?
-
LNM on Raspberry Pi 4. How to compile.
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
-
LNM on Raspberry Pi 4. How to compile.
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
-
LNM on Raspberry Pi 4. How to compile.
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
-
LNM on Raspberry Pi 4. How to compile.
Thanks very much for the quick reply, Alex. To answer your question. I do appear to have the latest OpenSSL. It is listed as 1.1.1n. Deleting the entries suggested in your post does work and LNM deploys and opens as usual. So that’s fine. Thanks for that. I will remember this for future updates. The problem may or may not result from the fact that the RPi does not appear to have a /usr/lib/x86_64-linux-gnu folder. In the RPi, I think the corresponding folder is arm-linux-gnueabihf, which also appears in /usr/lib. Anyway, thanks very much for sorting this out and for producing such a wonderful piece of software of course. It is indispensable. all the best upkeep
-
LNM on Raspberry Pi 4. How to compile.
Thanks very much for the new update: 2.8.8. I am having a bit of a problem installing the new 2.8.8. version on my Raspberry Pi (previous versions including 2.8.7 were fine). I always follow the earlier instructions on this thread and they usually work successfully. The problem with 2.8.8. comes in the Deploy stage of the instructions. It is almost certainly down to the changes made in the latest version concerning OpenSSL and mentioned in the Changelog, as it stops during the creation of the 'lib' folder and produces the following message in the console: cp: cannot stat '/usr/lib/x86_64-linux-gnu/libssl.so.1.1': No such file or directory make: *** [Makefile:1385: deploy] Error 1 When I then look at the 'lib' folder within the 'deploy' folder, it is incomplete with a lot of files missing and therefore LNM won't open. However if I copy the whole lib file from a previous version and add the missing files it works fine. I have checked and have the latest OpenSSL and the Pi is fully updated and on the latest software. Any help would be very much appreciated. Thanks very much. Best wishes Upkeep
-
Problem with resizing images from FSLTL for FPS saving
Thanks for your help, toby23. And for your advice. Yes, Ordenador does work for me without the dll. Thanks again for explaining.
-
Problem with resizing images from FSLTL for FPS saving
The tutorial is immensely helpful, and very clear to follow. Thank you for your hard work on this - it brings all the very useful advice in this thread into one place. A bit of a puzzle: I just ran the XnViewMP section only and reduced the textures to 2048 and they seem to work very well. I did not run Ordenador and the second section of the tutorial concerning MiMaps as I was a bit reluctant to download a .dll (rightly or wrongly I have tended to avoid this in the past), which I am sure I would need as I have Win64 not 32. Admittedly I have only tried a few airports, but all seem to show the liveries OK. I wonder if anyone has had this experience? Maybe if I try a specific airport I will find the liveries with errors? Anyway, thanks again for the tutorial - it certainly helps to reduce the space taken and offers fps improvements as well..
-
LNM on Raspberry Pi 4. How to compile.
Many thanks Sten. I have amended the script as suggested and will try it for the next update. Thanks again. Best wishes Upkeep
-
LNM on Raspberry Pi 4. How to compile.
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
-
LNM on Raspberry Pi 4. How to compile.
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
-
LNM on Raspberry Pi 4. How to compile.
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