Darknet/YOLO v5.0-10-g6abf042
Object Detection Framework
 
Loading...
Searching...
No Matches
darknet_version.h File Reference

The input file darknet_version.h.in is processed by CMake which then creates the header file darknet_version.h. More...

This graph shows which files directly or indirectly include this file:

Macros

#define DARKNET_BRANCH_NAME   "v5"
 Name of the git branch. This is normally "master".
 
#define DARKNET_VERSION_KEYWORD   "Moonlit"
 Various short names used for Darknet:
 
#define DARKNET_VERSION_SHORT   "5.0.10"
 Similar to DARKNET_VERSION_STRING but only contains the first 3 numerical fields.
 
#define DARKNET_VERSION_STRING   "v5.0-10-g6abf042"
 A version string generated by the CMake build process, based on the git tag and hash.
 
#define DARKNET_WEIGHTS_VERSION_MAJOR   0
 Skip the version macros when using tools like Java jextract.
 
#define DARKNET_WEIGHTS_VERSION_MINOR   2
 Skip the version macros when using tools like Java jextract.
 
#define DARKNET_WEIGHTS_VERSION_PATCH   5
 Skip the version macros when using tools like Java jextract.
 
#define DARKNET_WEIGHTS_VERSION_TWEAK   4
 Skip the version macros when using tools like Java jextract.
 

Detailed Description

The input file darknet_version.h.in is processed by CMake which then creates the header file darknet_version.h.

DO NOT EDIT THIS FILE MANUALLY!

Your changes will be overwritten by the build process when the file is re-generated.

Macro Definition Documentation

◆ DARKNET_BRANCH_NAME

#define DARKNET_BRANCH_NAME   "v5"

Name of the git branch. This is normally "master".

◆ DARKNET_VERSION_KEYWORD

#define DARKNET_VERSION_KEYWORD   "Moonlit"

Various short names used for Darknet:

  • v0 is the original Joseph Redmon repo, 2013-2018. (Did not have a "version" command.)
  • v1 is the popular fork maintained by Alexey Bochkovskiy (aka AlexeyAB), 2016-2021. (Did not have a "version" command.)
  • v2 is named "Oak", conversion from old C codebase to C++, Stephane Charette, 2023.
  • v3 is named "Jazz", significant optimizations for both training and inference, Stephane Charette, 2024.
  • v4 is named "Slate", add support for AMD GPU via ROCm, Stephane Charette, 2025.
  • v5 is named "Moonlit", more optimizations, Stephane Charette, 2025

◆ DARKNET_VERSION_SHORT

#define DARKNET_VERSION_SHORT   "5.0.10"

Similar to DARKNET_VERSION_STRING but only contains the first 3 numerical fields.

◆ DARKNET_VERSION_STRING

#define DARKNET_VERSION_STRING   "v5.0-10-g6abf042"

A version string generated by the CMake build process, based on the git tag and hash.

See also
DARKNET_VERSION_SHORT @also Darknet::show_version_info() @also darknet_show_version_info()

◆ DARKNET_WEIGHTS_VERSION_MAJOR

#define DARKNET_WEIGHTS_VERSION_MAJOR   0

Skip the version macros when using tools like Java jextract.

Under normal use, this is not defined and can be ignored. Use darknet_version_short() or darknet_version_string() functions instead. The DARKNET_WEIGHTS_VERSION_* macros identify the version numbers embedded in the header of .weights files. These numbers should only be changed when the internal format of the weights have changed, and do not represent a specific version of the Darknet framework. The "tweak" value is currently unused.

If you're looking for a version number to display in your application, then most likely you want to ignore these macros, and use DARKNET_VERSION_STRING or DARKNET_VERSION_SHORT instead.

◆ DARKNET_WEIGHTS_VERSION_MINOR

#define DARKNET_WEIGHTS_VERSION_MINOR   2

Skip the version macros when using tools like Java jextract.

Under normal use, this is not defined and can be ignored. Use darknet_version_short() or darknet_version_string() functions instead. The DARKNET_WEIGHTS_VERSION_* macros identify the version numbers embedded in the header of .weights files. These numbers should only be changed when the internal format of the weights have changed, and do not represent a specific version of the Darknet framework. The "tweak" value is currently unused.

If you're looking for a version number to display in your application, then most likely you want to ignore these macros, and use DARKNET_VERSION_STRING or DARKNET_VERSION_SHORT instead.

◆ DARKNET_WEIGHTS_VERSION_PATCH

#define DARKNET_WEIGHTS_VERSION_PATCH   5

Skip the version macros when using tools like Java jextract.

Under normal use, this is not defined and can be ignored. Use darknet_version_short() or darknet_version_string() functions instead. The DARKNET_WEIGHTS_VERSION_* macros identify the version numbers embedded in the header of .weights files. These numbers should only be changed when the internal format of the weights have changed, and do not represent a specific version of the Darknet framework. The "tweak" value is currently unused.

If you're looking for a version number to display in your application, then most likely you want to ignore these macros, and use DARKNET_VERSION_STRING or DARKNET_VERSION_SHORT instead.

◆ DARKNET_WEIGHTS_VERSION_TWEAK

#define DARKNET_WEIGHTS_VERSION_TWEAK   4

Skip the version macros when using tools like Java jextract.

Under normal use, this is not defined and can be ignored. Use darknet_version_short() or darknet_version_string() functions instead. The DARKNET_WEIGHTS_VERSION_* macros identify the version numbers embedded in the header of .weights files. These numbers should only be changed when the internal format of the weights have changed, and do not represent a specific version of the Darknet framework. The "tweak" value is currently unused.

If you're looking for a version number to display in your application, then most likely you want to ignore these macros, and use DARKNET_VERSION_STRING or DARKNET_VERSION_SHORT instead.