On Wed, 22 Aug 2007 10:07:29 +0200
Tobias Giesen <[EMAIL PROTECTED]> wrote:
> Hello,
>
> many thanks for your replies! I have found some interesting things
> that you pointed me too.
>
> However I think the cause is the relative search paths being sent to
> the compiler. The file that is not found is in the path ../units, and
> it was used by another file in ../units. The first file is found, but
> then another file in the same folder is not found.
Huh? Can you give more details?
> The error does not occur if the compiler encounters the file before
> it is used by a unit that's not in the main folder. For example, I
> have now added the unit to the top of the main program's uses clause
> and that has fixed the problem.
This sounds as if this unit exists twice.
Then the order of the compilation and search paths becomes relevant.
And this order depends on what units needs to be rebuild.
Build <> Build All.
This has nothing to do with relative vs. absolute paths, but how the
compiler searches for files.
> If we could choose absolute paths to be passed to the compiler, that
> would be great!
That would make no difference. Except that on some platforms the
command line would become too long.
Mattias
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
