On 21 October 2012 17:01, Charles Steinkuehler <[email protected]> wrote:
> #include "hal/components/thermistors.h" > > ...which seems kind of odd, since the comp file resides in > hal/components along with the thermistors.h file. The issue here is that the c-code which is generated from the .comp file is _not_ kept in the same place as the .comp file. To further complicate matters it seems to end up in a different place when it is compiled with "make" than when it is compiled with "comp" > So...is there a reliable or recommended way of including *.h files in > *.comp components, There is an "include" command that can be used before the ;; delimiter in the comp file. You can also use a #include in the C-code after the ;;, but it tends to be too far into the code to include types (if, for example, you want variables in the "variable" section which are not built-in types). The comp "include" command puts a #include near the top of the generated C file. However, the "include" command is undocumented, probably because of the problems you are seeing. The place to fix all this is probably in the comp.py program, as that probably knows where it is putting the C-code, and ought to be able to repair the path. -- 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
