Re: [Paparazzi-devel] Help needed in paparazzi source code makefiles

[Christophe De Wagter]

Since you are using the main_logger code you might be interested in:

airframe: https://github.com/paparazzi/paparazzi/blob/v4.0/conf/airframes/logger_sd.xml

This calls the "logger" firmware, which is defined in https://github.com/paparazzi/paparazzi/blob/v4.0/conf/firmwares/logger.makefile and compiles it for the tiny-2.11 board which in turn sets a lot of options using https://github.com/paparazzi/paparazzi/blob/v4.0/conf/boards/tiny_2.11.makefile.

On line 56 of logger.makefile you can see that indeed the mcu.c (microcontroller peripherals) are needed. 

Using this xml-based-makefile firmware/board structure we can put any code in any board which then calls the correct architecture files (provided some lowlevel drivers are present), and developers can restructure, move and combine files without any need for changes in airframe files. 

-Christophe 

On Wed, Oct 10, 2012 at 5:49 PM, Zhang Qiuchen <address@hidden> wrote:

Hello everyone,

My name is Autumn and I'm working on a paparazzi UAV project. I'm new to the forum and I really appreciate need help from all of you guys (and girls) and love to share experience with you. So there is the problem that I'm facing now.

I'm trying to make a piece of code from a older version of paparazzi (campaign 2010 martin mueller) compatible to the newer version (campaign 2011 martin mueller). So there were lots , of changes of directory to be modified. Right now there are 3 puzzles that I need your help with:

1) when I include a header file in a piece of c code, and the header file and the c file is in the same directory, do I still need to specify in the makefile to link them together when building the o file? I wonder because I used the main_logger.c in sw/airborne, and when it is building, there is an error saying that function mcu_init is undefined. But it is defined in the header file mcu.h, which is also in sw_airborne, and is included in the main.logger.c.

2) How do I know which makefile is responsible for linking which files/making which o files? Is it the one in the same directory as the c file? For example, main_logger.c is in the directory sw_airborne, and there is a Makefile in that directory, then should the information on how main_logger.o be built in that Makefile?  Or otherwise, where can I find the makefile to alter?

3) How do I do debug in the paparazzi  in general, can I print sth to the paparazzi center, for example using the echo command in the makefiles, to perform debugging?

Thank you very much for reading this message and any help will be appreciated !

Autumn Zhang



_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel