[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[paparazzi-commits] [6431] removed all software as we moved to git
|
From: |
Felix Ruess |
|
Subject: |
[paparazzi-commits] [6431] removed all software as we moved to git |
|
Date: |
Fri, 19 Nov 2010 21:22:40 +0000 |
Revision: 6431
http://svn.sv.gnu.org/viewvc/?view=rev&root=paparazzi&revision=6431
Author: flixr
Date: 2010-11-19 21:22:39 +0000 (Fri, 19 Nov 2010)
Log Message:
-----------
removed all software as we moved to git
Removed Paths:
-------------
paparazzi-software/trunk/AUTHORS
paparazzi-software/trunk/BUGS
paparazzi-software/trunk/COPYING
paparazzi-software/trunk/Doxyfile
paparazzi-software/trunk/Makefile
paparazzi-software/trunk/Makefile.ac
paparazzi-software/trunk/Makefile.install
paparazzi-software/trunk/Makefile.sys
paparazzi-software/trunk/README
paparazzi-software/trunk/TODO
paparazzi-software/trunk/conf/
paparazzi-software/trunk/data/
paparazzi-software/trunk/debian/
paparazzi-software/trunk/doc/
paparazzi-software/trunk/paparazzi
paparazzi-software/trunk/paparazzi-make
paparazzi-software/trunk/paparazzi.osx
paparazzi-software/trunk/pprz_src_test.sh
paparazzi-software/trunk/sw/
Deleted: paparazzi-software/trunk/AUTHORS
===================================================================
--- paparazzi-software/trunk/AUTHORS 2010-11-19 21:17:29 UTC (rev 6430)
+++ paparazzi-software/trunk/AUTHORS 2010-11-19 21:22:39 UTC (rev 6431)
@@ -1,36 +0,0 @@
-aibara = Allen Ibara <address@hidden>
-andy_hb = Andreas Kleinert <address@hidden>
-antonk = Anton Kochevar <address@hidden>
-bvandepo = Vandeportaele Bertrand <address@hidden>
-cracmike = Michel Gorraz <address@hidden>
-dewagter = Christophe De Wagter <address@hidden>
-disciple = Louis Dugrain <address@hidden>
-esden = Piotr Esden-Tempski <address@hidden>
-flixr = Felix Ruess <address@hidden>
-fuchsto = Tobias Fuchs <address@hidden>
-gany = Ganymed Stanek <address@hidden>
-gautier = Gautier Hattenberger <address@hidden>
-ghorn = Greg Horn <address@hidden>
-gov = Gustavo Oliveira Violato <address@hidden>
-gph = Pierre-Selim Huard <address@hidden>
-hecto = Pascal Brisset <address@hidden>
-jpdumont = jpdumont <address@hidden>
-lamestllama = Eric Parsonage <address@hidden>
-marcuswolschon = Marcus Wolschon <address@hidden>
-markgriffin = Mark Griffin <address@hidden>
-mayrit = Murat Bronz <address@hidden>
-mdieblich = Martin Dieblich <address@hidden>
-milesj = Miles Johnson <address@hidden>
-mmm = Martin Mueller <address@hidden>
-nzjrs = John Stowers <address@hidden>
-olri = Oliver Riesener <address@hidden>
-osam = OSAM-UAV Team <address@hidden>
-paulcox = Paul Cox <address@hidden>
-peddie = Matthew Peddie <address@hidden>
-pixhawkteam = Pixhawk Team <address@hidden>
-poine = Antoine Drouin <address@hidden>
-rad = rad <address@hidden>
-rbdavison = Bernard Davison <address@hidden>
-rkrash = Roman Krashanitsa <address@hidden>
-sergio812 = Serge Le Huitouze <address@hidden>
-vassilis = Vassilis V. <address@hidden>
Deleted: paparazzi-software/trunk/BUGS
===================================================================
--- paparazzi-software/trunk/BUGS 2010-11-19 21:17:29 UTC (rev 6430)
+++ paparazzi-software/trunk/BUGS 2010-11-19 21:22:39 UTC (rev 6431)
@@ -1,2 +0,0 @@
-We count on your for finding them
-
Deleted: paparazzi-software/trunk/COPYING
===================================================================
--- paparazzi-software/trunk/COPYING 2010-11-19 21:17:29 UTC (rev 6430)
+++ paparazzi-software/trunk/COPYING 2010-11-19 21:22:39 UTC (rev 6431)
@@ -1,339 +0,0 @@
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
-
- Appendix: How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) 19yy <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) 19yy name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
Deleted: paparazzi-software/trunk/Doxyfile
===================================================================
--- paparazzi-software/trunk/Doxyfile 2010-11-19 21:17:29 UTC (rev 6430)
+++ paparazzi-software/trunk/Doxyfile 2010-11-19 21:22:39 UTC (rev 6431)
@@ -1,1218 +0,0 @@
-# Doxyfile 1.4.2
-
-# This file describes the settings to be used by the documentation system
-# doxygen (www.doxygen.org) for a project
-#
-# All text after a hash (#) is considered a comment and will be ignored
-# The format is:
-# TAG = value [value, ...]
-# For lists items can also be appended using:
-# TAG += value [value, ...]
-# Values that contain spaces should be placed between quotes (" ")
-
-#---------------------------------------------------------------------------
-# Project related configuration options
-#---------------------------------------------------------------------------
-
-# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
-# by quotes) that should identify the project.
-
-PROJECT_NAME = Paparazzi3
-
-# The PROJECT_NUMBER tag can be used to enter a project or revision number.
-# This could be handy for archiving the generated documentation or
-# if some version control system is used.
-
-PROJECT_NUMBER = 3
-
-# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
-# base path where the generated documentation will be put.
-# If a relative path is entered, it will be relative to the location
-# where doxygen was started. If left blank the current directory will be used.
-
-OUTPUT_DIRECTORY = dox
-
-# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
-# 4096 sub-directories (in 2 levels) under the output directory of each output
-# format and will distribute the generated files over these directories.
-# Enabling this option can be useful when feeding doxygen a huge amount of
-# source files, where putting all generated files in the same directory would
-# otherwise cause performance problems for the file system.
-
-CREATE_SUBDIRS = NO
-
-# The OUTPUT_LANGUAGE tag is used to specify the language in which all
-# documentation generated by doxygen is written. Doxygen will use this
-# information to generate all constant output in the proper language.
-# The default language is English, other supported languages are:
-# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
-# Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
-# Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
-# Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
-# Swedish, and Ukrainian.
-
-OUTPUT_LANGUAGE = English
-
-# This tag can be used to specify the encoding used in the generated output.
-# The encoding is not always determined by the language that is chosen,
-# but also whether or not the output is meant for Windows or non-Windows
users.
-# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
-# forces the Windows encoding (this is the default for the Windows binary),
-# whereas setting the tag to NO uses a Unix-style encoding (the default for
-# all platforms other than Windows).
-
-USE_WINDOWS_ENCODING = NO
-
-# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
-# include brief member descriptions after the members that are listed in
-# the file and class documentation (similar to JavaDoc).
-# Set to NO to disable this.
-
-BRIEF_MEMBER_DESC = YES
-
-# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
-# the brief description of a member or function before the detailed
description.
-# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
-# brief descriptions will be completely suppressed.
-
-REPEAT_BRIEF = YES
-
-# This tag implements a quasi-intelligent brief description abbreviator
-# that is used to form the text in various listings. Each string
-# in this list, if found as the leading text of the brief description, will be
-# stripped from the text and the result after processing the whole list, is
-# used as the annotated text. Otherwise, the brief description is used as-is.
-# If left blank, the following values are used ("$name" is automatically
-# replaced with the name of the entity): "The $name class" "The $name widget"
-# "The $name file" "is" "provides" "specifies" "contains"
-# "represents" "a" "an" "the"
-
-ABBREVIATE_BRIEF =
-
-# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
-# Doxygen will generate a detailed section even if there is only a brief
-# description.
-
-ALWAYS_DETAILED_SEC = NO
-
-# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
-# inherited members of a class in the documentation of that class as if those
-# members were ordinary class members. Constructors, destructors and
assignment
-# operators of the base classes will not be shown.
-
-INLINE_INHERITED_MEMB = NO
-
-# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
-# path before files name in the file list and in the header files. If set
-# to NO the shortest path that makes the file name unique will be used.
-
-FULL_PATH_NAMES = YES
-
-# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
-# can be used to strip a user-defined part of the path. Stripping is
-# only done if one of the specified strings matches the left-hand part of
-# the path. The tag can be used to show relative paths in the file list.
-# If left blank the directory from which doxygen is run is used as the
-# path to strip.
-
-STRIP_FROM_PATH =
-
-# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
-# the path mentioned in the documentation of a class, which tells
-# the reader which header file to include in order to use a class.
-# If left blank only the name of the header file containing the class
-# definition is used. Otherwise one should specify the include paths that
-# are normally passed to the compiler using the -I flag.
-
-STRIP_FROM_INC_PATH =
-
-# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
-# (but less readable) file names. This can be useful is your file systems
-# doesn't support long names like on DOS, Mac, or CD-ROM.
-
-SHORT_NAMES = NO
-
-# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
-# will interpret the first line (until the first dot) of a JavaDoc-style
-# comment as the brief description. If set to NO, the JavaDoc
-# comments will behave just like the Qt-style comments (thus requiring an
-# explicit @brief command for a brief description.
-
-JAVADOC_AUTOBRIEF = NO
-
-# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
-# treat a multi-line C++ special comment block (i.e. a block of //! or ///
-# comments) as a brief description. This used to be the default behaviour.
-# The new default is to treat a multi-line C++ comment block as a detailed
-# description. Set this tag to YES if you prefer the old behaviour instead.
-
-MULTILINE_CPP_IS_BRIEF = NO
-
-# If the DETAILS_AT_TOP tag is set to YES then Doxygen
-# will output the detailed description near the top, like JavaDoc.
-# If set to NO, the detailed description appears after the member
-# documentation.
-
-DETAILS_AT_TOP = YES
-
-# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
-# member inherits the documentation from any documented member that it
-# re-implements.
-
-INHERIT_DOCS = YES
-
-# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
-# tag is set to YES, then doxygen will reuse the documentation of the first
-# member in the group (if any) for the other members of the group. By default
-# all members of a group must be documented explicitly.
-
-DISTRIBUTE_GROUP_DOC = NO
-
-# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
-# a new page for each member. If set to NO, the documentation of a member will
-# be part of the file/class/namespace that contains it.
-
-SEPARATE_MEMBER_PAGES = NO
-
-# The TAB_SIZE tag can be used to set the number of spaces in a tab.
-# Doxygen uses this value to replace tabs by spaces in code fragments.
-
-TAB_SIZE = 2
-
-# This tag can be used to specify a number of aliases that acts
-# as commands in the documentation. An alias has the form "name=value".
-# For example adding "sideeffect=\par Side Effects:\n" will allow you to
-# put the command \sideeffect (or @sideeffect) in the documentation, which
-# will result in a user-defined paragraph with heading "Side Effects:".
-# You can put \n's in the value part of an alias to insert newlines.
-
-ALIASES =
-
-# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
-# sources only. Doxygen will then generate output that is more tailored for C.
-# For instance, some of the names that are used will be different. The list
-# of all members will be omitted, etc.
-
-OPTIMIZE_OUTPUT_FOR_C = YES
-
-# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
sources
-# only. Doxygen will then generate output that is more tailored for Java.
-# For instance, namespaces will be presented as packages, qualified scopes
-# will look different, etc.
-
-OPTIMIZE_OUTPUT_JAVA = NO
-
-# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
-# the same type (for instance a group of public functions) to be put as a
-# subgroup of that type (e.g. under the Public Functions section). Set it to
-# NO to prevent subgrouping. Alternatively, this can be done per class using
-# the \nosubgrouping command.
-
-SUBGROUPING = YES
-
-#---------------------------------------------------------------------------
-# Build related configuration options
-#---------------------------------------------------------------------------
-
-# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
-# documentation are documented, even if no documentation was available.
-# Private class members and static file members will be hidden unless
-# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
-
-EXTRACT_ALL = YES
-
-# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
-# will be included in the documentation.
-
-EXTRACT_PRIVATE = YES
-
-# If the EXTRACT_STATIC tag is set to YES all static members of a file
-# will be included in the documentation.
-
-EXTRACT_STATIC = YES
-
-# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
-# defined locally in source files will be included in the documentation.
-# If set to NO only classes defined in header files are included.
-
-EXTRACT_LOCAL_CLASSES = YES
-
-# This flag is only useful for Objective-C code. When set to YES local
-# methods, which are defined in the implementation section but not in
-# the interface are included in the documentation.
-# If set to NO (the default) only methods in the interface are included.
-
-EXTRACT_LOCAL_METHODS = NO
-
-# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
-# undocumented members of documented classes, files or namespaces.
-# If set to NO (the default) these members will be included in the
-# various overviews, but no documentation section is generated.
-# This option has no effect if EXTRACT_ALL is enabled.
-
-HIDE_UNDOC_MEMBERS = NO
-
-# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
-# undocumented classes that are normally visible in the class hierarchy.
-# If set to NO (the default) these classes will be included in the various
-# overviews. This option has no effect if EXTRACT_ALL is enabled.
-
-HIDE_UNDOC_CLASSES = NO
-
-# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
-# friend (class|struct|union) declarations.
-# If set to NO (the default) these declarations will be included in the
-# documentation.
-
-HIDE_FRIEND_COMPOUNDS = NO
-
-# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
-# documentation blocks found inside the body of a function.
-# If set to NO (the default) these blocks will be appended to the
-# function's detailed documentation block.
-
-HIDE_IN_BODY_DOCS = NO
-
-# The INTERNAL_DOCS tag determines if documentation
-# that is typed after a \internal command is included. If the tag is set
-# to NO (the default) then the documentation will be excluded.
-# Set it to YES to include the internal documentation.
-
-INTERNAL_DOCS = NO
-
-# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
-# file names in lower-case letters. If set to YES upper-case letters are also
-# allowed. This is useful if you have classes or files whose names only differ
-# in case and if your file system supports case sensitive file names. Windows
-# and Mac users are advised to set this option to NO.
-
-CASE_SENSE_NAMES = YES
-
-# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
-# will show members with their full class and namespace scopes in the
-# documentation. If set to YES the scope will be hidden.
-
-HIDE_SCOPE_NAMES = NO
-
-# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
-# will put a list of the files that are included by a file in the
documentation
-# of that file.
-
-SHOW_INCLUDE_FILES = YES
-
-# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
-# is inserted in the documentation for inline members.
-
-INLINE_INFO = YES
-
-# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
-# will sort the (detailed) documentation of file and class members
-# alphabetically by member name. If set to NO the members will appear in
-# declaration order.
-
-SORT_MEMBER_DOCS = YES
-
-# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
-# brief documentation of file, namespace and class members alphabetically
-# by member name. If set to NO (the default) the members will appear in
-# declaration order.
-
-SORT_BRIEF_DOCS = NO
-
-# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
-# sorted by fully-qualified names, including namespaces. If set to
-# NO (the default), the class list will be sorted only by class name,
-# not including the namespace part.
-# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
-# Note: This option applies only to the class list, not to the
-# alphabetical list.
-
-SORT_BY_SCOPE_NAME = NO
-
-# The GENERATE_TODOLIST tag can be used to enable (YES) or
-# disable (NO) the todo list. This list is created by putting \todo
-# commands in the documentation.
-
-GENERATE_TODOLIST = YES
-
-# The GENERATE_TESTLIST tag can be used to enable (YES) or
-# disable (NO) the test list. This list is created by putting \test
-# commands in the documentation.
-
-GENERATE_TESTLIST = YES
-
-# The GENERATE_BUGLIST tag can be used to enable (YES) or
-# disable (NO) the bug list. This list is created by putting \bug
-# commands in the documentation.
-
-GENERATE_BUGLIST = YES
-
-# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
-# disable (NO) the deprecated list. This list is created by putting
-# \deprecated commands in the documentation.
-
-GENERATE_DEPRECATEDLIST= YES
-
-# The ENABLED_SECTIONS tag can be used to enable conditional
-# documentation sections, marked by \if sectionname ... \endif.
-
-ENABLED_SECTIONS =
-
-# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
-# the initial value of a variable or define consists of for it to appear in
-# the documentation. If the initializer consists of more lines than specified
-# here it will be hidden. Use a value of 0 to hide initializers completely.
-# The appearance of the initializer of individual variables and defines in the
-# documentation can be controlled using \showinitializer or \hideinitializer
-# command in the documentation regardless of this setting.
-
-MAX_INITIALIZER_LINES = 30
-
-# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
-# at the bottom of the documentation of classes and structs. If set to YES the
-# list will mention the files that were used to generate the documentation.
-
-SHOW_USED_FILES = YES
-
-# If the sources in your project are distributed over multiple directories
-# then setting the SHOW_DIRECTORIES tag to YES will show the directory
hierarchy
-# in the documentation.
-
-SHOW_DIRECTORIES = YES
-
-# The FILE_VERSION_FILTER tag can be used to specify a program or script that
-# doxygen should invoke to get the current version for each file (typically
from the
-# version control system). Doxygen will invoke the program by executing (via
-# popen()) the command <command> <input-file>, where <command> is the value of
-# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
-# provided by doxygen. Whatever the progam writes to standard output
-# is used as the file version. See the manual for examples.
-
-FILE_VERSION_FILTER =
-
-#---------------------------------------------------------------------------
-# configuration options related to warning and progress messages
-#---------------------------------------------------------------------------
-
-# The QUIET tag can be used to turn on/off the messages that are generated
-# by doxygen. Possible values are YES and NO. If left blank NO is used.
-
-QUIET = NO
-
-# The WARNINGS tag can be used to turn on/off the warning messages that are
-# generated by doxygen. Possible values are YES and NO. If left blank
-# NO is used.
-
-WARNINGS = YES
-
-# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
-# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
-# automatically be disabled.
-
-WARN_IF_UNDOCUMENTED = YES
-
-# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
-# potential errors in the documentation, such as not documenting some
-# parameters in a documented function, or documenting parameters that
-# don't exist or using markup commands wrongly.
-
-WARN_IF_DOC_ERROR = YES
-
-# This WARN_NO_PARAMDOC option can be abled to get warnings for
-# functions that are documented, but have no documentation for their
parameters
-# or return value. If set to NO (the default) doxygen will only warn about
-# wrong or incomplete parameter documentation, but not about the absence of
-# documentation.
-
-WARN_NO_PARAMDOC = NO
-
-# The WARN_FORMAT tag determines the format of the warning messages that
-# doxygen can produce. The string should contain the $file, $line, and $text
-# tags, which will be replaced by the file and line number from which the
-# warning originated and the warning text. Optionally the format may contain
-# $version, which will be replaced by the version of the file (if it could
-# be obtained via FILE_VERSION_FILTER)
-
-WARN_FORMAT = "$file:$line: $text"
-
-# The WARN_LOGFILE tag can be used to specify a file to which warning
-# and error messages should be written. If left blank the output is written
-# to stderr.
-
-WARN_LOGFILE =
-
-#---------------------------------------------------------------------------
-# configuration options related to the input files
-#---------------------------------------------------------------------------
-
-# The INPUT tag can be used to specify the files and/or directories that
contain
-# documented source files. You may enter file names like "myfile.cpp" or
-# directories like "/usr/src/myproject". Separate the files or directories
-# with spaces.
-
-INPUT = sw/airborne/booz_priv sw/airborne/booz_priv/
sw/airborne/booz_priv/arm7 sw/airborne/ sw/airborne/arm7
-
-# If the value of the INPUT tag contains directories, you can use the
-# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
-# and *.h) to filter out the source-files in the directories. If left
-# blank the following patterns are tested:
-# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
*.hxx
-# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
-
-FILE_PATTERNS =
-
-# The RECURSIVE tag can be used to turn specify whether or not subdirectories
-# should be searched for input files as well. Possible values are YES and NO.
-# If left blank NO is used.
-
-RECURSIVE = NO
-
-# The EXCLUDE tag can be used to specify files and/or directories that should
-# excluded from the INPUT source files. This way you can easily exclude a
-# subdirectory from a directory tree whose root is specified with the INPUT
tag.
-
-EXCLUDE =
-
-# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
-# directories that are symbolic links (a Unix filesystem feature) are excluded
-# from the input.
-
-EXCLUDE_SYMLINKS = NO
-
-# If the value of the INPUT tag contains directories, you can use the
-# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
-# certain files from those directories.
-
-EXCLUDE_PATTERNS =
-
-# The EXAMPLE_PATH tag can be used to specify one or more files or
-# directories that contain example code fragments that are included (see
-# the \include command).
-
-EXAMPLE_PATH =
-
-# If the value of the EXAMPLE_PATH tag contains directories, you can use the
-# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
-# and *.h) to filter out the source-files in the directories. If left
-# blank all files are included.
-
-EXAMPLE_PATTERNS =
-
-# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
-# searched for input files to be used with the \include or \dontinclude
-# commands irrespective of the value of the RECURSIVE tag.
-# Possible values are YES and NO. If left blank NO is used.
-
-EXAMPLE_RECURSIVE = NO
-
-# The IMAGE_PATH tag can be used to specify one or more files or
-# directories that contain image that are included in the documentation (see
-# the \image command).
-
-IMAGE_PATH =
-
-# The INPUT_FILTER tag can be used to specify a program that doxygen should
-# invoke to filter for each input file. Doxygen will invoke the filter program
-# by executing (via popen()) the command <filter> <input-file>, where <filter>
-# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
-# input file. Doxygen will then use the output that the filter program writes
-# to standard output. If FILTER_PATTERNS is specified, this tag will be
-# ignored.
-
-INPUT_FILTER =
-
-# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
-# basis. Doxygen will compare the file name with each pattern and apply the
-# filter if there is a match. The filters are a list of the form:
-# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
-# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
-# is applied to all files.
-
-FILTER_PATTERNS =
-
-# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
-# INPUT_FILTER) will be used to filter the input files when producing source
-# files to browse (i.e. when SOURCE_BROWSER is set to YES).
-
-FILTER_SOURCE_FILES = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to source browsing
-#---------------------------------------------------------------------------
-
-# If the SOURCE_BROWSER tag is set to YES then a list of source files will
-# be generated. Documented entities will be cross-referenced with these
sources.
-# Note: To get rid of all source code in the generated output, make sure also
-# VERBATIM_HEADERS is set to NO.
-
-SOURCE_BROWSER = YES
-
-# Setting the INLINE_SOURCES tag to YES will include the body
-# of functions and classes directly in the documentation.
-
-INLINE_SOURCES = NO
-
-# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
-# doxygen to hide any special comment blocks from generated source code
-# fragments. Normal C and C++ comments will always remain visible.
-
-STRIP_CODE_COMMENTS = YES
-
-# If the REFERENCED_BY_RELATION tag is set to YES (the default)
-# then for each documented function all documented
-# functions referencing it will be listed.
-
-REFERENCED_BY_RELATION = YES
-
-# If the REFERENCES_RELATION tag is set to YES (the default)
-# then for each documented function all documented entities
-# called/used by that function will be listed.
-
-REFERENCES_RELATION = YES
-
-# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
-# will generate a verbatim copy of the header file for each class for
-# which an include is specified. Set to NO to disable this.
-
-VERBATIM_HEADERS = YES
-
-#---------------------------------------------------------------------------
-# configuration options related to the alphabetical class index
-#---------------------------------------------------------------------------
-
-# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
-# of all compounds will be generated. Enable this if the project
-# contains a lot of classes, structs, unions or interfaces.
-
-ALPHABETICAL_INDEX = NO
-
-# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
-# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
-# in which this list will be split (can be a number in the range [1..20])
-
-COLS_IN_ALPHA_INDEX = 5
-
-# In case all classes in a project start with a common prefix, all
-# classes will be put under the same header in the alphabetical index.
-# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
-# should be ignored while generating the index headers.
-
-IGNORE_PREFIX =
-
-#---------------------------------------------------------------------------
-# configuration options related to the HTML output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
-# generate HTML output.
-
-GENERATE_HTML = YES
-
-# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `html' will be used as the default path.
-
-HTML_OUTPUT = html
-
-# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
-# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
-# doxygen will generate files with .html extension.
-
-HTML_FILE_EXTENSION = .html
-
-# The HTML_HEADER tag can be used to specify a personal HTML header for
-# each generated HTML page. If it is left blank doxygen will generate a
-# standard header.
-
-HTML_HEADER =
-
-# The HTML_FOOTER tag can be used to specify a personal HTML footer for
-# each generated HTML page. If it is left blank doxygen will generate a
-# standard footer.
-
-HTML_FOOTER =
-
-# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
-# style sheet that is used by each HTML page. It can be used to
-# fine-tune the look of the HTML output. If the tag is left blank doxygen
-# will generate a default style sheet. Note that doxygen will try to copy
-# the style sheet file to the HTML output directory, so don't put your own
-# stylesheet in the HTML output directory as well, or it will be erased!
-
-HTML_STYLESHEET =
-
-# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
-# files or namespaces will be aligned in HTML using tables. If set to
-# NO a bullet list will be used.
-
-HTML_ALIGN_MEMBERS = YES
-
-# If the GENERATE_HTMLHELP tag is set to YES, additional index files
-# will be generated that can be used as input for tools like the
-# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
-# of the generated HTML documentation.
-
-GENERATE_HTMLHELP = NO
-
-# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
-# be used to specify the file name of the resulting .chm file. You
-# can add a path in front of the file if the result should not be
-# written to the html output directory.
-
-CHM_FILE =
-
-# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
-# be used to specify the location (absolute path including file name) of
-# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
-# the HTML help compiler on the generated index.hhp.
-
-HHC_LOCATION =
-
-# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
-# controls if a separate .chi index file is generated (YES) or that
-# it should be included in the master .chm file (NO).
-
-GENERATE_CHI = NO
-
-# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
-# controls whether a binary table of contents is generated (YES) or a
-# normal table of contents (NO) in the .chm file.
-
-BINARY_TOC = NO
-
-# The TOC_EXPAND flag can be set to YES to add extra items for group members
-# to the contents of the HTML help documentation and to the tree view.
-
-TOC_EXPAND = NO
-
-# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
-# top of each HTML page. The value NO (the default) enables the index and
-# the value YES disables it.
-
-DISABLE_INDEX = NO
-
-# This tag can be used to set the number of enum values (range [1..20])
-# that doxygen will group on one line in the generated HTML documentation.
-
-ENUM_VALUES_PER_LINE = 4
-
-# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
-# generated containing a tree-like index structure (just like the one that
-# is generated for HTML Help). For this to work a browser that supports
-# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
-# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
-# probably better off using the HTML help feature.
-
-GENERATE_TREEVIEW = NO
-
-# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
-# used to set the initial width (in pixels) of the frame in which the tree
-# is shown.
-
-TREEVIEW_WIDTH = 250
-
-#---------------------------------------------------------------------------
-# configuration options related to the LaTeX output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
-# generate Latex output.
-
-GENERATE_LATEX = YES
-
-# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `latex' will be used as the default path.
-
-LATEX_OUTPUT = latex
-
-# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
-# invoked. If left blank `latex' will be used as the default command name.
-
-LATEX_CMD_NAME = latex
-
-# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
-# generate index for LaTeX. If left blank `makeindex' will be used as the
-# default command name.
-
-MAKEINDEX_CMD_NAME = makeindex
-
-# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
-# LaTeX documents. This may be useful for small projects and may help to
-# save some trees in general.
-
-COMPACT_LATEX = NO
-
-# The PAPER_TYPE tag can be used to set the paper type that is used
-# by the printer. Possible values are: a4, a4wide, letter, legal and
-# executive. If left blank a4wide will be used.
-
-PAPER_TYPE = a4wide
-
-# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
-# packages that should be included in the LaTeX output.
-
-EXTRA_PACKAGES =
-
-# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
-# the generated latex document. The header should contain everything until
-# the first chapter. If it is left blank doxygen will generate a
-# standard header. Notice: only use this tag if you know what you are doing!
-
-LATEX_HEADER =
-
-# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
-# is prepared for conversion to pdf (using ps2pdf). The pdf file will
-# contain links (just like the HTML output) instead of page references
-# This makes the output suitable for online browsing using a pdf viewer.
-
-PDF_HYPERLINKS = NO
-
-# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
-# plain latex in the generated Makefile. Set this option to YES to get a
-# higher quality PDF documentation.
-
-USE_PDFLATEX = NO
-
-# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
-# command to the generated LaTeX files. This will instruct LaTeX to keep
-# running if errors occur, instead of asking the user for help.
-# This option is also used when generating formulas in HTML.
-
-LATEX_BATCHMODE = NO
-
-# If LATEX_HIDE_INDICES is set to YES then doxygen will not
-# include the index chapters (such as File Index, Compound Index, etc.)
-# in the output.
-
-LATEX_HIDE_INDICES = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the RTF output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
-# The RTF output is optimized for Word 97 and may not look very pretty with
-# other RTF readers or editors.
-
-GENERATE_RTF = NO
-
-# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `rtf' will be used as the default path.
-
-RTF_OUTPUT = rtf
-
-# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
-# RTF documents. This may be useful for small projects and may help to
-# save some trees in general.
-
-COMPACT_RTF = NO
-
-# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
-# will contain hyperlink fields. The RTF file will
-# contain links (just like the HTML output) instead of page references.
-# This makes the output suitable for online browsing using WORD or other
-# programs which support those fields.
-# Note: wordpad (write) and others do not support links.
-
-RTF_HYPERLINKS = NO
-
-# Load stylesheet definitions from file. Syntax is similar to doxygen's
-# config file, i.e. a series of assignments. You only have to provide
-# replacements, missing definitions are set to their default value.
-
-RTF_STYLESHEET_FILE =
-
-# Set optional variables used in the generation of an rtf document.
-# Syntax is similar to doxygen's config file.
-
-RTF_EXTENSIONS_FILE =
-
-#---------------------------------------------------------------------------
-# configuration options related to the man page output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
-# generate man pages
-
-GENERATE_MAN = NO
-
-# The MAN_OUTPUT tag is used to specify where the man pages will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `man' will be used as the default path.
-
-MAN_OUTPUT = man
-
-# The MAN_EXTENSION tag determines the extension that is added to
-# the generated man pages (default is the subroutine's section .3)
-
-MAN_EXTENSION = .3
-
-# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
-# then it will generate one additional man file for each entity
-# documented in the real man page(s). These additional files
-# only source the real man page, but without them the man command
-# would be unable to find the correct page. The default is NO.
-
-MAN_LINKS = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the XML output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_XML tag is set to YES Doxygen will
-# generate an XML file that captures the structure of
-# the code including all documentation.
-
-GENERATE_XML = NO
-
-# The XML_OUTPUT tag is used to specify where the XML pages will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `xml' will be used as the default path.
-
-XML_OUTPUT = xml
-
-# The XML_SCHEMA tag can be used to specify an XML schema,
-# which can be used by a validating XML parser to check the
-# syntax of the XML files.
-
-XML_SCHEMA =
-
-# The XML_DTD tag can be used to specify an XML DTD,
-# which can be used by a validating XML parser to check the
-# syntax of the XML files.
-
-XML_DTD =
-
-# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
-# dump the program listings (including syntax highlighting
-# and cross-referencing information) to the XML output. Note that
-# enabling this will significantly increase the size of the XML output.
-
-XML_PROGRAMLISTING = YES
-
-#---------------------------------------------------------------------------
-# configuration options for the AutoGen Definitions output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
-# generate an AutoGen Definitions (see autogen.sf.net) file
-# that captures the structure of the code including all
-# documentation. Note that this feature is still experimental
-# and incomplete at the moment.
-
-GENERATE_AUTOGEN_DEF = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the Perl module output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_PERLMOD tag is set to YES Doxygen will
-# generate a Perl module file that captures the structure of
-# the code including all documentation. Note that this
-# feature is still experimental and incomplete at the
-# moment.
-
-GENERATE_PERLMOD = NO
-
-# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
-# the necessary Makefile rules, Perl scripts and LaTeX code to be able
-# to generate PDF and DVI output from the Perl module output.
-
-PERLMOD_LATEX = NO
-
-# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
-# nicely formatted so it can be parsed by a human reader. This is useful
-# if you want to understand what is going on. On the other hand, if this
-# tag is set to NO the size of the Perl module output will be much smaller
-# and Perl will parse it just the same.
-
-PERLMOD_PRETTY = YES
-
-# The names of the make variables in the generated doxyrules.make file
-# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
-# This is useful so different doxyrules.make files included by the same
-# Makefile don't overwrite each other's variables.
-
-PERLMOD_MAKEVAR_PREFIX =
-
-#---------------------------------------------------------------------------
-# Configuration options related to the preprocessor
-#---------------------------------------------------------------------------
-
-# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
-# evaluate all C-preprocessor directives found in the sources and include
-# files.
-
-ENABLE_PREPROCESSING = YES
-
-# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
-# names in the source code. If set to NO (the default) only conditional
-# compilation will be performed. Macro expansion can be done in a controlled
-# way by setting EXPAND_ONLY_PREDEF to YES.
-
-MACRO_EXPANSION = NO
-
-# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
-# then the macro expansion is limited to the macros specified with the
-# PREDEFINED and EXPAND_AS_PREDEFINED tags.
-
-EXPAND_ONLY_PREDEF = NO
-
-# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
-# in the INCLUDE_PATH (see below) will be search if a #include is found.
-
-SEARCH_INCLUDES = YES
-
-# The INCLUDE_PATH tag can be used to specify one or more directories that
-# contain include files that are not input files but should be processed by
-# the preprocessor.
-
-INCLUDE_PATH = var/BOOZ2_flixr var/include sw/include
sw/airborne/booz_priv sw/airborne/booz_priv/ sw/airborne/booz_priv/arm7
sw/airborne/ sw/airborne/arm7 var/BOOZ2_flixr
-
-# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
-# patterns (like *.h and *.hpp) to filter out the header-files in the
-# directories. If left blank, the patterns specified with FILE_PATTERNS will
-# be used.
-
-INCLUDE_FILE_PATTERNS =
-
-# The PREDEFINED tag can be used to specify one or more macro names that
-# are defined before the preprocessor is started (similar to the -D option of
-# gcc). The argument of the tag is a list of macros of the form: name
-# or name=definition (no spaces). If the definition and the = are
-# omitted =1 is assumed. To prevent a macro definition from being
-# undefined via #undef or recursively expanded use the := operator
-# instead of the = operator.
-
-PREDEFINED = KILL_SWITCH USE_BUSS_TWI_BLMC USE_AMI601
-
-# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
-# this tag can be used to specify a list of macro names that should be
expanded.
-# The macro definition that is found in the sources will be used.
-# Use the PREDEFINED tag if you want to use a different macro definition.
-
-EXPAND_AS_DEFINED =
-
-# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
-# doxygen's preprocessor will remove all function-like macros that are alone
-# on a line, have an all uppercase name, and do not end with a semicolon. Such
-# function macros are typically used for boiler-plate code, and will confuse
-# the parser if not removed.
-
-SKIP_FUNCTION_MACROS = YES
-
-#---------------------------------------------------------------------------
-# Configuration::additions related to external references
-#---------------------------------------------------------------------------
-
-# The TAGFILES option can be used to specify one or more tagfiles.
-# Optionally an initial location of the external documentation
-# can be added for each tagfile. The format of a tag file without
-# this location is as follows:
-# TAGFILES = file1 file2 ...
-# Adding location for the tag files is done as follows:
-# TAGFILES = file1=loc1 "file2 = loc2" ...
-# where "loc1" and "loc2" can be relative or absolute paths or
-# URLs. If a location is present for each tag, the installdox tool
-# does not have to be run to correct the links.
-# Note that each tag file must have a unique name
-# (where the name does NOT include the path)
-# If a tag file is not located in the directory in which doxygen
-# is run, you must also specify the path to the tagfile here.
-
-TAGFILES =
-
-# When a file name is specified after GENERATE_TAGFILE, doxygen will create
-# a tag file that is based on the input files it reads.
-
-GENERATE_TAGFILE =
-
-# If the ALLEXTERNALS tag is set to YES all external classes will be listed
-# in the class index. If set to NO only the inherited external classes
-# will be listed.
-
-ALLEXTERNALS = NO
-
-# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
-# in the modules index. If set to NO, only the current project's groups will
-# be listed.
-
-EXTERNAL_GROUPS = YES
-
-# The PERL_PATH should be the absolute path and name of the perl script
-# interpreter (i.e. the result of `which perl').
-
-PERL_PATH = /usr/bin/perl
-
-#---------------------------------------------------------------------------
-# Configuration options related to the dot tool
-#---------------------------------------------------------------------------
-
-# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
-# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with
base
-# or super classes. Setting the tag to NO turns the diagrams off. Note that
-# this option is superseded by the HAVE_DOT option below. This is only a
-# fallback. It is recommended to install and use dot, since it yields more
-# powerful graphs.
-
-CLASS_DIAGRAMS = YES
-
-# If set to YES, the inheritance and collaboration graphs will hide
-# inheritance and usage relations if the target is undocumented
-# or is not a class.
-
-HIDE_UNDOC_RELATIONS = YES
-
-# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
-# available from the path. This tool is part of Graphviz, a graph
visualization
-# toolkit from AT&T and Lucent Bell Labs. The other options in this section
-# have no effect if this option is set to NO (the default)
-
-HAVE_DOT = YES
-
-# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
-# will generate a graph for each documented class showing the direct and
-# indirect inheritance relations. Setting this tag to YES will force the
-# the CLASS_DIAGRAMS tag to NO.
-
-CLASS_GRAPH = YES
-
-# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
-# will generate a graph for each documented class showing the direct and
-# indirect implementation dependencies (inheritance, containment, and
-# class references variables) of the class with other documented classes.
-
-COLLABORATION_GRAPH = YES
-
-# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
-# will generate a graph for groups, showing the direct groups dependencies
-
-GROUP_GRAPHS = YES
-
-# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
-# collaboration diagrams in a style similar to the OMG's Unified Modeling
-# Language.
-
-UML_LOOK = NO
-
-# If set to YES, the inheritance and collaboration graphs will show the
-# relations between templates and their instances.
-
-TEMPLATE_RELATIONS = NO
-
-# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
-# tags are set to YES then doxygen will generate a graph for each documented
-# file showing the direct and indirect include dependencies of the file with
-# other documented files.
-
-INCLUDE_GRAPH = YES
-
-# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
-# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
-# documented header file showing the documented files that directly or
-# indirectly include this file.
-
-INCLUDED_BY_GRAPH = YES
-
-# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
-# generate a call dependency graph for every global function or class method.
-# Note that enabling this option will significantly increase the time of a
run.
-# So in most cases it will be better to enable call graphs for selected
-# functions only using the \callgraph command.
-
-CALL_GRAPH = NO
-
-# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
-# will graphical hierarchy of all classes instead of a textual one.
-
-GRAPHICAL_HIERARCHY = YES
-
-# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
-# then doxygen will show the dependencies a directory has on other directories
-# in a graphical way. The dependency relations are determined by the #include
-# relations between the files in the directories.
-
-DIRECTORY_GRAPH = YES
-
-# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
-# generated by dot. Possible values are png, jpg, or gif
-# If left blank png will be used.
-
-DOT_IMAGE_FORMAT = png
-
-# The tag DOT_PATH can be used to specify the path where the dot tool can be
-# found. If left blank, it is assumed the dot tool can be found in the path.
-
-DOT_PATH =
-
-# The DOTFILE_DIRS tag can be used to specify one or more directories that
-# contain dot files that are included in the documentation (see the
-# \dotfile command).
-
-DOTFILE_DIRS =
-
-# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
-# (in pixels) of the graphs generated by dot. If a graph becomes larger than
-# this value, doxygen will try to truncate the graph, so that it fits within
-# the specified constraint. Beware that most browsers cannot cope with very
-# large images.
-
-MAX_DOT_GRAPH_WIDTH = 1024
-
-# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
-# (in pixels) of the graphs generated by dot. If a graph becomes larger than
-# this value, doxygen will try to truncate the graph, so that it fits within
-# the specified constraint. Beware that most browsers cannot cope with very
-# large images.
-
-MAX_DOT_GRAPH_HEIGHT = 1024
-
-# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
-# graphs generated by dot. A depth value of 3 means that only nodes reachable
-# from the root by following a path via at most 3 edges will be shown. Nodes
-# that lay further from the root node will be omitted. Note that setting this
-# option to 1 or 2 may greatly reduce the computation time needed for large
-# code bases. Also note that a graph may be further truncated if the graph's
-# image dimensions are not sufficient to fit the graph (see
MAX_DOT_GRAPH_WIDTH
-# and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default),
-# the graph is not depth-constrained.
-
-MAX_DOT_GRAPH_DEPTH = 0
-
-# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
-# background. This is disabled by default, which results in a white
background.
-# Warning: Depending on the platform used, enabling this option may lead to
-# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
-# read).
-
-DOT_TRANSPARENT = NO
-
-# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
-# files in one run (i.e. multiple -o and -T options on the command line). This
-# makes dot run faster, but since only newer versions of dot (>1.8.10)
-# support this, this feature is disabled by default.
-
-DOT_MULTI_TARGETS = NO
-
-# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
-# generate a legend page explaining the meaning of the various boxes and
-# arrows in the dot generated graphs.
-
-GENERATE_LEGEND = YES
-
-# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
-# remove the intermediate dot files that are used to generate
-# the various graphs.
-
-DOT_CLEANUP = YES
-
-#---------------------------------------------------------------------------
-# Configuration::additions related to the search engine
-#---------------------------------------------------------------------------
-
-# The SEARCHENGINE tag specifies whether or not a search engine should be
-# used. If set to NO the values of all tags below this one will be ignored.
-
-SEARCHENGINE = NO
Deleted: paparazzi-software/trunk/Makefile
===================================================================
--- paparazzi-software/trunk/Makefile 2010-11-19 21:17:29 UTC (rev 6430)
+++ paparazzi-software/trunk/Makefile 2010-11-19 21:22:39 UTC (rev 6431)
@@ -1,227 +0,0 @@
-# Hey Emacs, this is a -*- makefile -*-
-#
-# Paparazzi main $Id$
-# Copyright (C) 2004 Pascal Brisset Antoine Drouin
-#
-# This file is part of paparazzi.
-#
-# paparazzi is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# paparazzi is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with paparazzi; see the file COPYING. If not, write to
-# the Free Software Foundation, 59 Temple Place - Suite 330,
-# Boston, MA 02111-1307, USA.
-
-# The default is to produce a quiet echo of compilation commands
-# Launch with "make Q=''" to get full echo
-Q=@
-
-ifeq ($(Q),@)
-MAKEFLAGS += --no-print-directory
-endif
-
-PAPARAZZI_SRC=$(shell pwd)
-empty=
-space=$(empty) $(empty)
-ifneq ($(findstring $(space),$(PAPARAZZI_SRC)),)
- $(error No fucking spaces allowed in the current directory name)
-endif
-ifeq ($(PAPARAZZI_HOME),)
-PAPARAZZI_HOME=$(PAPARAZZI_SRC)
-endif
-
-LIB=sw/lib
-AIRBORNE=sw/airborne
-COCKPIT=sw/ground_segment/cockpit
-TMTC=sw/ground_segment/tmtc
-MULTIMON=sw/ground_segment/multimon
-LOGALIZER=sw/logalizer
-SIMULATOR=sw/simulator
-MAKE=make PAPARAZZI_SRC=$(PAPARAZZI_SRC) PAPARAZZI_HOME=$(PAPARAZZI_HOME)
-CONF=$(PAPARAZZI_SRC)/conf
-STATICINCLUDE =$(PAPARAZZI_HOME)/var/include
-MESSAGES_H=$(STATICINCLUDE)/messages.h
-MESSAGES2_H=$(STATICINCLUDE)/messages2.h
-UBX_PROTOCOL_H=$(STATICINCLUDE)/ubx_protocol.h
-XSENS_PROTOCOL_H=$(STATICINCLUDE)/xsens_protocol.h
-DL_PROTOCOL_H=$(STATICINCLUDE)/dl_protocol.h
-DL_PROTOCOL2_H=$(STATICINCLUDE)/dl_protocol2.h
-MESSAGES_XML = $(CONF)/messages.xml
-UBX_XML = $(CONF)/ubx.xml
-XSENS_XML = $(CONF)/xsens_MTi-G.xml
-TOOLS=$(PAPARAZZI_SRC)/sw/tools
-HAVE_ARM_NONE_EABI_GCC := $(wildcard /usr/bin/arm-none-eabi-gcc)
-ifeq ($(strip $(HAVE_ARM_NONE_EABI_GCC)),)
-#ARMGCC=/opt/paparazzi/bin/arm-elf-gcc
-ARMGCC=/usr/bin/arm-elf-gcc
-else
-ARMGCC=/usr/bin/arm-none-eabi-gcc
-endif
-
-
-all: static conf
-
-static : lib center tools cockpit multimon tmtc logalizer lpc21iap sim_static
static_h usb_lib
-
-conf: conf/conf.xml conf/control_panel.xml
-
-conf/%.xml :conf/%.xml.example
- [ -L $@ ] || [ -f $@ ] || cp $< $@
-
-
-lib:
- cd $(LIB)/ocaml; $(MAKE)
-
-center: lib
- cd sw/supervision; make
-
-tools: lib
- cd $(TOOLS); make
-
-logalizer: lib
- cd $(LOGALIZER); $(MAKE)
-
-sim_static : lib
- cd $(SIMULATOR); $(MAKE) PAPARAZZI_SRC=$(PAPARAZZI_SRC)
-
-cockpit: lib
- cd $(COCKPIT); $(MAKE) all
-
-tmtc: lib cockpit
- cd $(TMTC); $(MAKE) all
-
-multimon:
- cd $(MULTIMON); $(MAKE)
-
-static_h: $(MESSAGES_H) $(MESSAGES2_H) $(UBX_PROTOCOL_H) $(XSENS_PROTOCOL_H)
$(DL_PROTOCOL_H) $(DL_PROTOCOL2_H)
-
-usb_lib:
- @[ -d sw/airborne/arch/lpc21/lpcusb ] && ((test -x $(ARMGCC) && (cd
sw/airborne/arch/lpc21/lpcusb; $(MAKE))) || echo "Not building usb_lib:
ARMGCC=$(ARMGCC) not found") || echo "Not building usb_lib:
sw/airborne/arch/lpc21/lpcusb directory missing"
-
-$(MESSAGES_H) : $(MESSAGES_XML) $(CONF_XML) tools
- $(Q)test -d $(STATICINCLUDE) || mkdir -p $(STATICINCLUDE)
- @echo BUILD $@
- $(Q)PAPARAZZI_SRC=$(PAPARAZZI_SRC) $(TOOLS)/gen_messages.out $<
telemetry > /tmp/msg.h
- $(Q)mv /tmp/msg.h $@
- $(Q)chmod a+r $@
-
-$(MESSAGES2_H) : $(MESSAGES_XML) $(CONF_XML) tools
- $(Q)test -d $(STATICINCLUDE) || mkdir -p $(STATICINCLUDE)
- @echo BUILD $@
- $(Q)PAPARAZZI_SRC=$(PAPARAZZI_SRC) $(TOOLS)/gen_messages2.out $<
telemetry > /tmp/msg2.h
- $(Q)mv /tmp/msg2.h $@
- $(Q)chmod a+r $@
-
-$(UBX_PROTOCOL_H) : $(UBX_XML) tools
- @echo BUILD $@
- $(Q)PAPARAZZI_SRC=$(PAPARAZZI_SRC) $(TOOLS)/gen_ubx.out $< > /tmp/ubx.h
- $(Q)mv /tmp/ubx.h $@
-
-$(XSENS_PROTOCOL_H) : $(XSENS_XML) tools
- @echo BUILD $@
- $(Q)PAPARAZZI_SRC=$(PAPARAZZI_SRC) $(TOOLS)/gen_xsens.out $< >
/tmp/xsens.h
- $(Q)mv /tmp/xsens.h $@
-
-$(DL_PROTOCOL_H) : $(MESSAGES_XML) tools
- @echo BUILD $@
- $(Q)PAPARAZZI_SRC=$(PAPARAZZI_SRC) $(TOOLS)/gen_messages.out $<
datalink > /tmp/dl.h
- $(Q)mv /tmp/dl.h $@
-
-$(DL_PROTOCOL2_H) : $(MESSAGES_XML) tools
- @echo BUILD $@
- $(Q)PAPARAZZI_SRC=$(PAPARAZZI_SRC) $(TOOLS)/gen_messages2.out $<
datalink > /tmp/dl2.h
- $(Q)mv /tmp/dl2.h $@
-
-include Makefile.ac
-
-sim : sim_static
-
-
-ac_h ac1 ac2 ac3 ac fbw ap: static conf
-
-##### preliminary hard wired arm7 bootloader rules
-#
-#
-# call with : make bl PROC=[TINY|FBW|AP|GENERIC]
-bl:
- cd $(AIRBORNE)/arch/lpc21/test/bootloader; make clean; make
-
-BOOTLOADER_DEV=/dev/ttyUSB0
-upload_bl bl.upload: bl
- lpc21isp -control $(AIRBORNE)/arch/lpc21/test/bootloader/bl.hex
$(BOOTLOADER_DEV) 38400 12000
-
-JTAG_INTERFACE = olimex-jtag-tiny.cfg
-#JTAG_INTERFACE = olimex-arm-usb-ocd.cfg
-
-upload_jtag: bl
- openocd -f interface/$(JTAG_INTERFACE) -f board/olimex_lpc_h2148.cfg
-c init -c halt -c "flash write_image erase
$(AIRBORNE)/arch/lpc21/test/bootloader/bl.hex" -c reset -c shutdown
-
-
-
-lpc21iap:
- cd sw/ground_segment/lpc21iap; make
-
-upgrade_bl bl.upgrade: bl lpc21iap
- $(PAPARAZZI_SRC)/sw/ground_segment/lpc21iap/lpc21iap
$(AIRBORNE)/arch/lpc21/test/bootloader/bl_ram.elf
- $(PAPARAZZI_SRC)/sw/ground_segment/lpc21iap/lpc21iap
$(AIRBORNE)/arch/lpc21/test/bootloader/bl.elf
-
-ms:
- cd $(AIRBORNE)/arch/lpc21/lpcusb; make
- cd $(AIRBORNE)/arch/lpc21/lpcusb/examples; make
-
-upload_ms ms.upload: ms
- $(PAPARAZZI_SRC)/sw/ground_segment/lpc21iap/lpc21iap
$(AIRBORNE)/arch/lpc21/lpcusb/examples/msc.elf
-
-#####
-#####
-
-doxygen:
- mkdir -p dox
- doxygen Doxyfile
-
-run_sitl :
- $(PAPARAZZI_HOME)/var/$(AIRCRAFT)/sim/simsitl
-
-install :
- make -f Makefile.install PREFIX=$(PREFIX)
-
-uninstall :
- make -f Makefile.install PREFIX=$(PREFIX) uninstall
-
-DISTRO=lenny
-deb :
- chmod u+x debian/rules
- cp debian/control.$(DISTRO) debian/control
- cp debian/changelog.$(DISTRO) debian/changelog
- dpkg-buildpackage $(DEBFLAGS) -Ivar -rfakeroot
-
-fast_deb:
- make deb OCAMLC=ocamlc.opt DEBFLAGS=-b
-
-clean:
- rm -fr dox build-stamp configure-stamp conf/%gconf.xml debian/files
debian/paparazzi-arm7 debian/paparazzi-avr debian/paparazzi-base
debian/paparazzi-bin debian/paparazzi-dev
- rm -f $(MESSAGES_H) $(MESSAGES2_H) $(UBX_PROTOCOL_H) $(DL_PROTOCOL_H)
- find . -mindepth 2 -name Makefile -exec sh -c '$(MAKE) -C `dirname {}`
$@' \;
- find . -name '*~' -exec rm -f {} \;
-
-dist_clean : clean
-
-
-ab_clean:
- find sw/airborne -name '*~' -exec rm -f {} \;
-
-test_all_example_airframes:
- $(MAKE) AIRCRAFT=BOOZ2_A2 clean_ac ap
- $(MAKE) AIRCRAFT=MJ5 clean_ac ap sim
- $(MAKE) AIRCRAFT=TJ1 clean_ac ap sim
- $(MAKE) AIRCRAFT=HITL clean_ac ap
- $(MAKE) AIRCRAFT=DM clean_ac ap sim
- $(MAKE) AIRCRAFT=CSC clean_ac ap
Deleted: paparazzi-software/trunk/Makefile.ac
===================================================================
--- paparazzi-software/trunk/Makefile.ac 2010-11-19 21:17:29 UTC (rev
6430)
+++ paparazzi-software/trunk/Makefile.ac 2010-11-19 21:22:39 UTC (rev
6431)
@@ -1,183 +0,0 @@
-# Hey Emacs, this is a -*- makefile -*-
-# Paparazzi main $Id$
-# Copyright (C) 2004 Pascal Brisset Antoine Drouin
-#
-# This file is part of paparazzi.
-#
-# paparazzi is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# paparazzi is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with paparazzi; see the file COPYING. If not, write to
-# the Free Software Foundation, 59 Temple Place - Suite 330,
-# Boston, MA 02111-1307, USA.
-
-# Preprocessing of XML configuration files
-
-PAPARAZZI_SRC=$(shell pwd)
-
-include conf/Makefile.local
-
-CONF=$(PAPARAZZI_HOME)/conf
-CONF_XML=$(CONF)/conf.xml
-AIRBORNE=sw/airborne
-MESSAGES_XML = $(CONF)/messages.xml
-ACINCLUDE = $(PAPARAZZI_HOME)/var/$(AIRCRAFT)
-AIRCRAFT_CONF_DIR = $(ACINCLUDE)/conf
-AIRFRAME_H=$(ACINCLUDE)/airframe.h
-
-ifndef PERIODIC_FREQ
-PERIODIC_FREQ = 60
-endif
-
-PERIODIC_H=$(ACINCLUDE)/periodic.h
-RADIO_H=$(ACINCLUDE)/radio.h
-FLIGHT_PLAN_H=$(ACINCLUDE)/flight_plan.h
-FLIGHT_PLAN_XML=$(ACINCLUDE)/flight_plan.xml
-SETTINGS_H=$(ACINCLUDE)/settings.h
-SETTINGS_XMLS=$(patsubst %,$(CONF)/%,$(SETTINGS))
-SETTINGS_XML=$(ACINCLUDE)/settings.xml
-SETTINGS_MODULES=$(ACINCLUDE)/settings_modules.xml
-MAKEFILE_AC=$(ACINCLUDE)/Makefile.ac
-SETTINGS_FILE=$(SETTINGS:settings%=%)
-#TUNING_FILE=$(subst ,_,$(SETTINGS:settings/%.xml=%)).h
-TUNING_H=$(ACINCLUDE)/tuning.h
-SUPERVISION=./paparazzi
-MAKE=make PAPARAZZI_SRC=$(PAPARAZZI_SRC) PAPARAZZI_HOME=$(PAPARAZZI_HOME)
-MODULES_H=$(ACINCLUDE)/modules.h
-MODULES_DIR=$(PAPARAZZI_HOME)/conf/modules/
-AIRCRAFT_MD5=$(AIRCRAFT_CONF_DIR)/aircraft.md5
-
-# "make Q=''" to get full echo
-Q=@
-
-init:
- @[ -d $(PAPARAZZI_HOME) ] || (echo "Copying config example in your
$(PAPARAZZI_HOME) directory"; mkdir -p $(PAPARAZZI_HOME); cp -a conf
$(PAPARAZZI_HOME); cp -a data $(PAPARAZZI_HOME); mkdir -p
$(PAPARAZZI_HOME)/var/maps; mv $(PAPARAZZI_HOME)/data/maps/trtqtttqtsrrt*.jpg
$(PAPARAZZI_HOME)/var/maps; mkdir -p $(PAPARAZZI_HOME)/var/include)
-
-demo:
- $(SUPERVISION)
-
-ifeq ($(MAKECMDGOALS),all_ac_h)
--include $(MAKEFILE_AC)
-endif
-
-
-
-all_ac_h: $(AIRFRAME_H) $(MODULES_H) $(SETTINGS_H) $(TUNING_H) $(MAKEFILE_AC)
$(PERIODIC_H)
- @echo "TARGET: " $(TARGET) "\n" > $(ACINCLUDE)/$(TARGET)_srcs.list
- @echo "CFLAGS: " $($(TARGET).CFLAGS) "\n" >>
$(ACINCLUDE)/$(TARGET)_srcs.list
- @echo "srcs: " $($(TARGET).srcs) >> $(ACINCLUDE)/$(TARGET)_srcs.list
-
-radio_ac_h : $(RADIO_H)
-
-flight_plan_ac_h : $(FLIGHT_PLAN_H) $(FLIGHT_PLAN_XML)
-
-makefile_ac: $(MAKEFILE_AC)
-
-$(AIRFRAME_H) : $(CONF)/$(AIRFRAME_XML) $(CONF_XML) $(AIRCRAFT_MD5)
- @echo BUILD $@
- $(Q)$(TOOLS)/gen_airframe.out $(AC_ID) $(AIRCRAFT) $(MD5SUM) $< >
/tmp/airframe.h
- $(Q)mv /tmp/airframe.h $@
- $(Q)cp $(CONF)/airframes/airframe.dtd $(AIRCRAFT_CONF_DIR)/airframes
-
-$(RADIO_H) : $(CONF)/$(RADIO) $(CONF_XML) $(TOOLS)/gen_radio.out
- @echo BUILD $@
- $(Q)$(TOOLS)/gen_radio.out $< > /tmp/radio.h
- $(Q)mv /tmp/radio.h $@
- $(Q)cp $< $(AIRCRAFT_CONF_DIR)/radios
-
-$(PERIODIC_H) : $(CONF)/$(AIRFRAME_XML) $(MESSAGES_XML) $(CONF_XML)
$(CONF)/$(TELEMETRY) $(MAKEFILE_AC)
- @echo BUILD $@
- $(Q)$(TOOLS)/gen_periodic.out $(CONF)/$(AIRFRAME_XML) $(MESSAGES_XML)
$(CONF)/$(TELEMETRY) $(PERIODIC_FREQ) > $@
- $(Q)chmod a+r $@
- $(Q)cp $< $(AIRCRAFT_CONF_DIR)
- $(Q)cp $(CONF)/$(TELEMETRY) $(AIRCRAFT_CONF_DIR)/telemetry
-
-$(FLIGHT_PLAN_H) : $(CONF)/$(FLIGHT_PLAN) $(CONF_XML)
$(TOOLS)/gen_flight_plan.out
- @echo BUILD $@
- $(Q)$(TOOLS)/gen_flight_plan.out $< > /tmp/$(AC_ID)_fp.h
- $(Q)mv /tmp/$(AC_ID)_fp.h $@
- $(Q)chmod a+r $@
- $(Q)cp $< $(AIRCRAFT_CONF_DIR)/flight_plans
-
-$(FLIGHT_PLAN_XML) : $(CONF)/$(FLIGHT_PLAN) $(CONF_XML)
$(TOOLS)/gen_flight_plan.out
- @echo BUILD $@
- $(Q)$(TOOLS)/gen_flight_plan.out -dump $< > $@
- $(Q)chmod a+r $@
-
-$(SETTINGS_H) : $(SETTINGS_XMLS) $(CONF_XML) $(SETTINGS_MODULES)
$(TOOLS)/gen_settings.out
- @echo BUILD $@
- $(Q)$(TOOLS)/gen_settings.out $(SETTINGS_XML) $(SETTINGS_XMLS)
$(SETTINGS_MODULES) > $@
- $(Q)chmod a+r $@
- $(Q)cp $(SETTINGS_XMLS) $(AIRCRAFT_CONF_DIR)/settings
-
-$(TUNING_H) : $(SETTINGS_XMLS) $(CONF_XML) $(TOOLS)/gen_tuning.out
- @echo BUILD $@
- $(Q)$(TOOLS)/gen_tuning.out $(SETTINGS_XMLS) > $@
-
-$(MODULES_H) : $(CONF)/$(AIRFRAME_XML) $(TOOLS)/gen_modules.out
$(CONF)/modules/*.xml
- @echo BUILD $@
- $(Q)$(TOOLS)/gen_modules.out $(MODULES_DIR) $(SETTINGS_MODULES) $< > $@
- $(Q)chmod a+r $@
-
-$(SETTINGS_MODULES) : $(MODULES_H)
-
-%.ac_h : $(TOOLS)/gen_aircraft.out
- $(Q)if (expr "$(AIRCRAFT)"); then : ; else echo "AIRCRAFT undefined:
type 'make AIRCRAFT=AircraftName ...'"; exit 1; fi
- @echo BUILD $(AIRCRAFT), TARGET $*
- +$(Q)PAPARAZZI_SRC=$(PAPARAZZI_SRC) PAPARAZZI_HOME=$(PAPARAZZI_HOME)
TARGET=$* Q=$(Q) $(TOOLS)/gen_aircraft.out $(AIRCRAFT)
-
-%.compile: %.ac_h
- cd $(AIRBORNE); $(MAKE) TARGET=$* all
-
-%.wr_fuses: %.compile
- cd $(AIRBORNE); $(MAKE) TARGET=$* wr_fuses
-
-%.rd_fuses: %.compile
- cd $(AIRBORNE); $(MAKE) TARGET=$* rd_fuses
-
-%.check_fuses: %.compile
- cd $(AIRBORNE); $(MAKE) TARGET=$* check_fuses
-
-%.erase: %.compile
- cd $(AIRBORNE); $(MAKE) TARGET=$* erase
-
-%.upload: %.compile
- cd $(AIRBORNE); $(MAKE) TARGET=$* upload
-
-# Copy from Makefile, to get it in the paparazzi-bin package
-BOOTLOADER_DEVICE=/dev/ttyUSB0
-tiny_bl.upload:
- lpc21isp -control $(AIRBORNE)/arch/lpc21/test/bootloader/bl.hex
$(BOOTLOADER_DEVICE) 38400 12000
-
-jsbsim jsbsim.compile: jsbsim.ac_h
- cd $(AIRBORNE); $(MAKE) TARGET=jsbsim ARCHI=jsbsim ARCH=jsbsim all
-
-sim sim.compile: sim.ac_h
- cd $(AIRBORNE); $(MAKE) TARGET=sim ARCHI=sim ARCH=sim all
-
-# Rules for backward compatibility (old guys are used to !)
-fbw : fbw.compile
-ap: ap.compile
-upload_fbw: fbw.upload
-upload_ap: ap.upload
-erase_fbw: fbw.erase
-erase_ap: ap.erase
-wr_fuses_ap: ap.wr_fuses
-wr_fuses_fbw: fbw.wr_fuses
-rd_fuses_ap: ap.rd_fuses
-rd_fuses_fbw: fbw.rd_fuses
-check_fuses_ap: ap.check_fuses
-check_fuses_fbw: fbw.check_fuses
-hard_ac ac: ac_h fbw ap
-
-clean_ac :
- $(Q)if (expr "$(AIRCRAFT)"); then : ; else echo "AIRCRAFT undefined:
type 'make AIRCRAFT=AircraftName ...'"; exit 1; fi
- rm -fr $(PAPARAZZI_HOME)/var/$(AIRCRAFT)
Deleted: paparazzi-software/trunk/Makefile.install
===================================================================
--- paparazzi-software/trunk/Makefile.install 2010-11-19 21:17:29 UTC (rev
6430)
+++ paparazzi-software/trunk/Makefile.install 2010-11-19 21:22:39 UTC (rev
6431)
@@ -1,148 +0,0 @@
-# Hey Emacs, this is a -*- makefile -*-
-
-# Installation of the files in the system tree
-
-PREFIX=/
-DESTDIR=$(PREFIX)/usr/share/paparazzi
-INSTALL=install -o root
-INSTALLDATA=install -o root -m 644
-
-install : install_files
-# post_install
-
-install_files: install_data install_conf install_bin install_libs
install_tools install_airborne_sources
-
-post_install :
- debian/paparazzi-bin.postinst
-
-install_data:
- $(INSTALL) -d $(DESTDIR)/data/maps
- $(INSTALLDATA) data/maps/muret_UTM.xml data/maps/muret_UTM.gif
$(DESTDIR)/data/maps
- $(INSTALL) -d $(DESTDIR)/data/pictures/gcs_icons
- $(INSTALLDATA) var/maps/trtqtttqtsrrtstq*.jpg
var/maps/trtqtttqtsrrttsr*.jpg $(DESTDIR)/data/maps
- $(INSTALLDATA) data/pictures/*.gif data/pictures/*.svg
data/pictures/*.jpg data/pictures/*.png $(DESTDIR)/data/pictures
- $(INSTALLDATA) data/pictures/gcs_icons/*.png
$(DESTDIR)/data/pictures/gcs_icons
- $(INSTALL) -d $(PREFIX)/usr/share/pixmaps
- $(INSTALLDATA) data/pictures/penguin_icon.png
$(PREFIX)/usr/share/pixmaps/paparazzi.png
- $(INSTALL) -d $(DESTDIR)/data/srtm
- $(INSTALLDATA) data/srtm/N43E001.hgt.bz2 $(DESTDIR)/data/srtm
-
-
-install_conf:
- $(INSTALL) -d $(DESTDIR)/conf
- $(INSTALLDATA) conf/conf.xml.example $(DESTDIR)/conf/conf.xml
- $(INSTALLDATA) conf/control_panel.xml.example
$(DESTDIR)/conf/control_panel.xml
- $(INSTALLDATA) conf/messages.xml $(DESTDIR)/conf/
- $(INSTALLDATA) conf/messages.dtd $(DESTDIR)/conf/
- $(INSTALLDATA) conf/gui.xml $(DESTDIR)/conf/
- $(INSTALL) -d $(DESTDIR)/conf/airframes
- $(INSTALLDATA) conf/airframes/airframe.dtd $(DESTDIR)/conf/airframes
- $(INSTALLDATA) conf/airframes/microjet5.xml $(DESTDIR)/conf/airframes
- $(INSTALLDATA) conf/airframes/twinstar1.xml $(DESTDIR)/conf/airframes
- $(INSTALLDATA) conf/airframes/twinjet1.xml $(DESTDIR)/conf/airframes
- $(INSTALLDATA) conf/airframes/tiny_hitl.xml $(DESTDIR)/conf/airframes
- $(INSTALLDATA) conf/airframes/booz2_a2.xml $(DESTDIR)/conf/airframes
- $(INSTALL) -d $(DESTDIR)/conf/autopilot
- $(INSTALLDATA) conf/autopilot/*.makefile $(DESTDIR)/conf/autopilot
- $(INSTALLDATA) conf/autopilot/*.h $(DESTDIR)/conf/autopilot
- $(INSTALL) -d $(DESTDIR)/conf/flight_plans
- $(INSTALLDATA) conf/flight_plans/*.dtd $(DESTDIR)/conf/flight_plans
- $(INSTALLDATA) conf/flight_plans/*.xml $(DESTDIR)/conf/flight_plans
- $(INSTALL) -d $(DESTDIR)/conf/gps
- $(INSTALLDATA) conf/gps/Makefile $(DESTDIR)/conf/gps
- $(INSTALLDATA) conf/gps/ublox_conf.c $(DESTDIR)/conf/gps
- $(INSTALLDATA) conf/gps/README $(DESTDIR)/conf/gps
- $(INSTALLDATA) conf/gps/*.inf $(DESTDIR)/conf/gps
- $(INSTALLDATA) conf/gps/*.txt $(DESTDIR)/conf/gps
- $(INSTALL) -d $(DESTDIR)/conf/radios
- $(INSTALLDATA) conf/radios/radio.dtd $(DESTDIR)/conf/radios
- $(INSTALLDATA) conf/radios/*.xml $(DESTDIR)/conf/radios
- $(INSTALL) -d $(DESTDIR)/conf/telemetry
- $(INSTALLDATA) conf/telemetry/telemetry.dtd $(DESTDIR)/conf/telemetry
- $(INSTALLDATA) conf/telemetry/*.xml $(DESTDIR)/conf/telemetry
- $(INSTALL) -d $(DESTDIR)/conf/settings
- $(INSTALLDATA) conf/settings/settings.dtd $(DESTDIR)/conf/settings
- $(INSTALLDATA) conf/settings/*.xml $(DESTDIR)/conf/settings
- $(INSTALL) -d $(DESTDIR)/conf/gcs
- $(INSTALLDATA) conf/gcs/layout.dtd $(DESTDIR)/conf/gcs
- $(INSTALLDATA) conf/gcs/*.xml $(DESTDIR)/conf/gcs
- $(INSTALL) -d $(PREFIX)/etc/udev/rules.d
- $(INSTALLDATA) conf/system/udev/rules/*.rules $(PREFIX)/etc/udev/rules.d
- $(INSTALL) -d $(PREFIX)/etc/modprobe.d
- $(INSTALLDATA) conf/system/modprobe.d/paparazzi $(PREFIX)/etc/modprobe.d
- $(INSTALL) -d $(PREFIX)/usr/share/applications
- $(INSTALLDATA) debian/paparazzi.desktop $(PREFIX)/usr/share/applications
-
-
-install_bin:
- $(INSTALL) -d $(PREFIX)/usr/bin/
- $(INSTALL) -d $(DESTDIR)/sw/supervision
- $(INSTALL) sw/supervision/paparazzicenter.glade
$(DESTDIR)/sw/supervision
- $(INSTALL) sw/supervision/*.cmo $(DESTDIR)/sw/supervision
- $(INSTALL) paparazzi-make $(PREFIX)/usr/bin/
- $(INSTALLDATA) -d $(DESTDIR)/sw/simulator
- $(INSTALL) sw/simulator/*.cmo $(DESTDIR)/sw/simulator
- $(INSTALL) sw/simulator/launchsitl $(DESTDIR)/sw/simulator
- $(INSTALL) -d $(DESTDIR)/sw/ground_segment/cockpit
- $(INSTALL) -d $(DESTDIR)/sw/ground_segment/tmtc
- $(INSTALL) -d $(DESTDIR)/sw/ground_segment/multimon
- $(INSTALLDATA) sw/ground_segment/cockpit/*.cmo
$(DESTDIR)/sw/ground_segment/cockpit
- $(INSTALLDATA) sw/ground_segment/cockpit/gcs.glade
$(DESTDIR)/sw/ground_segment/cockpit
- $(INSTALLDATA) sw/ground_segment/tmtc/*.cmo
$(DESTDIR)/sw/ground_segment/tmtc
- $(INSTALL) sw/ground_segment/tmtc/boa $(DESTDIR)/sw/ground_segment/tmtc
- $(INSTALLDATA) sw/ground_segment/multimon/multimon.cma
$(DESTDIR)/sw/ground_segment/multimon
- $(INSTALLDATA) sw/ground_segment/multimon/libmultimon.a
$(DESTDIR)/sw/ground_segment/multimon
- $(INSTALLDATA) sw/ground_segment/multimon/dllmultimon.so
$(DESTDIR)/sw/ground_segment/multimon
- $(INSTALL) -d $(DESTDIR)/sw/logalizer
- $(INSTALLDATA) sw/logalizer/*.cm[ox] $(DESTDIR)/sw/logalizer
- $(INSTALLDATA) sw/logalizer/*.o $(DESTDIR)/sw/logalizer
- $(INSTALLDATA) sw/logalizer/export.glade $(DESTDIR)/sw/logalizer
- ln -sf ../share/paparazzi/sw/supervision/paparazzicenter
$(PREFIX)/usr/bin/paparazzi
-
-install_libs:
- $(INSTALL) -d $(DESTDIR)/sw/lib/ocaml
- $(INSTALLDATA) sw/lib/ocaml/*.cma $(DESTDIR)/sw/lib/ocaml
- $(INSTALLDATA) sw/lib/ocaml/*.cmxa $(DESTDIR)/sw/lib/ocaml
- $(INSTALLDATA) sw/lib/ocaml/*.so $(DESTDIR)/sw/lib/ocaml
- $(INSTALLDATA) sw/lib/ocaml/*.a $(DESTDIR)/sw/lib/ocaml
- $(INSTALLDATA) sw/lib/ocaml/*.cmi $(DESTDIR)/sw/lib/ocaml
- $(INSTALLDATA) sw/lib/ocaml/myGtkInit.cmo $(DESTDIR)/sw/lib/ocaml
- $(INSTALLDATA) sw/lib/ocaml/widgets.glade $(DESTDIR)/sw/lib/ocaml
-
-install_tools:
- $(INSTALLDATA) Makefile.ac $(DESTDIR)
- $(INSTALL) -d $(DESTDIR)/sw/tools/
- $(INSTALLDATA) conf/Makefile* $(DESTDIR)/conf
- $(INSTALL) sw/tools/*.out $(DESTDIR)/sw/tools/
- rm -f $(DESTDIR)/sw/tools/gen_flight_plan.out
- $(INSTALLDATA) sw/tools/fp_syntax.cmo $(DESTDIR)/sw/tools
- $(INSTALLDATA) sw/tools/fp_parser.cmo $(DESTDIR)/sw/tools
- $(INSTALLDATA) sw/tools/fp_lexer.cmo $(DESTDIR)/sw/tools
- $(INSTALLDATA) sw/tools/fp_proc.cmo $(DESTDIR)/sw/tools
- $(INSTALLDATA) sw/tools/gen_flight_plan.cmo $(DESTDIR)/sw/tools
- $(INSTALLDATA) sw/tools/extract_makefile.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_aircraft.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_airframe.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_messages.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_periodic.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_radio.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_tuning.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_settings.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_tuning.ml $(DESTDIR)/sw/tools/
- $(INSTALLDATA) sw/tools/gen_ubx.ml $(DESTDIR)/sw/tools/
- $(INSTALL) -d $(DESTDIR)/sw/ground_segment/lpc21iap
- $(INSTALL) sw/ground_segment/lpc21iap/lpc21iap
$(DESTDIR)/sw/ground_segment/lpc21iap/
- $(INSTALL) -d $(DESTDIR)/sw/simulator
- $(INSTALLDATA) sw/simulator/sitl.cma $(DESTDIR)/sw/simulator
- $(INSTALLDATA) sw/simulator/simsitl.ml $(DESTDIR)/sw/simulator
- $(INSTALLDATA) sw/simulator/sim.cmi $(DESTDIR)/sw/simulator
- $(INSTALLDATA) sw/simulator/sitl.cmi $(DESTDIR)/sw/simulator
- $(INSTALLDATA) sw/simulator/libsitl.a $(DESTDIR)/sw/simulator
- $(INSTALL) sw/simulator/simhitl $(DESTDIR)/sw/simulator
-
-install_airborne_sources:
- $(INSTALL) -d $(DESTDIR)/sw/
- tar --exclude=CVS -cf - sw/airborne/ | tar -C $(DESTDIR) -xf -
- $(INSTALL) -d $(DESTDIR)/sw/include
- $(INSTALLDATA) sw/include/std.h $(DESTDIR)/sw/include
- $(INSTALLDATA) var/include/*.h $(DESTDIR)/sw/include
Deleted: paparazzi-software/trunk/Makefile.sys
===================================================================
--- paparazzi-software/trunk/Makefile.sys 2010-11-19 21:17:29 UTC (rev
6430)
+++ paparazzi-software/trunk/Makefile.sys 2010-11-19 21:22:39 UTC (rev
6431)
@@ -1,48 +0,0 @@
-# Paparazzi main $Id$
-# Copyright (C) 2004 Pascal Brisset Antoine Drouin
-#
-# This file is part of paparazzi.
-#
-# paparazzi is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# paparazzi is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with paparazzi; see the file COPYING. If not, write to
-# the Free Software Foundation, 59 Temple Place - Suite 330,
-# Boston, MA 02111-1307, USA.
-
-PAPARAZZI_DIR=/usr/share/paparazzi
-ifeq ($(PAPARAZZI_HOME),)
-PAPARAZZI_HOME=$(HOME)/paparazzi
-endif
-
-ac_h :
- $(PAPARAZZI_DIR)/bin/gen_aircraft.out $(AIRCRAFT)
-
-sim_sitl :
- cd $(PAPARAZZI_DIR)/sw/simulator; $(MAKE) sim_sitl AIRCRAFT=$(AIRCRAFT)
-
-clean_ac :
- rm -fr $(PAPARAZZI_HOME)/var/$(AIRCRAFT)
-
-run_sitl :
- $(PAPARAZZI_HOME)/var/$(AIRCRAFT)/sim/simsitl
-
-ap:
- cd $(PAPARAZZI_DIR)/sw/airborne/autopilot; $(MAKE) all
-
-fbw:
- cd $(PAPARAZZI_DIR)/sw/airborne/fly_by_wire; $(MAKE) all
-
-upload_ap:
- cd $(PAPARAZZI_DIR)/sw/airborne/autopilot; $(MAKE) upload
-
-upload_fbw:
- cd $(PAPARAZZI_DIR)/sw/airborne/fly_by_wire; $(MAKE) upload
Deleted: paparazzi-software/trunk/README
===================================================================
--- paparazzi-software/trunk/README 2010-11-19 21:17:29 UTC (rev 6430)
+++ paparazzi-software/trunk/README 2010-11-19 21:22:39 UTC (rev 6431)
@@ -1,99 +0,0 @@
-# Paparazzi $Id$
-# Copyright (C) 2003-2006 Pascal Brisset Antoine Drouin
-#
-# This file is part of paparazzi.
-#
-# paparazzi is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# paparazzi is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with paparazzi; see the file COPYING. If not, write to
-# the Free Software Foundation, 59 Temple Place - Suite 330,
-# Boston, MA 02111-1307, USA.
-
-Intro
------
-
-Paparazzi is an attempt to develop a cheap fixed wing UAV (Unmanned Air
-Vehicle). As of today we have successfully flown autonomously several small
-electro powered fixed wing aircraft (Twinstar, Microjet, ...).
-
-Up to date informations are available from the wiki website
-
- paparazzi.enac.fr
-
-and from the mailing list (http://savannah.nongnu.org/mail/?group=paparazzi)
-and the IRC channel (freenode, #paparazzi).
-
-Directories quick and dirty description:
----------------------------------------
-
-conf: the configuration directory (airframe, radio, ... descriptions).
-
-data: where to put read-only data (e.g. maps, terrain elevation files, icons)
-
-hw: hardware (electronic schemas, PCBs, ...)
-
-sw: software (onboard, ground station, simulation, ...)
-
-var: products of compilation, cache for the map tiles, ...
-
-debian: Debian packaging control files
-
-
-Required Software
------------------
-
-Installation is described in the wiki (paparazzi.enac.fr/wiki/Installation).
-Main requirements include
- - OCaml (ocaml.org), xml-light library (http://tech.motion-twin.com/xmllight)
- - gcc, GTK2, Glib2, libgnomecanvas, libxml2
- - ARM7 micro-controller development environnment (gcc, loader, libc, binutils)
- - ...
-
-For Debian or Ubuntu users, required packages are available at
-
- http://paparazzi.enac.fr/debian
-
-Installation of the meta-package "paparazzi-dev" will install
-everything needed to compile this project (if something is missing,
-please ask) for simulation. "paparazzi-arm7" is required to compile
-the code for the ARM based boards.
-
-Compilation and demo simulation
--------------------------------
-
- 1) "make" in the top directory to compile all the libraries and tools.
-
- 2) "./paparazzi" to run the Paparazzi Center
-
- 3) Select the "MJ5" or the "TJ1" aircraft in the upper-left A/C
-combo box. Select "sim" from upper-middle "target" combo box. Click
-"Build". When the compilation is finished, select "Simulation" from
-the upper-right session combo box and click "Execute".
-
- 4) In the GCS, wait about 10s for the aircraft to be in the "Holding
-point" navigation block. Switch to the "Takeoff" block (lower-left
-blue airway button in the strip). Takeoff with the green launch button.
-
-Uploading of the embedded software
-----------------------------------
-
- 1) Power the flight controller board while it is connected to the PC with
-the USB cable.
-
- 2) From the Paparazzi center, select the "ap" target, and click "Upload".
-
-
-Flight
--------------------------------------
-
- 1) From the Paparazzi Center, select the flight session and ... do
-the same than in simulation !
Deleted: paparazzi-software/trunk/TODO
===================================================================
--- paparazzi-software/trunk/TODO 2010-11-19 21:17:29 UTC (rev 6430)
+++ paparazzi-software/trunk/TODO 2010-11-19 21:22:39 UTC (rev 6431)
@@ -1,134 +0,0 @@
-
-
-add date/time of generation in generated code
-
-##############################################################
-
-add an irc client to morphix - preconfigured for paparazzi channel
-
-
-
-make clean doesn't delete boa config
-
-make a "single node" mode where boa isn't needed and serve file:// URL
-force ivybus to 127 in single node
-default to that mode
-
-
-
-
-
-
-######################################## obsolete ? ##############
-
-dans flybywire
-chop servo ne depends pas du servo
-
-
-pour les missions
-possibilit\xE9 de "transformer" (rotation Z, translation XYZ) une mission
-
-possibilitite de faire la meme chose pour une partie des waypoints (on en a
une partie pour les evolutions et une partie pour le circuit d'atterissage. On
deplace ceux du circuit d'atterissage pour qu'il colle a la piste. et on
deplace ceux des evolution pour etre en face du jury :)
-
-
-On stocke la/les transformations et on peut avoir des missions communes
muret/ricou
-
-des declarations de points locales aux blocs et des transformations par blocs
-
-
-faire medit avec visu3d
-
-proposer d'ajouter un waypoint en relatif par rapport a un autre - et en
coordonnees polaires (dist, QDM)
-
-
-
-
-
-l'interface du captureur de video - c'est aussi visu3d . Il a une liste de
textures (photos) et on peut les transformer. La description est sauv\xE9es
dans un fichier xml et peut etre recharg\xE9e. les photos vont dans var/photos
-
-
-dans visu3d, il faudrait pouvoir pivoter en Z sur la position courante (en
tenant compte du zoom )
-
-
-######################
-
-logger les simus comme les vols - y penser en refaisant receive - code commun
-
-Pour les simus a plusieurs avions, il doit y avoir partage d'un certain nombre
d'informations entre les differentes instances des simu (par exemple le vent)
-
-Dans un circle, il faut afficher le QDR - calcul au sol??
-
-Pour les missions, il faudrait pouvoir dire . faire un cercle pendant 180\xB0
ou faire un cercle pendant n secondes. Il faudrait donc disposer du temps
depuis le block et du de l'angle parcouru depuis le debut du cercle.
-C'est pour faire un palier en haut de la mont\xE9. Pour laisser le terme
accumulateur se recaler avant la descente.
-
-###########################################
-
-Sujet : procedure automatique d'interuption de vol pour microdrone
-
--identifier des scenarios:
-
-cause de l'interuption : autonomie, meteo, defaillance systeme
-
--modeliser la zone d'evolution et les autres contraintres (systemes
defaillants, meteo)
-
-(dans un meeting, on veut a tout prix eviter le public, les routes etc...)
-
-- initialisation
-- iteratif ?
-
-#######################################
-
-integrer les gazs pour estimer l'autonomie restante
-
-
-###########################################
-
-
-Sujet Drone Thales
-
-Les eleves (1A ou 2A) construisent un avion et apprennent a le faire voler
d'ici juillet.
-
-commande PCB
-commande composants radiospare/melexys/coronis/ublox
-labo pour assembler (labo micro onde ?)
-
-commande garat (avion, moteur, servos, batteries, radiocommande etc....)
-achat de petit outillage (dremel, fer a souder etc...)
-assemblage au labo drone
-
-cours de pilotages sur le twinstar
-
-On leur donne les petits projets pendant l'ann\xE9e sur Paparazzi.
-
-
-
-############################################
-
-mettre les projets enac sur la page web enac
-
-############################################
-
-
-Pourquoi on ne laisse pas message.xml modifiable, pour les taux de telemesure
par exemple.
-
-on split les Makefiles
-
-
-###########
-
-manque gerbmerge dans les dependance??? ha non ca n'existe pas... a packager !
-
-
->
->
-> - Pitch should more be in degree than in radian in flight plan files.
->It could be in the future version of Paparazzi.
->
->
-> - It's strange MIN_HEIGHT_CARROT and MAX_HEIGHT_CARROT are in the
->code. Shouldn't it be in a conf file so as to change it ?
->
-- In the same way, MIN_SPEED_FOR_TAKEOFF should be in the airframe
-conf file ?
-
-
Deleted: paparazzi-software/trunk/paparazzi
===================================================================
--- paparazzi-software/trunk/paparazzi 2010-11-19 21:17:29 UTC (rev 6430)
+++ paparazzi-software/trunk/paparazzi 2010-11-19 21:22:39 UTC (rev 6431)
@@ -1,15 +0,0 @@
-#!/usr/bin/ocamlrun /usr/bin/ocaml
-#load "unix.cma";;
-let (//) = Filename.concat
-let dirname = Filename.dirname Sys.argv.(0)
-let dirname = if Filename.is_relative dirname && dirname <>
Filename.current_dir_name then Sys.getcwd () // dirname else dirname
-let env =
- Array.map (fun var ->
- let value = try Sys.getenv var with _ -> dirname in
- let value = if value = "." then Sys.getcwd () else value in
- Printf.sprintf "%s=%s" var value)
- [|"PAPARAZZI_SRC"; "PAPARAZZI_HOME"|]
-let com = dirname // "sw/supervision/paparazzicenter";;
-Sys.argv.(0) <- com;;
-let env = Array.append env (Unix.environment ());;
-Unix.execve com Sys.argv env
Deleted: paparazzi-software/trunk/paparazzi-make
===================================================================
--- paparazzi-software/trunk/paparazzi-make 2010-11-19 21:17:29 UTC (rev
6430)
+++ paparazzi-software/trunk/paparazzi-make 2010-11-19 21:22:39 UTC (rev
6431)
@@ -1,3 +0,0 @@
-#!/bin/bash
-
-make -C /usr/share/paparazzi -f Makefile.ac $*
Deleted: paparazzi-software/trunk/paparazzi.osx
===================================================================
--- paparazzi-software/trunk/paparazzi.osx 2010-11-19 21:17:29 UTC (rev
6430)
+++ paparazzi-software/trunk/paparazzi.osx 2010-11-19 21:22:39 UTC (rev
6431)
@@ -1,15 +0,0 @@
-#!/usr/local/bin/ocamlrun /usr/local/bin/ocaml
-#load "unix.cma";;
-let (//) = Filename.concat
-let dirname = Filename.dirname Sys.argv.(0)
-let dirname = if Filename.is_relative dirname && dirname <>
Filename.current_dir_name then Sys.getcwd () // dirname else dirname
-let env =
- Array.map (fun var ->
- let value = try Sys.getenv var with _ -> dirname in
- let value = if value = "." then Sys.getcwd () else value in
- Printf.sprintf "%s=%s" var value)
- [|"PAPARAZZI_SRC"; "PAPARAZZI_HOME"|]
-let com = dirname // "sw/supervision/paparazzicenter";;
-Sys.argv.(0) <- com;;
-let env = Array.append env (Unix.environment ());;
-Unix.execve com Sys.argv env
Deleted: paparazzi-software/trunk/pprz_src_test.sh
===================================================================
--- paparazzi-software/trunk/pprz_src_test.sh 2010-11-19 21:17:29 UTC (rev
6430)
+++ paparazzi-software/trunk/pprz_src_test.sh 2010-11-19 21:22:39 UTC (rev
6431)
@@ -1,7 +0,0 @@
-#! /bin/sh
-if test -z "$PAPARAZZI_SRC"; then
- PAPARAZZI_SRC=/usr/share/paparazzi
- PAPARAZZI_BIN=$PAPARAZZI_SRC/bin
-else
- PAPARAZZI_BIN=$PAPARAZZI_SRC/sw/tools
-fi
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [paparazzi-commits] [6431] removed all software as we moved to git,
Felix Ruess <=