to
take a few days and really try to learn how to use the Conan package
manager in depth. If it works out well I will try to summarize and report
some of my findings. :)
Thanks,
Tim
On Sat, Feb 23, 2019 at 2:32 AM Craig Scott wrote:
>
>
> On Sat, Feb 23, 2019 at 4:14 PM Timothy Wrona
> w
of FetchContent :)
Thanks,
Tim
On Wed, Feb 20, 2019 at 8:22 AM Craig Scott wrote:
>
>
> On Wed, Feb 20, 2019 at 3:36 PM Timothy Wrona
> wrote:
>
>> (Included cmake-developers list as well in case this may have just been
>> something that should work that was overlooked w
I am having an issue with using FetchContent to grab two subprojects that
both contain a "doxygen" target to build the documentation.
Both of these subprojects need to be able to be built independently and
when built on their own they compile fine (along with their documentation),
but when I pull
e sub-projects and I will have all of the
source code available. I am hoping if I do this any changes I make to the
sub-projects can easily be committed and pushed back to their own
independent repositories.
On Tue, Feb 19, 2019 at 10:33 AM Timothy Wrona
wrote:
> Hi Craig,
>
> Thank you
better fit for this scenario.
- Maybe when the sub-project libraries reach a mature and stable
release they should be packaged into Conan and fetched in the
main project
from Conan at that point?
Let me know what you think! :)
On Tue, Feb 19, 2019 at 5:56 AM Craig Scott wrote:
>
&
I have been working on a new C++ project and I am trying to decide whether
I should use CMake as my package management system or if I should use a
dedicated package management tool such as Conan.
For more information on Conan see: https://conan.io/
I am trying to understand the main difference
That's what I was looking for! Thanks!!!
On Thu, Feb 14, 2019 at 9:04 AM wrote:
>
>
> > Am 14.02.2019 um 14:53 schrieb Timothy Wrona :
> >
> > How does Sphinx know to go parse that ".cmake" file? Does Sphinx
> recognize the „cmake-module" ke
Hi Gregor,
It looks like there's still a little bit of magic here. All those
"Help/.rst" files just have a single line in them that says:
.. cmake-module:: ../../Modules/.cmake
How does Sphinx know to go parse that ".cmake" file? Does Sphinx recognize
the "cmake-module" keyword in a special way
ese comments without
writing my own tool to do it? I mean it wouldn't be hard to script, but if
there is a standard way I would prefer to use what everyone else uses
rather than reinvent the wheel.
Thanks,
Tim
On Wed, Feb 13, 2019, 8:59 AM Timothy Wrona I am going to quote your response in an answer
I am going to quote your response in an answer on my stack overflow
question so others may find this information too.
On Wed, Feb 13, 2019 at 8:57 AM Timothy Wrona wrote:
> Thanks for the info and the links! I will start looking into it. :)
>
> On Wed, Feb 13, 2019 at 7:50 AM Torsten
Thanks for the info and the links! I will start looking into it. :)
On Wed, Feb 13, 2019 at 7:50 AM Torsten Robitzki
wrote:
>
>
> > Am 13.02.2019 um 13:42 schrieb Brad King via cmake-developers <
> cmake-developers@cmake.org>:
> >
> > The online docs, like those at
Note: I have additionally posted this question to stack overflow so if you
would like to answer there rather than email it may help a larger audience:
https://stackoverflow.com/questions/54660549/what-is-the-proper-way-to-document-a-cmake-module
On Tue, Feb 12, 2019 at 6:37 PM Timothy Wrona
A quick Google search (...actually many rather extensive Google searches)
have not been able to explain how to properly document a CMake module.
What I'm looking for is a way to document custom CMake modules so that they
work with the "cmake --help-module " command. Is there any
standard way of
I saw this email come through the cmake users mailing list but feel it is
more fitting for it to go to cmake-developers so I'm forwarding it here.
It is a pretty long rant, but I think his idea to add a keyword to the
"target_link_libraries()" command that would only look for cmake targets is
a
message like "all outputs
> up to date" and skips over it. So any associated custom commands with the
> target are never run.
> Adding a "command" that is even an echo, like add_custom_target(testcmake1
> COMMAND ${CMAKE_COMMAND} -E echo "Running testcmake1 step 1&quo
I have been following the examples in the "CMake Cookbook" by Radovan Bast
and Roberto Di Remigio and came across one example that doesn't appear to
work right on Windows.
The source code for these example can be found here:
https://github.com/dev-cafe/cmake-cookbook
Chapter-06/Recipe-07 is
, 2019 at 3:15 PM Timothy Wrona wrote:
> Thank you! I didn't know it would make a registry entry, that was the
> missing link!
>
> On Tue, Feb 5, 2019 at 2:46 PM Brad King wrote:
>
>> On 2/5/19 2:37 PM, Timothy Wrona wrote:
>> > Can anyone explain to me how "find
Thank you! I didn't know it would make a registry entry, that was the
missing link!
On Tue, Feb 5, 2019 at 2:46 PM Brad King wrote:
> On 2/5/19 2:37 PM, Timothy Wrona wrote:
> > Can anyone explain to me how "find_package" is able to find the Eigen
> libraries
> &g
I am working my way through the "CMake Cookbook" by Radovan Bast and
Roberto Di Remigio and got to an example that required the Eigen C++
libraries. (chapter-02/recipe-06)
I downloaded the ".zip" for the Eigen libraries and unzipped it to an
arbitrary location. Then I ran CMake on it (but I did
I recently started using a new package manager for C++ called "Conan" and
I'm finding it is solves many of the dependency issues that plague all of
my previous C++/CMake projects.
Conan is an up-and-coming tool, but it seems to be gaining quite a bit of
traction. It is designed with CMake in mind
20 matches
Mail list logo
