Forum > Embedded
Lazarus Pascal cross compile Raspberry pi PICO
andrew Bubble:
Hi DonAlfredo
I have done as you have suggested and I still get the error when I open the project.
I have my VMWare running at the moment and a Raspberry PI 5 running bookworm and they both show the exact same error when opening a project.
One thing I am not sure of is when I have installed all the fpc, Lazarus and the cross complier are there any configuration / settings I need to do within Lazarus.
Regards Andrew
Thaddy:
There may be a Wayland issue, but noy for FPC, only for Lazarus.
But installed from fpcupdeluxe it simply works. Maybe you still have the hidden directories from a previous install? Do you know how to list hidden - dotted prefix in Linux? Did you clean up the fpc.cfg in /etc before a new install?
andrew Bubble:
Hi Thaddy
Thanks for the quick reply, I realised early on and it was time consuming but every time I tried something different on the raspberry PI I started from a fresh SD format and install of the OS Bullseye, Bookworm.
Then installed all the fpc, Lazarus and cross compiler.
On my VMware I had a clean install of Windows 10 and as I was using this for test purposes I did a snapshot within VMware before any installs.
The only difference is on the Raspberry PI due the issues I had I had to choose fpc Embedded and Lazarus V2.2.6,
On the Windows VMware I selected the PICO button on the bottom of fpcpdeluxe and just let it run until complete.
The first thing I did after both the installs is try to open one of the examples, and in both cases this was Blinky.
Regards Andrew
DonAlfredo:
The problem is caused by Lazarus.
To accommodate for all embedded options, like eabi, soft/hard, armv5/6/7/8, fpcupdeluxe places the compiled units in separate directories and used FPC macro-expansion to point FPC to the correct units. This is why compilation works.
Lazarus has some hidden auto-detect mechanism to see if the correct units are placed in the correct directory. However, Lazarus does not handle the FPC macros as it should.
To circumvent this, fpcupdeluxe creates a dummy system.ppu in the correct (according to Lazarus) directory. Somehow, this does not work anymore.
I need to have a closer look at this.
Thaddy:
Do
--- Code: Bash [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---ls -a -R | grep /. in your user directory. If you find .lazarus or similar, delete it before a new install.
Of course only delete .lazarus and similar, nothing else. Not all hidden files there are related to a lazarus install.
Actually on the Pi, this is enough:
--- Code: Bash [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---ls -a -R | grep /.lazarus
Also do not forget to delete /etc/fpc.cfg, but back it up first if you heavily editted it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page