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?) -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ 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
