On Wed, 30 Sep 2020, Sven Barth via fpc-pascal wrote:
Lazarus is not Delphi. In Delphi this worked, because on Windows the GUI
libraries are always available and Windows doesn't care if you use UI
code in a "console" binary. On other systems (especially Linux and BSD)
this might not be the c
Am 27.09.2020 um 22:07 schrieb Bo Berglund via fpc-pascal:
On Sun, 27 Sep 2020 19:44:36 +0200, Sven Barth via fpc-pascal
wrote:
I am not using wsmenus...
Yes, you are, even if it is indirectly. Otherwise the compiler or linker
wouldn't complain about it.
It would be very good if the linker
On Sun, 27 Sep 2020 23:40:09 +0200, Bo Berglund via fpc-pascal
wrote:
>On Sun, 27 Sep 2020 22:07:16 +0200, Bo Berglund via fpc-pascal
> wrote:
>
>>The only required packages for my application now are:
>>LCLBase and indylaz. And if I remove LCLBase it still compiles OK but
>>also still fails the
On Sun, 27 Sep 2020 22:07:16 +0200, Bo Berglund via fpc-pascal
wrote:
>The only required packages for my application now are:
>LCLBase and indylaz. And if I remove LCLBase it still compiles OK but
>also still fails the link step.
I finally got it to compile!
What I did was to add Interfaces to t
On Sun, 27 Sep 2020 19:44:36 +0200, Sven Barth via fpc-pascal
wrote:
>> I am not using wsmenus...
>>
>
>Yes, you are, even if it is indirectly. Otherwise the compiler or linker
>wouldn't complain about it.
>
It would be very good if the linker could be told to show a message
saying from where th
Bo Berglund via fpc-pascal schrieb am
So., 27. Sep. 2020, 18:12:
> I am trying to find the cause of a linker error when building my
> application on Linux.
> While doing this I looked in the project file projname.lpi and found
> this strange entry:
>
>
>
>
>
>
>
> Why is the path d
I am trying to find the cause of a linker error when building my
application on Linux.
While doing this I looked in the project file projname.lpi and found
this strange entry:
Why is the path delimiter defined inside the project information file?
And what are th consequences when m
