-
Notifications
You must be signed in to change notification settings - Fork 17
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
Make project compatible with FetchContent
#32
Comments
Perhaps you can clarify some details I have been having about cmake, in the Lastly, I have been focusing on getting the cmake stuff in. And was planning on getting the sub-project part done soonish, so I'll get my hands dirty again and will likely ask you some questions (here) if you don't mind? :) |
In principle one does not have to do it. Normally you set
Sure thing, feel free to make a PR and I can review and give some tips there. |
That information would be great, I have just encountered problems where the targets were found, but the |
Note that |
Might I ask what you are planning to use fdict for? |
I don't know if it's a well-known design pattern, but I'm using this to add a context object/field so it is easier to write extensions in |
There are a few issues that should be resolved to make importing
find_package
andFetchContent
equivalent:fdict
->fdict::fdict
FDICT_INSTALL
,FDICT_SHARED_LIBS
to control howfdict
is being builtfdictConfig.cmake
usingreturn(PROPAGATE)
orset(PARENT_SCOPE)
The text was updated successfully, but these errors were encountered: