Use FPC from command line is easy if you're not using the LCL (the
Lazarus Component Library).
If you're using the LCL they explained in the other answers, but if you
just use the RTL then the easiest way is just calling FPC from the
same directory you have the sources:
~$ fpc theprogram
That wi
How can I provide functionality for chdir, mkdir etc. ? The current
implementation in freertos/sysdir.inc
is hard coded with IO errors, is there a way to override the default
implementation?
I have implemented RTL file handling functionality by assigning the
rtl_do_* procedural variables.
Should
On Mon, 16 Dec 2024 15:06:45 +0100, Bo Berglund via fpc-pascal
wrote:
>On Mon, 16 Dec 2024 14:19:56 +0100 (CET), Michael Van Canneyt via fpc-pascal
> wrote:
>
>>
>>
>>On Mon, 16 Dec 2024, Bo Berglund via fpc-pascal wrote:
>>
>>> I have written a command line utility program on Linux using Lazarus
On Mon, 16 Dec 2024 14:19:56 +0100 (CET), Michael Van Canneyt via fpc-pascal
wrote:
>
>
>On Mon, 16 Dec 2024, Bo Berglund via fpc-pascal wrote:
>
>> I have written a command line utility program on Linux using Lazarus as the
>> IDE.
>> This was done a while ago on an Ubuntu Desktop 20.04 machine
On Mon, Dec 16, 2024 at 2:21 PM Bo Berglund via fpc-pascal
wrote:
> Can this be done and in that case how?
Yes, of course it can be done.
Lazarus IDE just calls the compiler with the correct parameters ;-)
If you happen to have a compiled version of lazbuild on the computer
in question it's ea
On Mon, 16 Dec 2024, Bo Berglund via fpc-pascal wrote:
I have written a command line utility program on Linux using Lazarus as the IDE.
This was done a while ago on an Ubuntu Desktop 20.04 machine, which I normally
access using VNC when doing Lazarus work there.
Now since a few months the Ti
I have written a command line utility program on Linux using Lazarus as the IDE.
This was done a while ago on an Ubuntu Desktop 20.04 machine, which I normally
access using VNC when doing Lazarus work there.
Now since a few months the TigerVNC server on that machinbe won't start anymore
so I canno
On Sun, 15 Dec 2024, Sven Barth via fpc-pascal wrote:
Which I paraphrased loosely as:
"It's not because something is in the pascal standard, that FPC has it."
As with any of the language dialect compatibility modes the point is that
FPC can compile code in that dialect, but *not* that cod
