t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index c068594..2580bd2 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 16)
-set(CMake_VERSION_PATCH 20191007)
+set(CMake_VER
To avoid repetition, please view:
https://stackoverflow.com/questions/58253100/how-to-use-lld-with-cmake-on-windows
Sent with [ProtonMail](https://protonmail.com) Secure Email.--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
In my opinion [the latest documentation of the FindThreads
module](https://cmake.org/cmake/help/latest/module/FindThreads.html)
needs some work. Specifically please deal with the following documentation
issues.
* Threads_FOUND needs documentation. And that needs to be done at the
top of the
Ctest creates a log file in ../build/Testing/Temporary with a name like
LastTest_MMDD_HHMM.
Is there a way I an add some descriptions to this name?
For example, LastTest_MMDD_HHMM_MyTestDescription.
Thanks in advance.
--
Donald [|]
A bad day in [] is better than a good day in {}.
Hi,
can you reproduce my observations ? I'm I doing something wrong or is
there indeed an issue with CMake ? Should I follow up with a bug report ?
Thanks,
On 2019-10-04 2:20 p.m., stefan wrote:
On 2019-10-03 5:24 p.m., Kyle Edwards wrote:
On Thu, 2019-10-03 at 17:08 -0400, stefan wrote:
> I think that the word install is used consistently between GNU autotools and
> CMake:
Right, looks like it comes from the "good old times" when on Linux computers
software was "installed" by downloading, then doing a "make" and a "make
install" in order to get it running, while nowadays
On Mon, Oct 7, 2019, at 11:25 AM, Eric Noulard wrote:
>
>
> Le lun. 7 oct. 2019 à 16:49, Cornelis Bockemühl a
> écrit :
>> Thanks to both you and J Decker: I would say that this is still the part
>> that I understood! So basically the word "install" in cmake language could
>> be replaced by
>Le lun. 7 oct. 2019 à 16:49, Cornelis Bockemühl a
>écrit :
>
>> Thanks to both you and J Decker: I would say that this is still the part
>> that I understood! So basically the word "install" in cmake language could
>> be replaced by "copy" more or less in common human language - right?
>
>Nope
Le lun. 7 oct. 2019 à 16:49, Cornelis Bockemühl a
écrit :
> Thanks to both you and J Decker: I would say that this is still the part
> that I understood! So basically the word "install" in cmake language could
> be replaced by "copy" more or less in common human language - right?
>
Nope I
A note - INSTALL( FILES ) is only good for data files, if you have scripts
that have executable permissions using INSTALL( PROGRAMS ) will get execute
flag set too.
On Mon, Oct 7, 2019 at 7:49 AM Cornelis Bockemühl
wrote:
> Thanks to both you and J Decker: I would say that this is still the
Hi Eric,
Thanks for your prompt reply.
I have been able to follow your steps up until the item, so thanks!
COMMAND ${CMAKE_C_COMPILER} $
--symbol $.crc32 $
I ran into two challenges:
- The argument '$.crc32' should be the
actual content of the file, and not the file itself, i.e. the
ber components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 16)
-set(CMake_VERSION_PATCH 0)
-set(CMake_VERSION_RC 0)
+set(CMake_VERSION_PATCH 20191007)
+#set(CMake_VERSION_RC 0)
set(CMake_VERSION_IS_DIRTY 0)
# Start with the full version number used in tags. It has no dev info.
https:
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 ead89868ba09bb331ae31c116f1cec4a44713b3b (commit)
via
Thanks to both you and J Decker: I would say that this is still the part that I
understood! So basically the word "install" in cmake language could be replaced
by "copy" more or less in common human language - right?
But then, if it is about "installing" a "target", which is libraries in my
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 b734a04164dcd4eb37246b4b0d52e22996d8ef43 (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 947b02e2e0d0a7d9c8155b50ac79b56818f4b6f6 (commit)
via
I'll try some answer.
In order to illustrate my words have a look at this figure:
https://raw.githubusercontent.com/dev-cafe/cmake-cookbook/master/figures/cmake-times/cmake-times.jpg
1) When cmake "runs" (both cmake and generation times) you get your build
tree configured and populated
2) At
Install steps are done with `cmake --build . --target install` (or
--target INSTALL on some generators)
It's done after the build is complete, if the build step fails, it will not
install. (Install depends on build automatically)
The install steps can also be used by --target package - which
Le lun. 7 oct. 2019 à 14:41, Vincent van Beveren
a écrit :
> Hello everyone,
>
> I'm setting up a new build targeting an embedded platform (LM32) and
> trying to integrate a CRC32 into the resulting ELF. I have previously
> done this using plain Makefiles with the following steps (pseudo code):
Constantly I am stumbling over the word "install" in the context of cmake
scripts - while it is pretty clear that the word cannot mean what nowadays
people would understand by that term! But even reading the docs forwards and
backwards, studying examples and some generic cmake tutorials I
Hello everyone,
I'm setting up a new build targeting an embedded platform (LM32) and
trying to integrate a CRC32 into the resulting ELF. I have previously
done this using plain Makefiles with the following steps (pseudo code):
target.elf:
link --symbol CRC_VALUE=0 intermediate.elf
On Mon, Oct 7, 2019 at 11:21 PM Setzer Sebastian (CM-CI2/ECS2) <
sebastian.set...@de.bosch.com> wrote:
> Hi Craig,
>
> On Mon, 7. Oct 2019 12:56 Craig Scott wrote:
> > As it happens, I just updated the docs for these in the last day or so.
>
> You mean you updated the docs of the two commands,
Hi Craig,
On Mon, 7. Oct 2019 12:56 Craig Scott wrote:
> As it happens, I just updated the docs for these in the last day or so.
You mean you updated the docs of the two commands, but you did not update the
docs of the DEPENDS parameter, right?
> There is a difference between the two, but it's
On Mon, Oct 7, 2019, at 6:55 AM, Craig Scott wrote:
>
>
> On Mon, Oct 7, 2019 at 9:32 PM Setzer Sebastian (CM-CI2/ECS2) via CMake
> wrote:
>> Dear list,
>> The manual says:
>> https://cmake.org/cmake/help/latest/command/add_custom_target.html
>> Reference files and outputs of custom
On Mon, Oct 7, 2019 at 9:32 PM Setzer Sebastian (CM-CI2/ECS2) via CMake <
cmake@cmake.org> wrote:
> Dear list,
> The manual says:
> https://cmake.org/cmake/help/latest/command/add_custom_target.html
> Reference files and outputs of custom commands created with
> add_custom_command() command calls
Dear list,
The manual says:
https://cmake.org/cmake/help/latest/command/add_custom_target.html
Reference files and outputs of custom commands created with
add_custom_command() command calls in the same directory (CMakeLists.txt file).
They will be brought up to date when the target is built.
Use
Hello,
I’m experiencing an odd problem where no matter how I set CMP0093, it seems to
use the ‘NEW’ behaviour, breaking some other code relying on the OLD behaviour.
This is Cmake 3.15.4 from Homebrew, other people do report on other platforms
do report the policy working for them. Here’s my
27 matches
Mail list logo
