All,
It appears there have been some changes to how macOS handles the
system include path starting with macOS Mojave. It looks like Apple
has provided a workaround package you can install to re-instate the
/usr/include hierarchy, however I was wondering if this is something
that could be handled
We are using cmake for our project and recently discovered that the
generated Makefiles do not seem to work correctly with the '--question' or
'-q' option. They always exit with return code '1' even if there are no
changes which would require rebuilding anything. I am not sure if this is
an issue
Hi,
I see cmake producing a compile_commands.json file that contains a weird
expression like '@<< /TP -DECAL_LAYER_FASTRTPS <<'.
This expression causes an issue in my cmake4eclipse project [1].
The expression looks like a commandfile-specifiation, but the file `<<` does
not exist.
So my
Le mar. 13 nov. 2018 à 00:21, Craig Scott a
écrit :
>
>
> On Tue, Nov 13, 2018 at 9:51 AM Joachim Wuttke
> wrote:
>
>> My understanding was that prevalent usage in modern CMake
>> is all lowercase for function names, all uppercase for
>> macro names. In this sense, I submitted a number of merge
Le mar. 13 nov. 2018 à 10:41, Marc CHEVRIER a
écrit :
> I agree as well that trying to distinguish macros from functions is not a
> good idea because functions can act in the same way as macros (i.e.
> changing calling environment) but with a better control over environment
> changes (changes
I would just like to point out that some modules (ExternalData,
ExternalProject, to name two specific examples) adopted the convention
to prefix all their provided function names with the module name and
an underscore: for example, ExternalProject_Add and
ExternalData_Expand_Arguments.
These
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 9fee70422783af120bdaeff62ba77a71226f611d (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, release has been updated
via ad6ef6c1d5ba1434215bf9e891c87f71514446e9 (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 06ef9edd51a8ffbd77fb96f733cbe45af84e9559 (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 d3b932fa678516d3f5bb7f7209547a876a182d02 (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 3603b3964b308273725198cafdc2ce78a80fa862 (commit)
via
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 19e2da7..823 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 13)
-set(CMake_VERSION_PATCH 20181113)
+set(CMake_VER
On 2018 M11 12, Mon 17:53:38 CET Taylor Holberton wrote:
> Hello everyone!
>
> Today I released a short and sweet C++ library for accessing and modifying
> CMake Cache files.
>
> Feel free to use it, critique it, or ignore it entirely.
>
> You can find it on GitHub, at
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 64bc4bda748b6c33d496fe294e959e7609b89260 (commit)
via
14 matches
Mail list logo
