-
Notifications
You must be signed in to change notification settings - Fork 54
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
Install metadata (exported targets, etc.) is broken #50
Comments
@vikiboy: I believe you recently ran @BrendanDrewDaqri: are you running CMake with |
@crheckman: I've tried setting that flag both ways. What's a little complicated here is that I'm pulling in Calibu as a dependency ("superbuild" in cmake parlance) via ExternalPackage_Add. After poking around a bit, it seems that the way the export data is being generate is confusing. I'm hacking on a clone that we have and if I find anything useful (I have some suspicions about how to get the include paths properly expressed to CMake to make the export work the way it "should") BTW, if I should find a fix, I'm more than happy to share it but I'd like to make sure I've tested it on the right platforms before wasting your time. |
It's definitely tough keeping all of our packages in shape for supporting brew, CMake and If you're flip-flopping flags make sure you're doing them in clean build directories; I've found that CMake doesn't overwrite its own *Config.cmake files to reflect flopped flags. |
This seems to work for me (note that I've gutted out all the matlab stuff
It'll take me a little while to back-port my changes (I did a pretty build calibu libraryadd_library( calibu ${SOURCES} ) foreach(CALIBU_INCLUDE ${CALIBU_INC}) install everythinginstall(TARGETS calibu install(DIRECTORY include/calibu install(FILES ${CMAKE_CURRENT_BINARY_DIR}/include/calibu/config.h install(EXPORT calibuExports On Thu, Jul 14, 2016 at 3:31 PM, Christoffer Heckman <
|
No, there weren't any issues with other packages not finding calibu. A simple |
I just gave this a test, and it doesn't appear to support exporting from the build tree (https://cmake.org/Wiki/CMake/Tutorials/Exporting_and_Importing_Targets#Exporting_from_a_Build_Tree), which is a feature we have traditionally supported in our development environment. I would have to know a bit more about the roadblocks you've hit with our current master branch to see what exactly is breaking. As I said, the current approach (which uses a dazzlingly arcane set of commands all wrapped up in |
Specific platforms where I have problems: OS X (El Capitan, XCode 7.3.1). The generated exports capture include locations and libraries for Calibu's dependencies, but not for Calibu itself. There are also several warnings that are generated. FWIW, I find the following fragments helpful when doing install / export targets (for each exported library / "module"):
The text was updated successfully, but these errors were encountered: