Age | Commit message (Collapse) | Author |
|
Also simplify CMake-based dependency projects, the parameters that
have been set for the viewer seem to have been implied all this time
for the subprojects.
|
|
Its own CPACK_RPM_PACKAGE_REQUIRES will catch up soon.
|
|
instead of 0.
|
|
|
|
file(COPY) seems to already include making the necessary directories.
|
|
file(DOWNLOAD) replacing execute_process(COMMAND curl),
file(ARCHIVE_EXTRACT) replacing execute_process(COMMAND tar xf),
file(MAKE_DIRECTORY) replacing execute_process(COMMAND mkdir -p),
file(COPY) replacing execute_process(COMMAND cp),
file(RENAME) replacing execute_process(COMMAND mv),
try_compile replacing execute_process(COMMAND cmake/make),
LIBS_PREBUILT_DIR replacing AUTOBUILD_INSTALL_DIR,
0 replacing ${${_binary}_installed} where appropriate,
no FMOD reinstallation when it's already installed,
and archives & unarchived source/build directories are in CMake
root binary directory, instead of /tmp.
SHOW_PROGRESS is on for downloading Dullahan from the Megapahit
website cause it can be slow.
|
|
|
|
also fix ${_binary} to its intended fmodstudio name.
|
|
by making sure we *write* the _installed files (containing the value 0).
|
|
by moving them to Variables.cmake so they can be reused throughout
all CMake files.
|
|
and Ubuntu. find_package(meshoptimizer) didn't imply its
target_link_libraries.
|
|
It is decided that on x86-64, it's compiled too instead of using
LL's (old) prebuilt libmeshoptimizer.a.
|
|
on macOS and Fedora.
|
|
|
|
Co-authored-by: AiraYumi <aira.youme@airanyumi.net>
|
|
When cross-compiling, the host's /usr/local/include would be unsafely
included before. The problem with this was that it leaked other host
library headers unexpectedly, like Boost. The target compilation caught
some function from the host headers which of a newer version, and then
when trying to link to the target libraries, the function wasn't
available yet in the older version.
|
|
The Meshoptimizer CMake files don't seem to be working right. On more
than one platform, they always conclude the package as not found.
Nevertheless, the library is typically installed in standard paths, that
no special paths need to be included for Meshoptimizer to be found.
Except on macOS (so far), as existing package managers don't have that
package yet, hence the /usr/local/include addition. It's a safe path to
include anyway on other un*x platforms.
|
|
|