Project options: include path seems to be ignored

[mgerwinski]

Hello,

when trying to compile the "dynamic_ambient occlusion" example program from the Kambi VRML Game Engine project in my IDE (Lazarus 0.9.30 on a Windows XP system), I always get a "Can't open include file" error.

Fair enough, but the error doesn't go away when I add the include file's path to the "Project options: include files" path and also the "units" path. I tried relative path and absolute path, to no avail.

Am I missing something here?

Thanks in Advance,

  Markus

[Blaazen]

Example:

Code: [Select]

{$INCLUDE include/draw.inc} will look to subdirectory include for a file draw.inc

In this case, I have in Project Options-> Include files this:

Code: [Select]

$(LazarusDir)/lcl/include;include
See also: http://www.freepascal.org/docs-html/prog/progsu37.html

Note: Linux is case-sensitive and path is without quotes.

[mgerwinski]

Example:

Code: [Select]

{$INCLUDE include/draw.inc} will look to subdirectory include for a file draw.inc

... relatively to the project options "include files" path, right?

The code line in the example project I'm trying to compile simply reads:

Code: [Select]

{$I kambiconf.inc}
On my machine, the file kambiconf.inc is located at C:\Tools\kambi_vrml_game_engine\src\base, so this is the path I inserted into the project options (no quotes or similar added).

Note: Linux is case-sensitive and path is without quotes.

I know, but as already mentioned: I'm working on Windows.

[marcov]

Includes in source are always relative to the working dir of the compiler.

[mgerwinski]

Includes in source are always relative to the working dir of the compiler.

OK, but what is the "include files" path option for, then, if it doesn't change this at all?

[marcov]

Includes in source are always relative to the working dir of the compiler.

OK, but what is the "include files" path option for, then, if it doesn't change this at all?

It is to supply includefile directories on the commandline. Not for partial path completion.

In general IMHO it is a good habit to never store paths in sources.

[mgerwinski]

It is to supply includefile directories on the commandline. Not for partial path completion.

In general IMHO it is a good habit to never store paths in sources.

Uh... sorry, but I'm not sure if you are understanding what I'm trying to do.

First: as I said, the source code in question isn't by me. It is an example code to a library I'm trying to work with.

Second: there is no path in the source. See my code snippet above. There is only the file name, without path.

Third: what, please, is an includefile directory if not a directory where to find include files??