Hello Helge,
The airframe.xml file is converted (using paparazzi parsers) to an include file (airframe.h) and a makefile (Makefile.ac). Both end up in the ~/var/YOUR_AC_NAME/ directory upon compile.
The first defines a lot of ... "defines" that are used in the code and has all the servo mixing.
The latter defines which files and extra compile options are actually compiled.
As a debugging help an extra file is created in the same directory with a list of all global defines and all actual source file names next to each other (since the Makefile.ac conditionally includes a lot of stuff itself): targetname_srcs.list
does this help?
-Christophe
Hello,
While my Paparazzi programs seem to work fine, I would like so much to get a better understanding of the workings of the airframe file.
Could anyone please give an example of how one can follow a section and its defines into the appropriate program(s)?
It would be nice if this example was made from the firmware section and ap target.
If this is explained in the wiki I will of course read that, but I have not found such reading yet.
Thanks,
Helge.
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel