Thanks for the suggestions! I'll give it a try.
Cheers,
Attila
> On 28 Jan 2016, at 14:07, Domen Vrankar wrote:
>
>> Not sure how we can disable such script call from CPackRPM unless adding the
>> extra feature to call
>> rpm/rpmbuild wiht appropriate
I would like to move the ALL_BUILD target tot he "CMakePredefinedTargets",
however this seems not be possible straight away. At least even at the very end
of the very last CMakeLists.txt I still cannot call
set_target_properties(ALL_BUILD
PROPERTIES
FOLDER " CMakePredefinedTargets ")
On 01/25/2016 11:01 AM, Sam Spilsbury wrote:
> Over the last two years I've been working on a new unit testing
> framework for CMake. I started this project because I've been writing
> some other fairly complex CMake modules and I kept making mistakes
> which would take me hours to debug weeks
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=15941
==
Reported By:hegewald
Assigned To:
Hi Andreas,
thanks for bearing with me (-:
> On 28.01.2016, at 20:28, Andreas Pakulat wrote:
>
> Hi Jan,
>
> On Thu, Jan 28, 2016 at 4:52 PM, Jan Hegewald wrote:
> Hi Andreas,
>
> > On 28.01.2016, at 16:43, Andreas Pakulat wrote:
> >
> >
>From cmGlobalVisualStudioGenerator.cxx (line 92ff):
#if 0
// Can't activate this code because we want ALL_BUILD
// selected as the default "startup project" when first
// opened in Visual Studio... And if it's nested in a
// folder, then that doesn't happen.
//
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=15943
==
Reported By:senz
Assigned To:
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=15944
==
Reported By:hanno
Assigned To:
Dear CMake devs,
please find attached a minimal patch to fix a GCC 6 pedantic warning
concerning a superfluous semicolon after a method.
Additional I got the following warning:
> CMake/Source/cmGeneratorTarget.cxx:4835:52: warning: format ‘%u’ expects
> argument of type ‘unsigned int*’, but
Have you tried setting the toolset? The -T parameter can set the
toolset. This sets the platform toolset property that you would
normally set in Visual Studio. if Visual Studio lets you select the
llvm platform toolset, so will CMake.
On Fri, Jan 29, 2016 at 12:04 PM, Yi-Hong Lyu
On 29-Jan-16 19:04, Yi-Hong Lyu wrote:
Hello everyone,
I am a newbie of CMake. I would like to use clang-cl with MSBuild on
Windows. However it always use MSVC 19.0.23506.0 as the identified
compiler even I defined CMAKE_C_COMPILER / CMAKE_CXX_COMPILER /
CMAKE_C_COMPILER_FORCED /
_VERSION_MINOR 4)
-set(CMake_VERSION_PATCH 20160129)
+set(CMake_VERSION_PATCH 20160130)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
On 1/29/16, Brad King wrote:
> On 01/25/2016 11:01 AM, Sam Spilsbury wrote:
>> Over the last two years I've been working on a new unit testing
>> framework for CMake. I started this project because I've been writing
>> some other fairly complex CMake modules and I kept
On 1/29/2016 1:04 PM, Yi-Hong Lyu wrote:
Hello everyone,
I am a newbie of CMake. I would like to use clang-cl with MSBuild on
Windows. However it always use MSVC 19.0.23506.0 as the identified
compiler even I defined CMAKE_C_COMPILER / CMAKE_CXX_COMPILER /
CMAKE_C_COMPILER_FORCED /
Is it possible to execute commands after the generation step of the
project files?
I want to set custom properties in the generated Visual Studio project,
because it should be built as a driver, which requires a few extra steps.
These changes should be done automatically by CMake (or a script run
Hello everyone,
I am a newbie of CMake. I would like to use clang-cl with MSBuild on
Windows. However it always use MSVC 19.0.23506.0 as the identified compiler
even I defined CMAKE_C_COMPILER / CMAKE_CXX_COMPILER /
CMAKE_C_COMPILER_FORCED / CMAKE_CXX_COMPILER_FORCED:
$ cmake
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15945
==
Reported By:Gehua Yang
Assigned To:
On 1/20/16, Brad King wrote:
> On 01/20/2016 08:48 AM, Eric Wing wrote:
>> I thought maybe setting the internal
>> CMAKE_${lang}_COMPILER_ID_FLAGS_LIST or
>> CMAKE_${lang}_COMPILER_ID_FLAGS
>> to "-version" would fix this.
>>
>> But this did nothing.
>
> Those are internal
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15946
==
Reported By:Dan Kegel
Assigned To:
Just to answer some of your questions on this...
>
> I think the first step is design brainstorming and discussion to see if
> we can find something acceptable.
>
> IIRC one problem with earlier attempts at introducing Lua was that CMake's
> dynamic scoping is difficult to reconcile with Lua's
20 matches
Mail list logo