[Lazarus] When debugging, it open multiple copies of the same file

[Mattias Gaertner]

On Mon, 6 Jun 2011 13:02:41 +0200 (CEST)
michael.vancanneyt at wisa.be wrote:

> 
> 
> On Mon, 6 Jun 2011, Mattias Gaertner wrote:
> 
> > On Mon, 06 Jun 2011 12:31:15 +0200
> > Graeme Geldenhuys <graemeg.lists at gmail.com> wrote:
> >
> >> On 06/06/2011 12:10, Mattias Gaertner wrote:
> >>>
> >>> Maybe you use symlinks?
> >>
> >> Ah, I do have some directory symlinks - never file symlinks though.
> >> eg:
> >>
> >>   $HOME/prog/3rdParty/onguard/        ->   /opt/git/onguard.git/
> >>   $HOME/prog/3rdParty/tiOPF2/Source/  ->   /opt/git/tiopf_svn.git/
> >>
> >>
> >> I always reference the files inside the 3rdParty/* directories, never
> >> the symlink target location (/opt/git/*). So I guess Lazarus IDE doesn't
> >> work too well with symlink'd directories then. I guess I can shuffle my
> >> directories around and see if that solves the problem. Thanks for the hint.
> >
> > Lazarus is mostly symlink agnostic. For example /A/unit1.pas
> > and /B/unit1.pas are different files, even though they may be the same
> > through symlinks. This is needed, because all search paths are relative.
> 
> Isn't it planned to make references to used packages absolute ?

No. Packages are referenced by their name or by relative file names.


> Or better, is there a reason why you would not make them absolute ?

You can work with a project on multiple computers.


> To me, it makes no sense to refer to external packages using relative
> references. I often have problems because of symlinks.

I'm not sure why you come up with packages. This thread is about files
in general.

 
> I can understand that within a package/project you use relative references;
> you can then move a package/project, and it will continue to work.

Yes.

 
> But when moving one package, any link to it will be broken,
> whether it is relative or absolute. Since an absolute link 
> avoids symlink problems, their use seems preferable to me.

Moving a package without telling the IDE is the same as moving a
file in a project without telling the IDE: asking for trouble.
The solution is simple: tell it.
In case of a package it is ridcully easy: Just open the lpk file.

Mattias