(...)
> I guess, you mean something like this:
> /path/project/unit1.pas
> /path/dir/unit2.pas
>
> - project's unit path points to unit2
> - unit2 is not part of the project or any package
> - unit2 uses the LCL
>
> => The IDE will not find the LCL units for unit2
>
(...)
>
> Fix:
> Add unit2 to a package and define, what it needs.
But shouldn't the CodeTools use a fallback and search the default
project or Lazarus settings when no defines are found for a file?
I am converting the current SynEdit code to Lazarus and was a bit lazy
to add all the files to project. In the end it's nothing that a bit of
CLI magic didn't resolve in a blink, but I find the behaviour odd
anyway...
> Reason:
> Every package and project define their own set of values/search paths. For
> example the FPC sources are world of their own and do not use the LCL.
> Every directory can contain 'defines'. A 'define' is for example the
> definition of the SrcPath. The 'defines' are defined by the 'templates',
> seen in the codetools defines editor. When you browse through the tree, you
> can see, that most of the values are created from the compiler or the
> compiler options of the packages and project. And some, like the FPC and
> Lazarus sources are hand made.
> You can add your own definitions, like adding the defintions for a Delphi7
> Source directory. There is a template for that in the menu.
>
Hmm ok. So the only use for it is defining - say - the "paths dependencies"?
I'll try to add something about it in the wiki to compensate for your
time and explanation :-)
Regards,
Flávio
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
