Commit 8b206ba9 authored by Nicolas Mellado's avatar Nicolas Mellado

Use git changeset as version number in documentation

parent e8395356
......@@ -21,6 +21,10 @@ if( NOT cmake_build_type_tolower STREQUAL "debug"
message(FATAL_ERROR "Unknown build type \"${CMAKE_BUILD_TYPE}\". Allowed values are Debug, Release, RelWithDebInfo (case-insensitive).")
endif()
# get changeset id
execute_process(COMMAND git rev-parse HEAD OUTPUT_VARIABLE GIT_CHANGESET)
################################################################################
# Add core code source, so it is visible in dev environements #
################################################################################
......@@ -70,6 +74,8 @@ add_custom_target(vitelottes_vg_mesh_renderer_shaders
find_package(Doxygen)
if(DOXYGEN_FOUND)
set (PATATE_PROJECT_NUMBER ${GIT_CHANGESET})
configure_file(${CMAKE_CURRENT_SOURCE_DIR}/doc-src/Doxyfile.in ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile @ONLY)
add_custom_target(doc
......
......@@ -37,7 +37,7 @@ PROJECT_NAME = "Patate Lib"
# This could be handy for archiving the generated documentation or
# if some version control system is used.
PROJECT_NUMBER = 0.4
PROJECT_NUMBER = @PATATE_PROJECT_NUMBER@
# Using the PROJECT_BRIEF tag one can provide an optional one line description
# for a project that appears at the top of each page and should give viewer
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment