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/UI/cmake/InstallRules.cmake

112 lines
3.2 KiB
CMake
Raw Permalink Normal View History

Ladybird/CMake: Install resources and Lagom libraries alongside ladybird This setup should allow the package maintainers who are looking to distribute ladybird on their distributions to use CMake to install ladybird using cmake install rules rather than having to write their own
2022-09-16 10:08:24 +00:00
include(CMakePackageConfigHelpers)
include(GNUInstallDirs)
Ladybird: Remove $SERENITY_SOURCE_DIR from resource root candidates Now we will only load resources from $build/share/Lagom. On macOS, we load from the bundle directory Contents/Resources instead. This simplifies the commands and environment variables needed to execute Ladybird from the build directory, and makes our install setup less awkward for distributions and packagers.
2024-02-23 20:40:16 +00:00
set(package Ladybird)
Ladybird/CMake: Install resources and Lagom libraries alongside ladybird This setup should allow the package maintainers who are looking to distribute ladybird on their distributions to use CMake to install ladybird using cmake install rules rather than having to write their own
2022-09-16 10:08:24 +00:00
Ladybird: Always place helper processes in bundle directory on macOS Don't put them in bin/ and then copy them to the bundle dir later, as this means that they only get updated in the bundle directory if the Ladybird binary itself needs updated. Which is not a fun workflow if you are working on WPT and want to hack on the WebDriver binary.
2024-02-21 23:16:15 +00:00
set(ladybird_applications ladybird ${ladybird_helper_processes})
Ladybird: Clean up install rules for executables Use a list of executables to make sure that we don't miss any of the applications used by Ladybird and its friends like WebDriver, and make sure to install include all executables and their runtime dependencies.
2023-02-02 10:22:20 +00:00
Ladybird: Make Android build work again, and tidy up files We don't need the extra gradle files in our sources, the Qt CMake integration will generate suitable ones for us. Make sure that assets is always a folder, so that we can get the proper layout for the ladybird-assets.tar.gz and CMake doesn't create a gzip file with the name "assets". Fix up the AndroidPlatform file and make sure it's linked into all the applications that need it. Also make sure to copy all the application shared libraries into the ladybird APK so that when we make them into proper Services, the libs are already there.
2023-07-19 16:27:16 +00:00
set(app_install_targets ${ladybird_applications})
Ladybird: Move helper processes to CMAKE_INSTALL_LIBEXECDIR It aligns better with the Filesystem Heirarchy Standard[1] to put our program-specific helper programs that are not intended to be executed by the user of the application in $prefix/libexec or in whatever the packager sets as the CMake equivalent. Namely, on Debian systems this should be /usr/lib/Ladybird or similar. [1] https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#usrlibexec
2024-02-24 00:02:17 +00:00
install(TARGETS ladybird
Ladybird/CMake: Install resources and Lagom libraries alongside ladybird This setup should allow the package maintainers who are looking to distribute ladybird on their distributions to use CMake to install ladybird using cmake install rules rather than having to write their own
2022-09-16 10:08:24 +00:00
EXPORT ladybirdTargets
RUNTIME
COMPONENT ladybird_Runtime
DESTINATION ${CMAKE_INSTALL_BINDIR}
BUNDLE
COMPONENT ladybird_Runtime
DESTINATION bundle
LIBRARY
COMPONENT ladybird_Runtime
NAMELINK_COMPONENT ladybird_Development
DESTINATION ${CMAKE_INSTALL_LIBDIR}
CMake: Make sure to install generated sources and header files We weren't installing a lot of generated sources for the top level Lagom build or for LibWeb, making it impossible to use LibWeb from a find_package. ...And also Kernel/API/KeyCode.h, which is included by no less than 8 different files in Userland/Libraries. We also weren't installing any Ladybird header files.
2023-08-08 04:14:22 +00:00
FILE_SET browser
DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}
FILE_SET ladybird
DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}
Ladybird/CMake: Install resources and Lagom libraries alongside ladybird This setup should allow the package maintainers who are looking to distribute ladybird on their distributions to use CMake to install ladybird using cmake install rules rather than having to write their own
2022-09-16 10:08:24 +00:00
)
Ladybird: Move helper processes to CMAKE_INSTALL_LIBEXECDIR It aligns better with the Filesystem Heirarchy Standard[1] to put our program-specific helper programs that are not intended to be executed by the user of the application in $prefix/libexec or in whatever the packager sets as the CMake equivalent. Namely, on Debian systems this should be /usr/lib/Ladybird or similar. [1] https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#usrlibexec
2024-02-24 00:02:17 +00:00
install(TARGETS ${ladybird_helper_processes}
EXPORT ladybirdTargets
RUNTIME
COMPONENT ladybird_Runtime
DESTINATION ${CMAKE_INSTALL_LIBEXECDIR}
)
Everywhere: Replace SERENITY_SOURCE_DIR with LADYBIRD_SOURCE_DIR In order to have checkouts of both SerenityOS and Ladybird, we need to use a different environment variable for Ladybird.
2024-06-03 12:40:19 +00:00
include("${LADYBIRD_SOURCE_DIR}/Meta/Lagom/get_linked_lagom_libraries.cmake")
Ladybird: Clean up install rules for executables Use a list of executables to make sure that we don't miss any of the applications used by Ladybird and its friends like WebDriver, and make sure to install include all executables and their runtime dependencies.
2023-02-02 10:22:20 +00:00
foreach (application IN LISTS ladybird_applications)
get_linked_lagom_libraries("${application}" "${application}_lagom_libraries")
list(APPEND all_required_lagom_libraries "${${application}_lagom_libraries}")
endforeach()
Ladybird: Ensure that installed ladybird can launch WebContent process Always call platform_init after there's a QApplication, because in the installed configuration that's how we find the resources. Try QCoreApplication::applicationDirPath() after looking in ./WebContent for the WebContent process. In an installed configuration, ladybird and WebContent will both be in $PREFIX/bin. Add install rules for WebContent and its linked libraries, for if they ever differ from ladybird's.
2022-10-07 23:08:29 +00:00
list(REMOVE_DUPLICATES all_required_lagom_libraries)
Ladybird/CMake: Install resources and Lagom libraries alongside ladybird This setup should allow the package maintainers who are looking to distribute ladybird on their distributions to use CMake to install ladybird using cmake install rules rather than having to write their own
2022-09-16 10:08:24 +00:00
Ladybird: Add new template Kotlin Android application without Qt This template app from Android Studio should hopefully be more fun to work on than the Qt wrapped application we were using before. :^) It currently builds the native code using gradle rules, and has a stub WebViewImplementationNative class that will wrap a c++ class of the same name that inhertis from WebView::ViewImplementation. Spawning helper processes and creating proper views in Kotlin is next on the list.
2023-09-02 15:30:21 +00:00
# Remove ladybird shlib if it exists
list(REMOVE_ITEM all_required_lagom_libraries ladybird)
Meta: Add new top-level CMakeLists
2024-06-03 19:24:20 +00:00
if (APPLE)
# Fixup the app bundle and copy:
# - Libraries from lib/ to Ladybird.app/Contents/lib
# Remove the symlink we created at build time for the lib directory first
install(CODE "
file(REMOVE \${CMAKE_INSTALL_PREFIX}/bundle/Ladybird.app/Contents/lib)
set(lib_dir \${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_LIBDIR})
if (IS_ABSOLUTE ${CMAKE_INSTALL_LIBDIR})
set(lib_dir ${CMAKE_INSTALL_LIBDIR})
endif()
set(contents_dir \${CMAKE_INSTALL_PREFIX}/bundle/Ladybird.app/Contents)
file(COPY \${lib_dir} DESTINATION \${contents_dir})
"
COMPONENT ladybird_Runtime)
endif()
Ladybird: Ensure that installed ladybird can launch WebContent process Always call platform_init after there's a QApplication, because in the installed configuration that's how we find the resources. Try QCoreApplication::applicationDirPath() after looking in ./WebContent for the WebContent process. In an installed configuration, ladybird and WebContent will both be in $PREFIX/bin. Add install rules for WebContent and its linked libraries, for if they ever differ from ladybird's.
2022-10-07 23:08:29 +00:00
install(TARGETS ${all_required_lagom_libraries}
Ladybird/CMake: Install resources and Lagom libraries alongside ladybird This setup should allow the package maintainers who are looking to distribute ladybird on their distributions to use CMake to install ladybird using cmake install rules rather than having to write their own
2022-09-16 10:08:24 +00:00
EXPORT ladybirdTargets
COMPONENT ladybird_Runtime
LIBRARY
COMPONENT ladybird_Runtime
NAMELINK_COMPONENT ladybird_Development
DESTINATION ${CMAKE_INSTALL_LIBDIR}
Ladybird: Install headers for WebContent when used externally
2023-08-12 01:38:31 +00:00
FILE_SET server
DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}
FILE_SET ladybird
DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}
Ladybird/CMake: Install resources and Lagom libraries alongside ladybird This setup should allow the package maintainers who are looking to distribute ladybird on their distributions to use CMake to install ladybird using cmake install rules rather than having to write their own
2022-09-16 10:08:24 +00:00
)
write_basic_package_version_file(
"${package}ConfigVersion.cmake"
COMPATIBILITY SameMajorVersion
)
# Allow package maintainers to freely override the path for the configs
set(
ladybird_INSTALL_CMAKEDIR "${CMAKE_INSTALL_DATADIR}/${package}"
CACHE PATH "CMake package config location relative to the install prefix"
)
mark_as_advanced(ladybird_INSTALL_CMAKEDIR)
install(
FILES cmake/LadybirdInstallConfig.cmake
DESTINATION "${ladybird_INSTALL_CMAKEDIR}"
RENAME "${package}Config.cmake"
COMPONENT ladybird_Development
)
install(
Meta: Add new top-level CMakeLists
2024-06-03 19:24:20 +00:00
FILES "${CMAKE_CURRENT_BINARY_DIR}/${package}ConfigVersion.cmake"
Ladybird/CMake: Install resources and Lagom libraries alongside ladybird This setup should allow the package maintainers who are looking to distribute ladybird on their distributions to use CMake to install ladybird using cmake install rules rather than having to write their own
2022-09-16 10:08:24 +00:00
DESTINATION "${ladybird_INSTALL_CMAKEDIR}"
COMPONENT ladybird_Development
)
install(
EXPORT ladybirdTargets
NAMESPACE ladybird::
DESTINATION "${ladybird_INSTALL_CMAKEDIR}"
COMPONENT ladybird_Development
)
Ladybird: Remove $SERENITY_SOURCE_DIR from resource root candidates Now we will only load resources from $build/share/Lagom. On macOS, we load from the bundle directory Contents/Resources instead. This simplifies the commands and environment variables needed to execute Ladybird from the build directory, and makes our install setup less awkward for distributions and packagers.
2024-02-23 20:40:16 +00:00
if (NOT APPLE)
# On macOS the resources are handled via the MACOSX_PACKAGE_LOCATION property on each resource file
install_ladybird_resources("${CMAKE_INSTALL_DATADIR}/Lagom" ladybird_Runtime)
endif()
Reference in a new issue Copy permalink