Am Montag, 6. Februar 2012, 19:12:27 schrieb Michael Pechner:
> Is this the correct forum?
cmake-develop...@cmake.org would be the right place. Or open a bug report at
http://cmake.org/Bug and attach it there.
> What format do you want the patch in?
git format-patch
> My changes are in 2.8.4.
Hello Friends,
How do I specify the default generator that CMAKE should use when invoked
without the "-G" option?
I am on Windows.
I saw an old thread on this. But I am not sure if any support was added later
on.
Is there a REGISTRY entry in Windows that we can set to make so that CMAKE can
ch
Is this the correct forum?
What format do you want the patch in?
My changes are in 2.8.4. Will that be acceptable?
Or do you require I move my changes to 2.8.7 then generate the patch?
--
Michael Pechner
NE6RD - Amateur Extra
mi...@mikey.com
--
Powered by www.kitware.com
Visit other Kitware ope
Replies requested. Short replies only. Read on. Just a short reply
with bug numbers or links to the bugs is all we need here. ...
http://public.kitware.com/Bug/view.php?id=7867 (have CTest report
compiler type/version)
David
--
Powered by www.kitware.com
Visit other Kitware open-s
On 02/06/2012 10:56 PM, Alexander Neundorf wrote:
> On Saturday 04 February 2012, Oliver Smith wrote:
>> My CMakeLists uses the Subversion repository information in a couple of
>> places (it configures a file revision.h and it uses it for the CPack
>> package name).
>>
>> The problem is that this v
Thanks.
This seems to work:
set_property( TARGET foo APPEND_STRING PROPERTY
COMPILE_FLAGS "/ZI "
)
set_property( TARGET foo APPEND_STRING PROPERTY
COMPILE_FLAGS "/W4 "
)
Just make sure you have a space at the end of each one, so that when the
strings are appended, there is a space between each
I believe that is the defined behavior. Usually, people would use
add_definitions() to add the flags before creating the target. If you
have one target per subdirectory, you don't have to worry about removing
them afterwards:
CMakeLists.txt:
add_definitions(/foo)
add_subdirectory(b
I would like to set the COMPILE_FLAGS property multiple times on the same
target through set_target_properties(), however only the last call seems to
persist. Previous flags set get overridden. Is this the correct behavior?
If so, is there a way to make this property append instead of replace on
th
On Saturday 04 February 2012, Oliver Smith wrote:
> My CMakeLists uses the Subversion repository information in a couple of
> places (it configures a file revision.h and it uses it for the CPack
> package name).
>
> The problem is that this variable is cached and retained until the cache
> is rebu
If you supply add_definitions(/ZI) it will override the /Zi default and
provide you with the edit and continue setting.
I verified the behavior with this cmakelists.txt:
With /ZI:
cmake_minimum_required (VERSION 2.8)
project(TestProj CXX)
file(WRITE ${CMAKE_CURRENT_SOURCE_DIR}/main.cpp
In Visual Studio 2008, CMake generates projects to use the /Zi option,
which is just "Program Database" in visual studio. The /ZI option enables
"Program Database with Edit & Continue", allowing the edit & continue
functionality to be used. Is there a built in feature to change the debug
informatio
2012/2/6 Ralf Lange :
> The CMake version is 2.8.2.
> The system is Debian 6.0.4 (squeez).
> The kernel is 2.6.32-5-amd64.
> The Desktop is Gnome 2.30.2.
Could you try, cmake 2.8.7
(may be this fix
http://www.cmake.org/Bug/view.php?id=10325 could solve your problem)
and/or
run cpack in fakeroot l
The CMake version is 2.8.2.
The system is Debian 6.0.4 (squeez).
The kernel is 2.6.32-5-amd64.
The Desktop is Gnome 2.30.2.
CPack generates the deb package. Than I open the package using GDebi
Packet Installer. The installer ask for the superuser password and ends
without installation. The error m
Hi there
The following message in cmTest.cxx doesn't seem to be accurate for Visual
Studio 9.
200 cm->DefineProperty
201 ("WORKING_DIRECTORY", cmProperty::TEST,
202 "The directory from which the test executable will be called.",
203
"If this is not set it is called from the
On Mon, Feb 6, 2012 at 5:44 AM, Ralf Lange wrote:
> Hi,
> I use CPACK to generate RPM and DEB packages for my software. The RPM
> package wirks fine but the DEB package can not create the neccessary
> directories in the usr/lib directory. When I create the direcories by hand,
> it works.
> Who can
2012/2/6 Ralf Lange :
> Hi,
> I use CPACK to generate RPM and DEB packages for my software. The RPM
> package wirks fine but the DEB package can not create the neccessary
> directories in the usr/lib directory. When I create the direcories by hand,
> it works.
> Who can help to fix this problem?
M
Hi,
I use CPACK to generate RPM and DEB packages for my software. The RPM
package wirks fine but the DEB package can not create the neccessary
directories in the usr/lib directory. When I create the direcories by
hand, it works.
Who can help to fix this problem?
Thanks
Ralf
--
Powered by www.ki
17 matches
Mail list logo