-
Notifications
You must be signed in to change notification settings - Fork 9
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
Patch step error while linking library with CMake #28
Comments
In addition to this, I've noticed that the headers are not installed to the installation destination, which is usually convenient for linking. Would it be possible to add a step to your CMake along these lines:
|
Thanks @rlorigro — I'll tag @jamshed here but I'm sure he'll see it anyway. In the first case, I think we haven't tested including cuttlefish with In the second case, we don't install headers by default since (at least until this point) the primary user usecase has been to use cuttlefish as a standalone program rather than to interact with it programmatically as a library (apart from our own use in |
Nice, thanks for the quick reply. I've managed to fix the patch step error with this (admittedly hacky) solution:
It just copies the diff file into the place where it was looking for it But now I'm getting a new error relating to finding the KMC headers. Haven't been able to fix it by including the directories manually
I suspect a lot of this is a result of my brute force method for linking, so If you have any recommendations for how to make this simpler, please let me know :) |
Hi,
I'm attempting to link your library with a combination of
FetchContent
andadd_custom_target
. Everything installs great, but when I link KMC (the one built by your CMakeLists) in order to satisfy your dependencies, I get this error during the build step:and I've noticed there is a relevant line in your CMake, which might explain this strange error:
cuttlefish/CMakeLists.txt
Line 190 in 30eef21
I'm not familiar enough with CMake to understand this. Is there something I can do to work around it?
Here is my implementation:
The text was updated successfully, but these errors were encountered: