t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 8330dc8..e69ceb9 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 14)
-set(CMake_VERSION_PATCH 20190214)
+set(CMake_VER
Sounds good. The FAQ has a question "Is there a way to skip checking
of dependent libraries when compiling?" - perhaps you can add one just
before that, something like "Is there a way to reduce the amount of
linking when building a large project?".or similar.
Thanks again,
itay
On Thu, Feb 14,
I agree that we should document this property better.
I recommend looking at the CMake wiki (
https://gitlab.kitware.com/cmake/community/wikis/home ) and thinking
maybe adding a new recipe for `optimizing redundant linking`.
On Thu, Feb 14, 2019 at 3:11 PM Itay Chamiel wrote:
>
> On Thu, Feb 14,
On Thu, Feb 14, 2019 at 8:08 PM Robert Maynard
wrote:
> By default CMake wants to get a correct build 100% of the time. There
> is nothing to stop people from having functions defined in a .cxx file
> with no corresponding header, and using manual forward deceleration is
> used in a consuming
I might be getting close and the root cause might be related to a
conceptual question that I was saving for later: how transitive
linking should be done!
Returning to the build design: pytorch is compile if not installed in
the system, lib datareader_core consumes pytorch and standalone_gtests
I guess what I would ultimately like to achieve would be a
"pre-cmake-configuration" step that just initializes the package registry
with the location of each project's build tree and copies the
"project-config.cmake" files into each projects build-tree. This would
allow it to be found during
Le jeu. 14 févr. 2019 à 18:57, Timothy Wrona a
écrit :
> The problem is it is very likely that there are some circular dependencies
> in the build tree -- which is why it was broken up to generation of all,
> then build all, then link all in the first place.
>
Yes, wrong solution to a real
> I wonder why this isn't the default behavior
By default CMake wants to get a correct build 100% of the time. There
is nothing to stop people from having functions defined in a .cxx file
with no corresponding header, and using manual forward deceleration is
used in a consuming
The problem is it is very likely that there are some circular dependencies
in the build tree -- which is why it was broken up to generation of all,
then build all, then link all in the first place.
With circular dependencies there's no real way to sort these dependencies
out without just running
Le jeu. 14 févr. 2019 à 18:22, Timothy Wrona a
écrit :
> I have a collection of interdependent CMake projects (lots of legacy code)
> that I want to convert to using CMake targets for linking. The code is
> built in such a way that all projects run cmake generation, then all
> projects build,
I have a collection of interdependent CMake projects (lots of legacy code)
that I want to convert to using CMake targets for linking. The code is
built in such a way that all projects run cmake generation, then all
projects build, then all projects link.
I would like to export a CMake target from
On Thu, Feb 14, 2019 at 12:39 PM Craig Scott wrote:
> I think you might be looking for the LINK_DEPENDS_NO_SHARED target property
> (or more likely its associated CMAKE_LINK_DEPENDS_NO_SHARED variable).
After my previous response I experimented a little more, and I got it
to work. My mistake
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 8c4de819449bbb1710b1cc2440357757e5cb757c (commit)
via
Hi,
I'm having an issue with CUDA (sadly the old-style FindCUDA, not the new
native support of CUDA).
The following CMake file reproduces the issue easily on Windows with any
Visual Studio Generator (14 2015 Win64 being the one I use).
Adding the file generated by cuda_compile_ptx to any target
Thanks, Thompson, I will look into BUILD_RPATH and possibly INSTALL_RPATH.
I just learned about `export LD_DEBUG=files` to debug linking issues
on linux. It provides more detail on the ldd output, as below:
18843: file=libc10.so [0]; needed by
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, release has been updated
via 2f51f281a8c9684c25cf97499a4382e1b5ae68b9 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via e3353a0175fb27bc2967c3df78b8be1c0615b21d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 0069825f50c83b8144374150dd682d48c84f6874 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 50ba2f019baa3e5487a975cb72059f1fc178f9d0 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 49a53cac87fe3a303a2794ccdd7c1b5cecd2d016 (commit)
via
Thiago,
I haven’t see the double entry pattern that you mention below. However, you
might want to tell CMake to embed a BUILD_RPATH in your libraries. This should
get around the issue of manually setting LD_LIBRARY_PATH.
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" keyword in a special way and know what to do
> with it?
> 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" keyword in a special way and know what to do with it?
it’s from a Sphinx module that you can find the in the CMake sources
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
On 2/14/19 12:38 PM, Craig Scott wrote:
I think you might be looking for the LINK_DEPENDS_NO_SHARED target
property (or more likely its associated CMAKE_LINK_DEPENDS_NO_SHARED variable).
On Thu, Feb 14, 2019 at 9:24 PM Itay Chamiel wrote:
> Hi,
>
> I've asked this question on Stack Overflow almost a year ago with no
> useful responses (with the same topic if you wish to search for it), so I'm
> trying my luck here.
>
> I work on a large commercial C++ project comprised of a
Hi,
I've asked this question on Stack Overflow almost a year ago with no useful
responses (with the same topic if you wish to search for it), so I'm trying
my luck here.
I work on a large commercial C++ project comprised of a couple dozen
dynamically linked shared libraries, each of which has
Hello,
On 14.02.19 04:39, Timothy Wrona wrote:
Okay so I dug a little deeper into this and it definitely looks like
sphinx is the correct tool to use, but I still have one problem.
I would like sphinx to be able to extract ".rst" formatted comments
directly out of my cmake source files to
28 matches
Mail list logo
