ardupilot/Rover/version.h

#pragma once

#ifndef FORCE_VERSION_H_INCLUDE
#error version.h should never be included directly. You probably want to include AP_Common/AP_FWVersion.h
#endif

#include "ap_version.h"

#define THISFIRMWARE "ArduRover V4.5.0-beta1"

// the following line is parsed by the autotest scripts
#define FIRMWARE_VERSION 4,5,0,FIRMWARE_VERSION_TYPE_BETA

#define FW_MAJOR 4
#define FW_MINOR 5
#define FW_PATCH 0
#define FW_TYPE FIRMWARE_VERSION_TYPE_BETA

#include <AP_Common/AP_FWVersionDefine.h>
APMrover2: use separate header for version macro Having the version macro in the config.h and consequently in the main vehicle header means that whenever the version changes we need to compiler the whole vehicle again. This would not be so bad if we weren't also appending the git hash in the version. In this case, whenever we commit to the repository we would need to recompile everything. Move to a separate header that is include only by its users. Then instead of compiling everything we will compile just a few files. 2016-05-05 19:10:08 -03:00			`#pragma once`

APMrover2: protect version.h from inclusion and use ap_version.h 2017-09-12 15:34:57 -03:00			`#ifndef FORCE_VERSION_H_INCLUDE`
			`#error version.h should never be included directly. You probably want to include AP_Common/AP_FWVersion.h`
			`#endif`

			`#include "ap_version.h"`
Global: use ap_version.h This header is used by waf to contain the generated version macros, particularly using the git hash. For waf it's better to be in a separate header since it then can keep track of changes on it a trigger recompilation. For the make build system, a dummy ap_version.h file has been added in the missing/ folder so both implementations can co-exist. 2016-05-05 19:18:36 -03:00
Rover: version to 4.5.0-beta1 2024-01-25 07:26:32 -04:00			`#define THISFIRMWARE "ArduRover V4.5.0-beta1"`
Rover: add constant structure holding firmware version 2017-08-19 07:04:56 -03:00
			`// the following line is parsed by the autotest scripts`
Rover: version to 4.5.0-beta1 2024-01-25 07:26:32 -04:00			`#define FIRMWARE_VERSION 4,5,0,FIRMWARE_VERSION_TYPE_BETA`
APMrover2: use separate header for version macro Having the version macro in the config.h and consequently in the main vehicle header means that whenever the version changes we need to compiler the whole vehicle again. This would not be so bad if we weren't also appending the git hash in the version. In this case, whenever we commit to the repository we would need to recompile everything. Move to a separate header that is include only by its users. Then instead of compiling everything we will compile just a few files. 2016-05-05 19:10:08 -03:00
Rover: version to 4.0.0-dev 2019-09-16 23:00:05 -03:00			`#define FW_MAJOR 4`
Rover: version to 4.5.0-dev 2023-04-23 21:30:23 -03:00			`#define FW_MINOR 5`
Rover: version to 4.1.0-dev 2020-03-03 23:21:18 -04:00			`#define FW_PATCH 0`
Rover: version to 4.5.0-beta1 2024-01-25 07:26:32 -04:00			`#define FW_TYPE FIRMWARE_VERSION_TYPE_BETA`
ArduRover: Use new AP_FWVersionDefine header Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com> 2020-09-18 13:58:58 -03:00
Rover: version to 4.2.0-dev we have branched for 4.1 so this will make it more clear if an autopilot is using pre or post branch software 2021-07-23 20:51:03 -03:00			`#include <AP_Common/AP_FWVersionDefine.h>`