Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust exported target location, remove Deps downloading #952

Closed
wants to merge 3 commits into from

Conversation

starseeker
Copy link
Contributor

This allows a find_package in BRL-CAD to locate Manifold using the manifoldConfig.cmake file, and avoids performing the dependency downloads as a consequence of the find_package call.

@starseeker
Copy link
Contributor Author

To clarify, this does not eliminate manifoldDeps.cmake from the Manifold build itself - just from the exported targets.

@@ -162,13 +162,15 @@ write_basic_package_version_file(
VERSION ${MANIFOLD_VERSION}
COMPATIBILITY SameMajorVersion
)
install(EXPORT manifoldTargets DESTINATION ${CMAKE_INSTALL_DATADIR}/manifold)
install(EXPORT manifoldTargets
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are the files being installed with this install call?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The DESTINATION is ${CMAKE_INSTALL_LIBDIR}/cmake/manifold, so lib/cmake/manifold. That seems to be where CMake is looking for these files, at least on Linux:

https://cmake.org/cmake/help/latest/command/find_package.html#search-procedure

I'm open to a better specification for where to place the files that will be better for cross-platform scenarios - the EXPORT feature is new to me, so I'm not properly conversant with best practices yet.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to try to merge this PR, or just do this as part of your larger reorganization?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm game either way - if you think there's a good chance of the larger reorg getting merged there's probably no particular need for this, but if that's problematic this would be helpful.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's see how the other does, since this isn't passing the CI anyway.

@starseeker
Copy link
Contributor Author

Closing in favor of #961

@starseeker starseeker closed this Sep 29, 2024
@starseeker starseeker deleted the export_targets branch September 29, 2024 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants