Tree: 85d12efbef

AP_Periph-1.3

Copter-4.2

Copter-4.2-BW

apm_2208

apm_2208-rover

apm_2208-rover-debug

c421

copter407

gps-1.3.1

main

master

master_rangefinder

mission-4.1.18

periph-1.3.1

release-4.2.3

rover_4.3

zr-sdk-4.3.1

zr-v5.0

zr-v5.1

zr/Rover-4.3

zr/main-4.3

zr_rover4.2

数字绿土/zr-v5.0

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '85d12efbef'

${ noResults }

Commit Graph

3 Commits (85d12efbef3ee8fc75912a295d6b93254c7c26a7)

Author	SHA1	Message	Date
Caio Marcelo de Oliveira Filho	19b4ca60c4	AP_HAL: provide AP_HAL_MAIN() ... Move the macros to a single place and reduce the variations not based on board, but based on - The name of the entry-point function, specified by AP_MAIN; - Whether it contains argc/argv arguments or not. The goal here is that programs (vehicles and examples) don't need to include all possible boards to define a main function. Further patches will change the programs.	9 years ago
Gustavo Jose de Sousa	ca5afbfdc9	AP_HAL_Empty: 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.	10 years ago
Pat Hickey	3e3c0f57ae	AP_HAL_Empty: started building out the scaffolding	12 years ago