On Sat, 02 Feb 2013 15:07:51 +0000 Mark Morgan Lloyd <[email protected]> wrote:
> Mattias Gaertner wrote: > > >>> Set a breakpoint in TCustomFrame.Create and single step to see what is > >>> executed. > >> I'm still trying to look at this, but a side question if I may. Could > >> this be caused by the fact that one of the directories is accessed via a > >> symlink? I notice that the IDE doesn't much like this, with extra tabbed > >> panes being opened whenever there's a compilation error and the risk of > >> "file changed on disk" inconsistencies if I don't force a manual save. > > > > Symlinked files are a problem. > > I've never tried that. > > > Symlinked directories are only a > > problem, if you use both paths in the same project. > > I'm definitely not doing that, and they're definitely a problem. I've > got a tree like > > /usr/local/src/inifiles > /usr/local/src/inifiles/trunk > > /usr/local/src/heavywethers > /usr/local/src/heavywethers/trunk > /usr/local/src/heavywethers/inifiles -> /usr/local/src/inifiles > > with the project only referring to ../inifiles/trunk: > > <SearchPaths> > <IncludeFiles Value="$(ProjOutDir);$(LazarusDir)\ide"/> > <OtherUnitFiles Value="..\inifiles\trunk"/> > </SearchPaths> The relative path "../inifiles/trunk" is passed absolute to the compiler. If for example your project directory is /usr/local/src/heavywethers/trunk the IDE passes -Fu/usr/local/src/heavywethers/inifiles/trunk to the compiler. Mattias -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
