From: EBo <eb...@sa...> - 2011-03-23 03:07:59
|
On Wed, 23 Mar 2011 00:45:07 +0000, andy pugh wrote: > (supplementary question) > > On 22 March 2011 21:54, Jeff Epler <je...@un...> wrote: > >> so for the >> moment it's easier to put them directly in src/hal/drivers. > > Making the #include work is a bit awkward. > the comp file is preprocessed into a c file, which is created in > src/objects/hal/drivers. > The hostmot2 header files are in src/hal/drivers. > > I have the following include (comp-format incude), but surely that > can't be right? > > include "../../../hal/drivers/mesa-hostmot2/hostmot2.h"; > > Is there a neat way to define an absolute path? Depending on what you mean by absolute path... #include "hal/drivers/mesa-hostmot2/hostmot2.h" and have the realization of TOP="../../.." added to the compiler defines as CFLAGS += "-I${TOP}" Other than that, it is a bad idea to write literal absolute paths in incloude arguments unless these are system standards. Hope that helps. EBo -- |