Already looked on google and at the CMake documentation but everything listed
does not seem to work so here is the setup.
I am using MKL and I have a home grown FindMKL since there isn’t an official
one. Inside that is the typical find_library() calls which will find the
libraries just fine.
On Wed, 2019-09-11 at 21:40 +0300, Avraham Shukron wrote:
> Hi!
>
> I'm pretty new to cmake and I came across a question which I could
> not find any information about in the official documentation or blog
> posts.
>
> When adding a target through add_library / add_executable - should
> the
On Wed, 2019-09-11 at 22:00 +0300, Avraham Shukron wrote:
>
>
> On Wed, Sep 11, 2019 at 9:49 PM Kyle Edwards m> wrote:
> > You can list them or not list them. CMake will recognize them as
> > header
> > files and ignore them (not attempt to compile them.) It's a matter
> > of
> > personal
On Mittwoch, 11. September 2019 21:22:04 CEST Kyle Edwards via CMake wrote:
> On Wed, 2019-09-11 at 22:00 +0300, Avraham Shukron wrote:
> > On Wed, Sep 11, 2019 at 9:49 PM Kyle Edwards >
> > m> wrote:
> > > You can list them or not list them. CMake will recognize them as
> > > header
> > > files
Hi!
I'm pretty new to cmake and I came across a question which I could not find
any information about in the official documentation or blog posts.
When adding a target through add_library / add_executable - should the
header files of the target also be listed?
The question also applies to
On Wed, Sep 11, 2019 at 9:49 PM Kyle Edwards
wrote:
> You can list them or not list them. CMake will recognize them as header
> files and ignore them (not attempt to compile them.) It's a matter of
> personal preference. CMake's own CMake script lists them, but there are
> plenty of projects
On Wed, 2019-09-11 at 17:33 -0400, Michael Jackson wrote:
> Already looked on google and at the CMake documentation but
> everything listed does not seem to work so here is the setup.
>
> I am using MKL and I have a home grown FindMKL since there isn’t an
> official one. Inside that is the
On 9/11/19, 5:42 PM, "Kyle Edwards" wrote:
On Wed, 2019-09-11 at 17:33 -0400, Michael Jackson wrote:
> Already looked on google and at the CMake documentation but
> everything listed does not seem to work so here is the setup.
>
> I am using MKL and I have a home grown
Hello,
I'm using CPack to create RPMs for an application. I have this working but
the CPack step is quite slow. While investigating this, I noticed that all
files in a directory I'm packaging, which contains a large number of small
files, is being listed in the spec file.
For instance, say I have
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 0d48a72..fc86b56 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,7 +1,7 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 15)
-set(CMake_VERSION_PATCH 20190911)
+set(CMake_VER
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 b5b10c8e955abb2b0f18c3e41b7892471857bcc1 (commit)
via
11 matches
Mail list logo
