On 09 Apr 2012, at 16:28, Alan Krause wrote:
> Indeed. You can put the following in your .bashrc file:
>
> export LD_LIBRARY_PAH=.
Make sure to never do that on a multi-user system, or you open yourself up to
easy hijacking of your account (in the same way that adding "." to your PATH
does).
On 09/04/12 17:28, Alan Krause wrote:
Indeed. You can put the following in your .bashrc file:
export LD_LIBRARY_PAH=.
Not recommended security wise, especially that it is needed for testing
only.
Stephano
___
fpc-pascal maillist - fpc-pascal@lists
Indeed. You can put the following in your .bashrc file:
export LD_LIBRARY_PAH=.
Alan
On Sun, Apr 8, 2012 at 3:00 PM, Tomas Hajny wrote:
> On 9 Apr 12, at 0:42, patspiper wrote:
>
> > Is it possible to test a shared library compiled with Lazarus/FPC under
> > Linux without copying that library
On 09/04/12 01:00, Tomas Hajny wrote:
On 9 Apr 12, at 0:42, patspiper wrote:
Is it possible to test a shared library compiled with Lazarus/FPC under
Linux without copying that library to /usr/lib or fiddling with the OS
configuration to locate them?
Under Windows, it is enough to have the test
On 9 Apr 12, at 0:42, patspiper wrote:
> Is it possible to test a shared library compiled with Lazarus/FPC under
> Linux without copying that library to /usr/lib or fiddling with the OS
> configuration to locate them?
>
> Under Windows, it is enough to have the testing executable (host
> appli
Is it possible to test a shared library compiled with Lazarus/FPC under
Linux without copying that library to /usr/lib or fiddling with the OS
configuration to locate them?
Under Windows, it is enough to have the testing executable (host
application) in the same folder as the shared library. I
