On 10/20/2012 5:01 PM, andy pugh wrote: > Here is a funny one. > The mesa_7i65.comp file contains: > include "../../../hal/drivers/mesa-hostmot2/hostmot2.h"; > > This pattern is needed because the generated C code is compiled > somewhere other than where the .comp file resides. > > This works fine during "make", but if you want to comp --install the > file instead, then you need > include "../../hal/drivers/mesa-hostmot2/hostmot2.h"; > ie, crawl back one level fewer. > > This probably doesn't matter, as nobody really needs to comp --install > that file, but it does lead to me wondering if there is a more robust > way of finding hostmot2.h > (some macro-defined absolute path, perhaps?) >
Andy: Certainly there are tricks that can be played (just look at all those -I directives issued to gcc in the process) but this behavior may be indicative of a more fundamental problem. Have you noticed that trying directly to compile most *any* comp file in src/hal/drivers fails? e.g., cd src/hal/drivers comp --compile pluto_servo.comp also fails. Lots of lines of error messages but the first one complains it can't find the include file just as in the case of compiling mesa_7i65.comp. I can't say more before I spend some time digging around. Perhaps someone else will beat me to it. Regards, Kent ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
