Files
paparazzi/conf/airframes
Gautier Hattenberger 4ac6279aa9
Issues due date / Add labels to issues (push) Has been cancelled
Doxygen / build (push) Has been cancelled
Docker update / build_docker_image (push) Has been cancelled
Fix compilation tests (#3550)
* [fix] fix some bugs

small errors from compilation tests

* Attempt to fix the detection of failing tests

Side effect: the file issues.md is not produced anymore, but still available in stdout, so needs a manual copy if needed
2025-10-20 16:57:24 +02:00
..
2024-11-01 17:58:50 +01:00
2025-10-20 16:57:24 +02:00
2025-10-20 16:57:24 +02:00
2025-08-15 16:00:32 +02:00

If you have your own autonomous aircraft, it is really apriciated if you would:
* Create your own short UPPERCASE directory name within this one, e.g. "MYX"
* Prefix your airframe names with the same name in lowercase and add an underscore, e.g. myx_superdart.xml

This will make your life of updating Paparazzi much simpler...

It can be helpful to take a look at how other paparazzi enthousiasts like you did just that.

TIP: Remember to put the following DOCTYPE line in the top of your airframe file: 

 <!DOCTYPE airframe SYSTEM "../airframe.dtd">

Have a great day!