Forum > Options
Raspberry with source directory on a windows share
sporex:
--- Quote from: MarkMLl on May 20, 2022, 11:08:25 am ---You might need to find a text editor that saves files with unix-style line endings. I /thought/ that the compiler was tolerant of variations there.
MarkMLl
--- End quote ---
But this cannot be the reason for the problem because the source file on the local file system has the same format:
--- Code: Pascal [+][-]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";}};} --- test0.pas: ASCII text, with CRLF line terminators
this test0.pas was written with the source editor on the windows LAZ, stored to /NAS and then transferred to the local file system of the RPi, and it compiles.
MarkMLl:
Hmm. Going back through the thread: I used ** to indicate a footnote and assumed you would understand that you had to enter something like
--- Code: ---file test.pas
--- End code ---
Is it /really/ showing test.pas empty after compilation?
MarkMLl
sporex:
Really, really. This is before compilation:
--- Code: Pascal [+][-]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";}};} ---pi@DEB11IDE:/NAS/TEST $ file ./test0.pas./test0.pas: ASCII text, with CRLF line terminators
And this is afterwards:
--- Code: Pascal [+][-]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";}};} ---pi@DEB11IDE:/NAS/TEST $ file ./test0.pas./test0.pas: empty
And this is the source on the local file system that compiles:
--- Code: Pascal [+][-]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";}};} --- pi@DEB11IDE:~/fpcsrc/TEST $ file ./test0.pas./test0.pas: ASCII text, with CRLF line terminators
MarkMLl:
Really, really odd :-|
Presumably you're building using the full IDE... what happens if instead you apply lazbuild to the .lpi (Lazarus project information) file?
I must say that mapping stuff like that wouldn't be my first choice: I usually use Subversion as the common point. Any idea what protocol is being used (check mount command output)?
Edited: incorrectly referred to .lpr file.
MarkMLl
sporex:
--- Quote from: MarkMLl on May 20, 2022, 01:11:18 pm ---Really, really odd :-|
Presumably you're building using the full IDE... what happens if instead you apply lazbuild to the lpr (Lazarus project) file?
I must say that mapping stuff like that wouldn't be my first choice: I usually use Subversion as the common point. Any idea what protocol is being used (check mount command output)?
MarkMLl
--- End quote ---
The mount result gives me this (for the share):
--- Code: Pascal [+][-]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";}};} --- //192.168.2.126/PINAS/RASPI on /NAS type cifs (rw,relatime,vers=2.1,cache=strict,username=pi,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.2.126,file_mode=0777,dir_mode=0777,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,bsize=1048576,echo_interval=60,actimeo=1)
And this is what I get for the Jessie IDE (where all is ok)
--- Code: Pascal [+][-]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";}};} --- //192.168.2.126/PINAS/RASPI on /NAS type cifs (rw,relatime,vers=2.1,sec=ntlmssp,cache=strict,username=pi,domain=P1W764,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.2.126,file_mode=0755,dir_mode=0755,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)
You know that I am not so deeply involved in the internals of Lazarus stuff but what I did so far was:
- create /NAS/TEST/test_abc on the LAZ_WIN IDE
- trying to conpile (Ctrl-F9) --> failed
- trying to Build (Shift-F9) --> failed
So I am loosing hope.
I can only confirm that I have a SD card image with Debian 8 (Jessie) and LAZ 1.2.4.dfsg2-1 where all this has worked perfectly for years now.
To compile to/from the win share is very convenient because I can edit under LAZ-WIN and compile/debug under LINUX arm and get the executable right back to the archive from where I can redistribute it to many other RPi units in the field.
Unfortunately I am forced to upgrade all RPi units now to Debian 11 (Jessie is end of life) and it seems that some of the executables that I create with the Jessie IDE do not run on the upgraded Bullseye units.
The majority of my applications are "SimpleProgram" without GUI. Only one uses GUI
I have to say that I am not interested to always have the most recent release of LAZ and that "compiling the IDE" "cross compiling" and such stuff is beyond my knowledge.
So my first choice would be to have a simple way to install version 1.2.4.dfsg2-1 (apt-get install ...) on the Bullseye image, provided that it creates executables that are running.
Navigation
[0] Message Index
[#] Next page
[*] Previous page