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, I haven't forgotten about this. I'm just distracted by real life. I'm getting a good feel now for what comp does and what make tells it to do (every problem is a learning opportunity in disguise). I have an alternative to your example include string that avoids making the component programmer know the details but I don't have an answer that works for all possible uses of comp, at least not yet. More about this later. Along the way, I've started composing additional material for the "Comp HAL Component Generator" chapter in the HAL manual (html version) aka "comp: a tool for creating HAL modules" in the pdf version. This material includes: 1) the missing declarations---include, notes, modparam---their syntax and what they do. 2) indications of where the resulting .c file ends up using various incantations. 3) the boilerplate, such as the rtai includes, that is always generated by comp. 4) a few typo fixes, notably of a mistake concerning where driver .comp files should be placed. Ta for now. 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
