t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index c0b209c..381fbe3 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 15)
-set(CMake_VERSION_PATCH 20190605)
+set(CMake_VER
Le mer. 5 juin 2019 à 12:00, Mathieu Malaterre
a écrit :
> Hi there,
>
> I am trying to use NuGet generator for GDCM project. Typically my
> install rules are as follow:
>
> add_library(foo SHARED foo.c)
> install(TARGETS foo
> EXPORT ${MY_TARGETS_NAME}
> RUNTIME DESTINATION
Tom,
That was a really helpful tip. At least as far as building goes, I've
ported my app. Now on to debugging the system nuances.
Ty!
On Wed, Jun 5, 2019 at 12:13 PM Tom Finegan wrote:
>
> On Wed, Jun 5, 2019 at 9:29 AM Bryan Christ
> wrote:
>
>> Tom,
>>
>> I'll give that a try. Can that
On Wed, Jun 5, 2019 at 9:29 AM Bryan Christ wrote:
> Tom,
>
> I'll give that a try. Can that variable be changed after project() is
> called?
>
Yes, you should be able to change it at any point in your CMake script(s).
Remember that CMAKE__LINKER_FLAGS will effect all targets.
Restricting
Tom,
I'll give that a try. Can that variable be changed after project() is
called?
On Tue, Jun 4, 2019 at 5:24 PM Tom Finegan wrote:
> I think you want CMAKE_SHARED_LINKER_FLAGS:
>
> https://cmake.org/cmake/help/latest/variable/CMAKE_SHARED_LINKER_FLAGS.html
>
> You can also use
Yes. Unfortunately the version of curses which is supplied by XCode
doesn't include the wide character support so I have to point elsewhere.
On Tue, Jun 4, 2019 at 5:57 PM Juan E. Sanchez
wrote:
> Hello,
>
> It looks like you are making progress. Note that to use the gcc-8 and
> g++-8
El 05/06/19 a las 11:51, Brad King escribió:
On 6/5/19 8:27 AM, Gonzalo Garramuño wrote:
This used to print out all that cpack was doing while it was doing it.
Now with v3.15.0-rc1 it just sits there and outputs all the text at the
end when it finishes, which sucks as it looks like it has
On 6/5/19 8:27 AM, Gonzalo Garramuño wrote:
> This used to print out all that cpack was doing while it was doing it.
> Now with v3.15.0-rc1 it just sits there and outputs all the text at the
> end when it finishes, which sucks as it looks like it has hung.
Thanks for trying the release
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 8c704cfad4deee359fb65cd49a7cf4686130d8ea (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 556277eb100c2fa061677a59be33eb71876a2a72 (commit)
via
I run cpack with the trick of using a custom configuration.
ADD_CUSTOM_TARGET( bundle
COMMAND "${CMAKE_CPACK_COMMAND}"
"-C" "$"
"--config" "${CMAKE_BINARY_DIR}/BundleConfig.cmake"
COMMENT "Running CPack. Please wait..."
Hi,
I encapsulate the literal **project** call in a **macro** that is adding
some general settings required for every project setup.
This worked flawlessly and without warnings in the last CMake versions
since 3.4.
Beginning with CMake Version 3.15.0-rc1 the following warning pops up:
No
Hi there,
I am trying to use NuGet generator for GDCM project. Typically my
install rules are as follow:
add_library(foo SHARED foo.c)
install(TARGETS foo
EXPORT ${MY_TARGETS_NAME}
RUNTIME DESTINATION ${MY_INSTALL_BIN_DIR} COMPONENT Applications
LIBRARY DESTINATION ${MY_INSTALL_LIB_DIR}
13 matches
Mail list logo
