On Fri, Nov 2, 2012 at 5:44 PM, Eskandar Ensafi
wrote:
> I'm not sure if I'm qualified to propose a patch, but I will look at the
> source code to see what I can come up with. I have additional concerns about
> the way the CMAKE_ARGVn variables are initialized, and this might be a good
> time
I'm not sure if I'm qualified to propose a patch, but I will look at the source
code to see what I can come up with. I have additional concerns about the way
the CMAKE_ARGVn variables are initialized, and this might be a good time to
address these concerns.
I don't know if this was a design ch
On 2012-11-02 17:14, Bill Hoffman wrote:
On 11/2/2012 5:00 PM, Dominik Schmidt wrote:
With the latest release of CMake compilation of Tomahawk Player stopped
working
Why can't people try the rc releases :(
We put them out there so that stuff can get fixed before the release.
Any ideas on h
On 02.11.2012 22:26, Bill Hoffman wrote:> On 11/2/2012 5:18 PM, Dominik
Schmidt wrote:
>> Anyways I promise to test next RC releases :-)
>>
> That would be great. It was half rant/ half what do we have to do?
> It just seems that people find the time as soon as the "real" release
> comes out.
Bill Hoffman wrote:
> On 11/2/2012 5:00 PM, Dominik Schmidt wrote:
> > With the latest release of CMake compilation of Tomahawk Player stopped
> > working
>
> Why can't people try the rc releases :(
>
> We put them out there so that stuff can get fixed before the release.
> Any ideas on how t
On 02.11.2012 22:14, Bill Hoffman wrote:> On 11/2/2012 5:00 PM, Dominik
Schmidt wrote:
>> With the latest release of CMake compilation of Tomahawk Player stopped
>> working
> Why can't people try the rc releases
>
> We put them out there so that stuff can get fixed before the release.
> Any i
On 11/2/2012 5:00 PM, Dominik Schmidt wrote:
With the latest release of CMake compilation of Tomahawk Player stopped
working
Why can't people try the rc releases :(
We put them out there so that stuff can get fixed before the release.
Any ideas on how to get projects to try the rc's to avo
Moin!
With the latest release of CMake compilation of Tomahawk Player stopped
working for us because automoc stopped producing output for a certain file.
Obviously code ifdef'ed by "#if QT_VERSION >= 0x040400" isn't scanned
anymore. Is that on purpose?
Best regards,
Dominik
P.S.: Commit th
Vyacheslav Karamov wrote:
> Thank you very much, Eric!
> It works!
>
> --- CMakeLists.txt --
>
> include (FindSubversion)
>
> if (NOT Subversion_FOUND)
> message(FATAL_ERROR "Please install subversion command-line client and
> add its folder to the system PATH")
> endif()
On Nov 2, 2012, at 9:29 AM, Gary Little wrote:
> Is any time frame when CMake 2.8.10 will be added to MacPorts?
>
> And to put my time where my mouth is, m ay I be of assistance? Are there
> files I can acquire that would allow me to do add it?
This question is probably better asked on the MacP
Is any time frame when CMake 2.8.10 will be added to MacPorts?
And to put my time where my mouth is, m ay I be of assistance? Are there files
I can acquire that would allow me to do add it?
Gary Little
H (952) 223-1349
C (952) 454-4629
gglit...@comcast.net
--
Powered by www.kitware.com
Visit
Oh, that is some kind of special street magic!
RPATH is empty without these lines in CMakeLists.txt
set(CPACK_PROJECT_CONFIG_FILE ${CMAKE_SOURCE_DIR}/cmake/CPackOptions.cmake)
if(${CMAKE_SYSTEM_NAME} STREQUAL "Linux" AND EXISTS
"${CMAKE_ROOT}/Modules/CPack.cmake")
set(CPACK_PACKAGING_INS
Thank you very much, Eric!
It works!
--- CMakeLists.txt --
include (FindSubversion)
if (NOT Subversion_FOUND)
message(FATAL_ERROR "Please install subversion command-line client and
add its folder to the system PATH")
endif()
# Update working copy at every non-debug bu
When a test times out, I want to inspect its state to look for deadlocks. Is
there a way to get ctest to save a corefile from a process it kills due to
timing out? Is there a way to configure it to use a custom signal that I can
catch in my tests?
I may have asked this before. I remember ctest
Hi,
I'm still having problems with this. It seems my swig is not creating
the output directory for the swig generated cxx file. To get this to
work I have had to add a further make_directory command to the custom
command to create the required output directory before the file is swigged.
I
Hello,
I filed a bug: http://www.cmake.org/Bug/view.php?id=13643
Regards,
Gregoire
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Clinton Stimpson
Sent: jeudi 1 novembre 2012 15:05
To: Stephen Kelly
Cc: cmake@cmake.org
Subject: Re: [CMake
"--" for script mode is a good idea. (Actually, if we had this for
non-script mode even, it would then make sense to expose the command
line arguments in similar variables even when configuring a CMakeLists
file. Presently, the CMAKE_ARGVn vars are only available in script
mode.)
Can you propose a
The scripts that buld the CMake release binaries are in CMake/Utilities/Release.
If you have a system-installed OpenSSL, then setting the cache
variable CMAKE_USE_OPENSSL should be sufficient.
If not, and you have a custom built openssl, you need to set the
following variables as well:
CMAKE_USE
2012/11/1 Vyacheslav Karamov :
> Hi All!
>
> Is it possible to change rpath at the packaging stage?
CPack is using cmake_install.cmake scripts which gets influenced
by CMAKE_INSTALL_RPATH variable and/or INSTALL_RPATH target property.
Did you try to play with that? i.e.
SET(CMAKE_INSTALL_RPATH "
2012/11/2 Ralph Zhang :
> Hi guys
>
> I'm working on a project which generates quite a few executables, libraries
> and configs, they need to be packed into different packages for deployment.
> The problem is, the inclusion of those targets/files is not mutual
> exclusive. One target/file can belon
20 matches
Mail list logo
