On Wed, 15 Aug 2007, Graeme Geldenhuys wrote:
> On 15/08/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> > > In the mean time I grep searched all the FPC src and couldn't find
> > > such a function. For now I implemented some $I included file trickery
> > > to avoid IFDEF's in my code.
> >
On 15/08/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> > In the mean time I grep searched all the FPC src and couldn't find
> > such a function. For now I implemented some $I included file trickery
> > to avoid IFDEF's in my code.
>
> You must have missed
>
> fpReadLink
My search string ha
On Wed, 15 Aug 2007, Graeme Geldenhuys wrote:
> On 15/08/07, Vincent Snijders <[EMAIL PROTECTED]> wrote:
> >
> > If you cannot find it in the RTL, consider submitting ReadAllLinks from the
> > LCL's
> > fileutil unit to the FPC team. At least it doesn't depend on libc
> > (directly).
>
> Than
On 15/08/07, Vincent Snijders <[EMAIL PROTECTED]> wrote:
>
> If you cannot find it in the RTL, consider submitting ReadAllLinks from the
> LCL's
> fileutil unit to the FPC team. At least it doesn't depend on libc (directly).
Thanks Vincent. I'll go have a look.
In the mean time I grep searched a
Graeme Geldenhuys schreef:
Hi,
Is there a function in SysUtils or some other place in RTL that I can
use to extract the target path of a symlink file? I'm using
FindFirst/FindNext. The sr.Attrib and faSymLink is True, but I can't
(in a easy way) see how I can actually find out where it points
Hi,
Is there a function in SysUtils or some other place in RTL that I can
use to extract the target path of a symlink file? I'm using
FindFirst/FindNext. The sr.Attrib and faSymLink is True, but I can't
(in a easy way) see how I can actually find out where it points to.
I'm thinking x-platform h
