Mirror/betaflight
1
0
Fork 0
mirror of https://github.com/betaflight/betaflight.git synced 2025-07-17 13:25:30 +03:00
Code Issues Wiki Activity

Adding comments to common PRE and POST (#12196)

Browse source
This commit is contained in:
J Blackman 2023-01-18 12:36:08 +11:00 • committed by GitHub
parent a7cf8f0c6a
commit e5c53597a3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 37 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

18
src/main/target/common_post.h
View file

@ -18,12 +18,26 @@
* If not, see <http://www.gnu.org/licenses/>. * If not, see <http://www.gnu.org/licenses/>.
*/ */
// Touch up configuration
#pragma once #pragma once
#include "build/version.h" #include "build/version.h"
/*
The purpose of this file is to enable / disable any firmware "gates" for features and drivers
that require hardware resources that are either available or not available after the target.h
has been processed.
It should also be used to define anything that should be defined (and is required), but is not
already, to some sort of defaults.
CLOUD_BUILD and CORE_BUILD should not be referenced here.
NOTE: for 4.5 we will be removing any conditions related to specific MCU types, instead
these should be defined in the target.h or in a file that is imported by target.h (in the
case of common settings for a given MCU group)
*/
/* /*
BEGIN HARDWARE INCLUSIONS BEGIN HARDWARE INCLUSIONS

21
src/main/target/common_pre.h
View file

@ -20,6 +20,27 @@
#pragma once #pragma once
/*
The purpose of this file is to enable the firmware "gates" for features and drivers
prior to entering the target.h.
CLOUD_BUILD is used to signify that the build is a user requested build and that the
features to be enabled will be defined ALREADY.
CORE_BUILD is used to signify that the build is a user requested build and that the
features to be enabled will be the minimal set, and all the drivers should be present.
If neither of the above are present then the build should simply be a baseline build
for continuous integration, i.e. the compilation of the majority of features and drivers
dependent on the size of the flash available.
NOTE: for 4.5 we will be removing any conditions related to specific MCU types, instead
these should be defined in the target.h or in a file that is imported by target.h (in the
case of common settings for a given MCU group)
*/
#define USE_PARAMETER_GROUPS #define USE_PARAMETER_GROUPS
// type conversion warnings. // type conversion warnings.
// -Wconversion can be turned on to enable the process of eliminating these warnings // -Wconversion can be turned on to enable the process of eliminating these warnings