>> https://bugs.freepascal.org/view.php?id=32367
> Maybe close out that bug then?
Or fix it (Martin gave all the keys how to do, even Florian agree with it) ?
-
Many thanks ;-)
--
Sent from: http://free-pascal-general.1045716.n5.nabble.com/
___
Maybe close out that bug then?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
https://bugs.freepascal.org/view.php?id=32367
-
Many thanks ;-)
--
Sent from: http://free-pascal-general.1045716.n5.nabble.com/
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
Anthony Walter schrieb am So., 12. Mai 2019, 20:42:
> Okay, so I need to install the dev versions of any package I want to link
> against. But when my program is distributed it will link at load time
> correctly to the non dev versions.
>
It links against the version the development version
Okay, so I need to install the dev versions of any package I want to link
against. But when my program is distributed it will link at load time
correctly to the non dev versions.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
Anthony Walter schrieb am So., 12. Mai 2019, 18:41:
> For example suppose I want to write some pascal code linking to an
> external functions like so:
>
> const
> libsdl2 = 'libSDL2-2.0.so.0';
>
> function SDL_Init(flags: Uint32): LongInt; cdecl; external libsdl2;
> procedure SDL_Quit; cdecl;
I'm am not sure how long I've ignored this problem, but can someone explain
to me the proper way to get FPC and Lazarus to allow linking of external
shared object files without the need to create "friendly" symbolic link
names FPC and Lazarus can see?
For example suppose I want to write some
