James
James
In any case, if it is a header only library, it shouldnt have ``self.cpp_info.libs = ["MyLib"]`` line at all, that is only for compiled libraries. I would also strongly recommend...
Hi @kyllingstad The truth is that we have thought about this a few times, and always rejected the idea, because the recipe is not only composed by the conanfile.py, but...
Good! Moved this to the documentation, lets add there a visible warning.
> So overall I would appreciate if Conan could handle this in some better way. @chausner the thing is that I have already implemented this thing. It was a huge...
I agree, maybe having a warning is very doable and could help users enough. Wdyt @solvingj?
Hi @rconde01 Indeed, the ``self.copy`` is injected for the ``package()`` method, but will not exist in other recipe methods. We are structuring better the things that can be used in...
> another point here is that copy is available from other methods (e.g. imports) Exactly. In fact, the important point is that the copy from the ``import()`` is a different...
Yep, there is no way to declare that directly in the ``conanfile.txt`` a ``conanfile.py`` is necessary.
[feature] docs/Getting Started: Update this guide to use at least the `cmake_find_package` generator
We are already starting the work to re-write the whole docs for Conan 2.0, it is not worth to change it, because we are already in 2.0-alpha stage.
[feature] docs/Getting Started: Update this guide to use at least the `cmake_find_package` generator
> Thanks a lot for your continuous work and quick answer! I thought about to fight some spare time for contribution as my friend, being a novice C++ programmer, had...