Re: #include <sane...> instead of "sane..."

From: Petter Reinholdtsen (pere@hungry.com)
Date: Tue Oct 31 2000 - 21:42:24 PST

Next message: Petter Reinholdtsen: "Re: sane-config"

Previous message: Sébastien Sablé: "Re: [snapscan] Testing Agfa 1212U"
Maybe in reply to: Henning Meier-Geinitz: "#include <sane...> instead of "sane...""
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[Oliver Rauch]
> As far as I know it is not defined in which order the directories
> specified with "-I" and the system include directories are searched.
> (I know some users had problems because of that).

Eh, I am pretty sure they are searched in the order they are specified
on the command line. A simple test shows this to be true on Linux /
GCC at least. I believe this to be true for all Unix C compilers, and
probably all sensible C compilers. Where did users have problems
because of another include search order?

I suggest making sure "-I../include/sane " is the first -I statement
when compiling, and leave it at that.

-- ##> Petter Reinholdtsen <## | pere@td.org.uit.no

-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

Next message: Petter Reinholdtsen: "Re: sane-config"
Previous message: Sébastien Sablé: "Re: [snapscan] Testing Agfa 1212U"
Maybe in reply to: Henning Meier-Geinitz: "#include <sane...> instead of "sane...""
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Oct 31 2000 - 21:41:45 PST