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 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
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).
I get the following error when trying to install “lazmkunit” or
“gecko” using fppkg.
===
C:\lazarus\fpc\2.6.0\bin\i386-win32>fppkg install lazmkunit
An unhandled exception occurred at $004377D5 :
EProcess : Failed to execute fpc.exe -iVTPTO : 2
$004377D5
$0040F953
$00
When I need a variation in procedures (standalone, not a class or
object procedure) I use across my applications, I often find it more
convenient to create a copy the unit into the project folder and make
the changes there. Sometimes they get merged back into the shared unit
or not at all.
I am th
