[Lazarus] Built console app on Linux, but won't run on another Linux machine

[Juha Manninen]

On Sat, Oct 27, 2018 at 7:11 PM Bo Berglund via Lazarus
<lazarus at lists.lazarus-ide.org> wrote:
> In the converted Delphi project I started with a .dpr file that
> contained all active code except for two units to read Ini files mor
> easily and to create Unix style hashed passwords. When it
> was done it still used the dpr file as the main program source.

I don't understand you. The converter creates a .lpr file for sure.


On Sat, Oct 27, 2018 at 7:20 PM Bo Berglund via Lazarus
<lazarus at lists.lazarus-ide.org> wrote:
> >If yes then use the Project Inspector, double click on the required
> >packages to see their dependencies. Or use Package / Package graph to
> >see the dependencies.
>
> This amazingly shows:
>   LCL
>   IDEIntf
>   FCL (>=1.0)
> But I think these are for the Lazarus IDE integration of the visual components
> and I am not using any forms or such so there is no use for this.

Indeed!
It is not only for the IDE integration. There are units with GUI that need LCL.


> Now I am at a loss as to how I can use Indy without bringing in
> IndyLaz, just the required files. On Windows it is simple, I just set
> the search path in Delpi to the location of the three Indy10 source
> directories and I am done.

You mean in Delphi it is simple.(?)
But no, actually the global search path in Delphi can be considered a
bug but they cannot remove it for backward compatibility.
It pollutes the namespace also for projects that do not need a
specific library/package.

> Not so simple in Lazarus until I saw I could install indylaz.
> Has worked fine for GUI applications so far....

Yes, Indy apparently suits best for GUI apps.
You can of course set the search path of your Lazarus project to point
to Indy source directories.
That is not recommended normally but this is a special case.
If Indy Lazarus port was well designed, it would separate the GUI and
non-GUI parts to their own packages.

Juha