beenull/ladybird
1
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2024-11-21 23:20:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6
ladybird/Meta/CMake/code_generators.cmake

82 lines
3.6 KiB
CMake
Raw Permalink Normal View History

Meta: Move code generator helpers to their own CMake helper file compile_gml, compile_ipc, and generate_state_machine all use host tools to generate sources for the target build. As part of trying to organize host tools into a common area, let's move these helper rules to a common file that we can add other host tools to later. And, keep the host tool helpers separate from the CMake target helpers for apps and libraries.
2021-08-07 23:37:09 +00:00
#
# Functions for generating sources using host tools
#
Meta: Make embed_as_string_view.py produce Strings instead This is only used for CSS style sheets. One case wants it as a String, and the others don't care, but will in future also want to have the source as a String.
2024-08-22 11:42:12 +00:00
function(embed_as_string name source_file output source_variable_name)
Meta: Make `embed_as_string_view.py` usable by CMake builds :^)
2023-08-23 19:38:28 +00:00
cmake_parse_arguments(PARSE_ARGV 4 EMBED_STRING_VIEW "" "NAMESPACE" "")
set(namespace_arg "")
if (EMBED_STRING_VIEW_NAMESPACE)
set(namespace_arg "-s ${EMBED_STRING_VIEW_NAMESPACE}")
endif()
CMake: Query Python interpreter with `find_package` This lets us fail early at configure time if a suitable Python 3 interpreter is not present, instead of delaying the error until Ninja attempts to run `embed_as_string_view.py` to generate a header in the middle of the build. Refs #21791
2023-11-05 09:52:27 +00:00
find_package(Python3 REQUIRED COMPONENTS Interpreter)
Meta: Make `embed_as_string_view.py` usable by CMake builds :^)
2023-08-23 19:38:28 +00:00
add_custom_command(
OUTPUT "${output}"
Meta: Make embed_as_string_view.py produce Strings instead This is only used for CSS style sheets. One case wants it as a String, and the others don't care, but will in future also want to have the source as a String.
2024-08-22 11:42:12 +00:00
COMMAND "${Python3_EXECUTABLE}" "${SerenityOS_SOURCE_DIR}/Meta/embed_as_string.py" "${source_file}" -o "${output}.tmp" -n "${source_variable_name}" ${namespace_arg}
Meta: Make `embed_as_string_view.py` usable by CMake builds :^)
2023-08-23 19:38:28 +00:00
COMMAND "${CMAKE_COMMAND}" -E copy_if_different "${output}.tmp" "${output}"
COMMAND "${CMAKE_COMMAND}" -E remove "${output}.tmp"
VERBATIM
Meta: Make embed_as_string_view.py produce Strings instead This is only used for CSS style sheets. One case wants it as a String, and the others don't care, but will in future also want to have the source as a String.
2024-08-22 11:42:12 +00:00
DEPENDS "${SerenityOS_SOURCE_DIR}/Meta/embed_as_string.py"
Meta: Make `embed_as_string_view.py` usable by CMake builds :^)
2023-08-23 19:38:28 +00:00
MAIN_DEPENDENCY "${source_file}"
)
add_custom_target("generate_${name}" DEPENDS "${output}")
add_dependencies(all_generated "generate_${name}")
endfunction()
Meta: Add a script and CMake function to generate a clang module map In theory the clang module map should not have absolute paths for the headers. Other Swift projects seem to use the -ivfsoverlay feature of clang to work around this, but it seems difficult to get to work.
2024-08-06 02:45:00 +00:00
function(generate_clang_module_map target_name)
Meta+LibGfx: Exclude Metal and Vulkan headers from Clang module map These headers are platform-specific, and shouldn't need to be used by Swift code anyway.
2024-11-14 23:05:08 +00:00
cmake_parse_arguments(PARSE_ARGV 1 MODULE_MAP "" "DIRECTORY" "GENERATED_FILES;EXCLUDE_FILES")
Meta: Add a script and CMake function to generate a clang module map In theory the clang module map should not have absolute paths for the headers. Other Swift projects seem to use the -ivfsoverlay feature of clang to work around this, but it seems difficult to get to work.
2024-08-06 02:45:00 +00:00
if (NOT MODULE_MAP_DIRECTORY)
set(MODULE_MAP_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}")
endif()
Meta+Libraries+AK: Append Cxx to imported library module names in swift At the same time, simplify CMakeLists magic for libraries that want to include Swift code in the library. The Lib-less name of the library is now always the module name for the library with any Swift additions, extensions, etc. All vfs overlays now live in a common location to make finding them easier from CMake functions. A new pattern is needed for the Lib-less modules to re-export their Cxx counterparts.
2024-08-27 01:04:05 +00:00
string(REPLACE "Lib" "" module_name ${target_name})
set(module_name "${module_name}Cxx")
Meta: Add a script and CMake function to generate a clang module map In theory the clang module map should not have absolute paths for the headers. Other Swift projects seem to use the -ivfsoverlay feature of clang to work around this, but it seems difficult to get to work.
2024-08-06 02:45:00 +00:00
set(module_map_file "${CMAKE_CURRENT_BINARY_DIR}/module/module.modulemap")
Meta+Libraries+AK: Append Cxx to imported library module names in swift At the same time, simplify CMakeLists magic for libraries that want to include Swift code in the library. The Lib-less name of the library is now always the module name for the library with any Swift additions, extensions, etc. All vfs overlays now live in a common location to make finding them easier from CMake functions. A new pattern is needed for the Lib-less modules to re-export their Cxx counterparts.
2024-08-27 01:04:05 +00:00
set(vfs_overlay_file "${VFS_OVERLAY_DIRECTORY}/${target_name}_vfs_overlay.yaml")
Meta: Add a script and CMake function to generate a clang module map In theory the clang module map should not have absolute paths for the headers. Other Swift projects seem to use the -ivfsoverlay feature of clang to work around this, but it seems difficult to get to work.
2024-08-06 02:45:00 +00:00
find_package(Python3 REQUIRED COMPONENTS Interpreter)
# FIXME: Make this depend on the public headers of the target
add_custom_command(
OUTPUT "${module_map_file}"
Meta+Libraries+AK: Append Cxx to imported library module names in swift At the same time, simplify CMakeLists magic for libraries that want to include Swift code in the library. The Lib-less name of the library is now always the module name for the library with any Swift additions, extensions, etc. All vfs overlays now live in a common location to make finding them easier from CMake functions. A new pattern is needed for the Lib-less modules to re-export their Cxx counterparts.
2024-08-27 01:04:05 +00:00
COMMAND "${Python3_EXECUTABLE}" "${SerenityOS_SOURCE_DIR}/Meta/generate_clang_module_map.py"
"${MODULE_MAP_DIRECTORY}"
--module-name "${module_name}"
--module-map "${module_map_file}"
--vfs-map ${vfs_overlay_file}
Meta+LibGfx: Exclude Metal and Vulkan headers from Clang module map These headers are platform-specific, and shouldn't need to be used by Swift code anyway.
2024-11-14 23:05:08 +00:00
--exclude-files ${MODULE_MAP_EXCLUDE_FILES}
--generated-files ${MODULE_MAP_GENERATED_FILES}
Meta: Add a script and CMake function to generate a clang module map In theory the clang module map should not have absolute paths for the headers. Other Swift projects seem to use the -ivfsoverlay feature of clang to work around this, but it seems difficult to get to work.
2024-08-06 02:45:00 +00:00
VERBATIM
DEPENDS "${SerenityOS_SOURCE_DIR}/Meta/generate_clang_module_map.py"
)
add_custom_target("generate_${target_name}_module_map" DEPENDS "${module_map_file}")
add_dependencies(all_generated "generate_${target_name}_module_map")
add_dependencies("${target_name}" "generate_${target_name}_module_map")
target_compile_options(${target_name} PUBLIC "SHELL:$<$<COMPILE_LANGUAGE:Swift>:-Xcc -ivfsoverlay${vfs_overlay_file}>")
endfunction()
Meta: Make `embed_as_string_view.py` usable by CMake builds :^)
2023-08-23 19:38:28 +00:00
Meta: Move code generator helpers to their own CMake helper file compile_gml, compile_ipc, and generate_state_machine all use host tools to generate sources for the target build. As part of trying to organize host tools into a common area, let's move these helper rules to a common file that we can add other host tools to later. And, keep the host tool helpers separate from the CMake target helpers for apps and libraries.
2021-08-07 23:37:09 +00:00
function(compile_ipc source output)
CMake: Don't mess with absolute compile_ipc() source paths If given an absolute path, compile_ipc() should just use it verbatim instead of trying to be helpful.
2022-10-06 09:23:53 +00:00
if (NOT IS_ABSOLUTE ${source})
set(source ${CMAKE_CURRENT_SOURCE_DIR}/${source})
endif()
Meta: Move code generator helpers to their own CMake helper file compile_gml, compile_ipc, and generate_state_machine all use host tools to generate sources for the target build. As part of trying to organize host tools into a common area, let's move these helper rules to a common file that we can add other host tools to later. And, keep the host tool helpers separate from the CMake target helpers for apps and libraries.
2021-08-07 23:37:09 +00:00
add_custom_command(
OUTPUT ${output}
IPCCompiler: Add option to pass output file path Instead of requiring the caller to redirect stdout, let's be nice citizens and add an option for the output file.
2023-04-24 09:00:34 +00:00
COMMAND $<TARGET_FILE:Lagom::IPCCompiler> ${source} -o ${output}.tmp
Meta: Move code generator helpers to their own CMake helper file compile_gml, compile_ipc, and generate_state_machine all use host tools to generate sources for the target build. As part of trying to organize host tools into a common area, let's move these helper rules to a common file that we can add other host tools to later. And, keep the host tool helpers separate from the CMake target helpers for apps and libraries.
2021-08-07 23:37:09 +00:00
COMMAND "${CMAKE_COMMAND}" -E copy_if_different ${output}.tmp ${output}
COMMAND "${CMAKE_COMMAND}" -E remove ${output}.tmp
VERBATIM
Meta: Use Lagom:: namespaced names for code generators This will be required when we switch to a SuperBuild that has Lagom as a configure time dependency, but is a distinct enough change to be separate.
2021-09-07 06:54:27 +00:00
DEPENDS Lagom::IPCCompiler
Meta: Move code generator helpers to their own CMake helper file compile_gml, compile_ipc, and generate_state_machine all use host tools to generate sources for the target build. As part of trying to organize host tools into a common area, let's move these helper rules to a common file that we can add other host tools to later. And, keep the host tool helpers separate from the CMake target helpers for apps and libraries.
2021-08-07 23:37:09 +00:00
MAIN_DEPENDENCY ${source}
)
get_filename_component(output_name ${output} NAME)
add_custom_target(generate_${output_name} DEPENDS ${output})
CMake: Add custom target to build only the generated sources This is needed so all headers and files exist on disk, so that the sonar cloud analyzer can find them when executing the compilation commands contained in compile_commands.json, without actually building. Co-authored-by: Andrew Kaster <akaster@serenityos.org>
2021-08-30 02:27:50 +00:00
add_dependencies(all_generated generate_${output_name})
CMake: Install generated IPC headers under /usr/include in compile_ipc() Generated IPC headers are now installed under /usr/include in the system's filesystem image.
2022-03-19 10:31:59 +00:00
CMake: Resolve FIXMEs related to CMake < 3.20 We already have required this version for quite a while for Lagom, Ladybird and Serenity. Now that we require it in all of our CMakeLists, let's scrub for better ways of writing things.
2024-04-25 17:30:44 +00:00
cmake_path(RELATIVE_PATH CMAKE_CURRENT_SOURCE_DIR BASE_DIRECTORY ${SerenityOS_SOURCE_DIR} OUTPUT_VARIABLE current_source_dir_relative)
Meta: Guard everything that installs headers with an option
2024-07-20 17:03:24 +00:00
if (ENABLE_INSTALL_HEADERS)
install(FILES ${CMAKE_CURRENT_BINARY_DIR}/${output} DESTINATION "${CMAKE_INSTALL_INCLUDEDIR}/${current_source_dir_relative}" OPTIONAL)
endif()
Meta: Move code generator helpers to their own CMake helper file compile_gml, compile_ipc, and generate_state_machine all use host tools to generate sources for the target build. As part of trying to organize host tools into a common area, let's move these helper rules to a common file that we can add other host tools to later. And, keep the host tool helpers separate from the CMake target helpers for apps and libraries.
2021-08-07 23:37:09 +00:00
endfunction()
Reference in a new issue Copy permalink