AP_Arming: standardize inclusion of libaries headers

This commit changes the way libraries headers are included in source files:

 - If the header is in the same directory the source belongs to, so the
 notation '#include ""' is used with the path relative to the directory
 containing the source.

 - If the header is outside the directory containing the source, then we use
 the notation '#include <>' with the path relative to libraries folder.

Some of the advantages of such approach:

 - Only one search path for libraries headers.

 - OSs like Windows may have a better lookup time.
This commit is contained in:
Gustavo Jose de Sousa 2015-08-11 16:28:42 +10:00 committed by Randy Mackay
parent 8fb7098903
commit d25f7b8ed3
2 changed files with 6 additions and 6 deletions

View File

@ -14,8 +14,8 @@
along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
#include <AP_Arming.h>
#include <AP_Notify.h>
#include "AP_Arming.h"
#include <AP_Notify/AP_Notify.h>
extern const AP_HAL::HAL& hal;

View File

@ -3,10 +3,10 @@
#ifndef __AP_ARMING_H__
#define __AP_ARMING_H__
#include <AP_AHRS.h>
#include <AP_HAL.h>
#include <AP_Param.h>
#include <GCS_MAVLink.h>
#include <AP_AHRS/AP_AHRS.h>
#include <AP_HAL/AP_HAL.h>
#include <AP_Param/AP_Param.h>
#include <GCS_MAVLink/GCS_MAVLink.h>
class AP_Arming {
public: