[Lazarus] [Lazarus 0012254]: Code tools bug: with Code completition

[Mattias Gaertner]

On Fri, 3 Oct 2008 14:49:42 +0100
"Henry Vermaak" <henry.vermaak at gmail.com> wrote:

>[...]
> >> what i should probably explain is that these units don't get
> >> compiled, since they are already built and the ppu/o files are in
> >> a directory i specified under "Other Unit Files" in the compiler
> >> options.
> >
> > Please run the project / compiler options / test. Does it show
> > warnings / errors?
> 
> no warnings (except duplicate ppu for apache units in fpc), the
> project builds fine.  it's a similar situation as with fpc having its
> compiled units in one place, and the source in another.

Pretty normal.

>  so i specify
> the unit dir as /path/to/compiledunits/$(TargetCPU)-$(TargetOS),

The macros are normal. But this looks like an absolute path. Maybe you
meant compiledunits/$(TargetCPU)-$(TargetOS), relative to your package?


> and i
> specify the path to all the source so the ide can find it for
> completion, etc.

What do you mean with specify?
In lazarus you use packages to specify paths. You hardly write paths
yourself in the edit/combo boxes of the IDE.

 
> it just seems to be that it doesn't find the source if it's in a
> different directory to the source of the unit you are clicking on
> (does that make sense?).

You can see the search paths via source editor / popup menu / file
settings / unit info. The 'unit path' is given to the compiler, the
'source path' is an addition for the IDE. Both are normally defined by
the compiler options.

Are you using a package?
Can you give some more details, what you want to do?


Mattias