On 5/10/09, chris at cnpbagwell.com <chris at cnpbagwell.com> wrote: > The following commit has been merged in the master branch: > commit 4d9e8138af0f399e72599631854fa266cb18a4da > Author: chris at cnpbagwell.com <chris at cnpbagwell.com> > Date: Thu May 7 22:06:20 2009 -0500 > > standardize including local sane/ include files. > > Source code was inconsistent on how they were referencing > include files in include/sane. In certain cases, sane/sane.h > and sane/saneopts.h was really including external copies (with > some preprocessor implementations anyways). >
Could you please describe in what matter using relative paths to header files (eg. #include "../include/sane/sane.h") is better in comparision with -I../include command line option? Just to have cleaner picture... -- Ilia Sotnikov
