Rooba
/
flatbuffers
mirror of https://github.com/google/flatbuffers.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Added INCLUDE_PREFIX option for flatbuffers_generate_headers (#5866) 

This option was in an earlier revision of flatbuffers_generate_headers
but was lost while refactoring by mistake. We have it as a function
argument rather than one of the optional flags so that we can use it to
inform the rule where to place the generated headers, so that the file
location matches the prefix that will be added to the filenames in the
generated files.

Also fixed some of the documentation in the file.
This commit is contained in:
Alex Ames 2020-04-23 10:09:19 -07:00 committed by GitHub
parent 40ba170c94
commit 99aa1ef21d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 20 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
CMake/BuildFlatBuffers.cmake
View File

@ -160,22 +160,24 @@ endfunction()
# Arguments: # Arguments:
# TARGET: The name of the target to generate. # TARGET: The name of the target to generate.
# SCHEMAS: The list of schema files to generate code for. # SCHEMAS: The list of schema files to generate code for.
# BINARY_SCHEMAS_DIR: The directory in which to generate binary schemas. # BINARY_SCHEMAS_DIR: Optional. The directory in which to generate binary
# Binary schemas will only be generated if a path is provided. # schemas. Binary schemas will only be generated if a path is provided.
# INCLUDE: Search for includes in the specified paths. (Use this instead of # INCLUDE: Optional. Search for includes in the specified paths. (Use this
# "-I <path>" and the FLAGS option so that CMake is aware of the # instead of "-I <path>" and the FLAGS option so that CMake is aware of
# directories that need to be searched). # the directories that need to be searched).
# FLAGS: A list of any additional flags that you would like to pass to flatc. # INCLUDE_PREFIX: Optional. The directory in which to place the generated
# files. Use this instead of the --include-prefix option.
# FLAGS: Optional. A list of any additional flags that you would like to pass
# to flatc.
# #
# Example: # Example:
# #
# flatbuffers_generate_headers( # flatbuffers_generate_headers(
# TARGET my_generated_headers_target # TARGET my_generated_headers_target
# INCLUDE_PREFIX ${MY_INCLUDE_PREFIX}"
# SCHEMAS ${MY_SCHEMA_FILES} # SCHEMAS ${MY_SCHEMA_FILES}
# BINARY_SCHEMAS_DIR "${MY_BINARY_SCHEMA_DIRECTORY}" # BINARY_SCHEMAS_DIR "${MY_BINARY_SCHEMA_DIRECTORY}"
# FLAGS # FLAGS --gen-object-api)
# --include-prefix "${MY_INCLUDE_PREFIX}"
# --gen-object-api)
# #
# target_link_libraries(MyExecutableTarget # target_link_libraries(MyExecutableTarget
# PRIVATE my_generated_headers_target # PRIVATE my_generated_headers_target
@ -185,6 +187,7 @@ function(flatbuffers_generate_headers)
set(options) set(options)
set(one_value_args set(one_value_args
"TARGET" "TARGET"
"INCLUDE_PREFIX"
"BINARY_SCHEMAS_DIR") "BINARY_SCHEMAS_DIR")
set(multi_value_args set(multi_value_args
"SCHEMAS" "SCHEMAS"
@ -219,6 +222,8 @@ function(flatbuffers_generate_headers)
set(generated_include_dir "${generated_target_dir}") set(generated_include_dir "${generated_target_dir}")
if (NOT ${FLATBUFFERS_GENERATE_HEADERS_INCLUDE_PREFIX} STREQUAL "") if (NOT ${FLATBUFFERS_GENERATE_HEADERS_INCLUDE_PREFIX} STREQUAL "")
set(generated_include_dir "${generated_include_dir}/${FLATBUFFERS_GENERATE_HEADERS_INCLUDE_PREFIX}") set(generated_include_dir "${generated_include_dir}/${FLATBUFFERS_GENERATE_HEADERS_INCLUDE_PREFIX}")
list(APPEND FLATBUFFERS_GENERATE_HEADERS_FLAGS
"--include-prefix" ${FLATBUFFERS_GENERATE_HEADERS_INCLUDE_PREFIX})
endif() endif()
# Create rules to generate the code for each schema. # Create rules to generate the code for each schema.
@ -290,8 +295,7 @@ endfunction()
# #
# This function takes a target name and a list of schemas and Json files. You # This function takes a target name and a list of schemas and Json files. You
# can also specify other flagc flags and options to change the behavior of the # can also specify other flagc flags and options to change the behavior of the
# flatc compiler. Flags are named the same as they would be in the flatc tool # flatc compiler.
# except ALL_CAPS. For example, --strict-json would be passed in as STRICT_JSON.
# #
# Adding this target to your executable ensurses that the flatbuffer binaries # Adding this target to your executable ensurses that the flatbuffer binaries
# are compiled before your executable is run. # are compiled before your executable is run.
@ -300,12 +304,13 @@ endfunction()
# TARGET: The name of the target to generate. # TARGET: The name of the target to generate.
# JSON_FILES: The list of json files to compile to flatbuffers binaries. # JSON_FILES: The list of json files to compile to flatbuffers binaries.
# SCHEMA: The flatbuffers schema of the Json files to be compiled. # SCHEMA: The flatbuffers schema of the Json files to be compiled.
# INCLUDE: Search for includes in the specified paths. (Use this instead of # INCLUDE: Optional. Search for includes in the specified paths. (Use this
# "-I <path>" and the FLAGS option so that CMake is aware of the # instead of "-I <path>" and the FLAGS option so that CMake is aware of
# directories that need to be searched). # the directories that need to be searched).
# OUTPUT_DIR: The directly where the generated flatbuffers binaries should be # OUTPUT_DIR: The directly where the generated flatbuffers binaries should be
# placed. # placed.
# FLAGS: A list of any additional flags that you would like to pass to flatc. # FLAGS: Optional. A list of any additional flags that you would like to pass
# to flatc.
# #
# Example: # Example:
# #