Hi everyone,
I've been porting our commercial, in-house, unmaintainable Linux product build
process to CMake. It's been remarkably easy, but now I've hit a hurdle.
I need to produce an RPM that will install on both Red Hat 5 and Suse 11. For
political reasons I can't produce two distinct RPMs
On 12/29/2011 08:01 PM, Denis Scherbakov wrote:
> Dear All!
>
> Maybe someone can help me: I have a project, we compile binaries and then
> using various INSTALL directives finish the job by copying files where they
> belong: to "bin", "man", "libexec", etc. The point is, we need to run
> executa
On 12/31/2011 02:10 AM, Robert Dailey wrote:
> I'd like to introduce boost into CMake for this.
Whenever I've advocated CMake as build system, one of the strongest
selling points has been its self-sufficiency, i.e. the fact that it
does not have any external dependencies except for a C++ environm
On 01/05/2012 02:42 PM, Mateusz Loskot wrote:
> On 5 January 2012 12:31, vivek goel wrote:
>> I am using code
>> where f contains the file name
>>
>>
>> set(MY_PATH "-D__RELATIVE_PATH__=\\\"ab\\\"")
>> set_source_files_properties(${f} PROPERTIES
>> COMPILE_FLAGS ${MY_PATH})
>>
>> I am not able t
Hi,
I am writing a library using boost_regex. For the unit test part, I
am using boost_unit_test_framework and needs to be dynamical linked.
Everything worked great on Linux but not the Windows VS 2008.
I used the BoostPro binary installer, got boost components like:
boost_regex-vc90-mt-gd-1_
Using COMPILE_DEFINITIONS is also not working.
set(MY_PATH "__RELATIVE_PATH__=ab")
set_source_files_properties(${f} PROPERTIES
COMPILE_DEFINITIONS ${MY_PATH})
On 1/5/12, Mateusz Loskot wrote:
> On 5 January 2012 12:31, vivek goel wrote:
>> I am using code
>> where f contains the file name
>
Hi David,
This is great news! I have updated the matrix to use footnotes, and also added
the 2.8.7 changes to it. The whole matrix now looks much more clearly:
http://www.cmake.org/Wiki/CMake_Version_Compatibility_Matrix
Cheers,
Johannes
On Tuesday 03 January 2012 17:25:31 David Cole wrote:
I am eager to use DeployQt4 because of the complexity of creating
applications.
This is a snippet of what I currently have:
--
if( APPLE )
set(GUI_TYPE MACOSX_BUNDLE)
set( app_postfix ".app" )
set( plugin_dest_dir bin/${appName}${app_postfix}/Contents/MacOS
On Thursday 05 January 2012, James Sutherland wrote:
> On Wed, Jan 4, 2012 at 2:28 AM, wrote:
> > Does anyone have a working example for the new DeployQt4 module?
>
> I was just looking for the same thing and found this:
> http://mikemcquaid.com/2012/01/deploying-qt-applications-with-deployqt4/
Great thanks
Am 05.01.2012 um 17:30 schrieb James Sutherland :
>
> On Wed, Jan 4, 2012 at 2:28 AM, wrote:
> Does anyone have a working example for the new DeployQt4 module?
>
>
> I was just looking for the same thing and found this:
> http://mikemcquaid.com/2012/01/deploying-qt-application
On Jan 5, 2012, at 11:30 AM, James Sutherland wrote:
>
> On Wed, Jan 4, 2012 at 2:28 AM, wrote:
> Does anyone have a working example for the new DeployQt4 module?
>
>
> I was just looking for the same thing and found this:
> http://mikemcquaid.com/2012/01/deploying-qt-applications-with-dep
On Wed, Jan 4, 2012 at 2:28 AM, wrote:
> Does anyone have a working example for the new DeployQt4 module?
>
>
I was just looking for the same thing and found this:
http://mikemcquaid.com/2012/01/deploying-qt-applications-with-deployqt4/
James
--
Powered by www.kitware.com
Visit other Kitware
On 5 January 2012 12:31, vivek goel wrote:
> I am using code
> where f contains the file name
>
>
> set(MY_PATH "-D__RELATIVE_PATH__=\\\"ab\\\"")
> set_source_files_properties(${f} PROPERTIES
> COMPILE_FLAGS ${MY_PATH})
>
> I am not able to see -D__RELATIVE_PATH__ inside compilation flags.
You
hello,
just installed cdash from svn and using ctest with valgrind and
codecoverage(bullseye) => it's really great, thanks first of all.
Now I would like to test kwstyle but I don't find any recent ctest
script that illustrates it. I tried to look at the notes of the kwstyle
build for cmake
I am using code
where f contains the file name
set(MY_PATH "-D__RELATIVE_PATH__=\\\"ab\\\"")
set_source_files_properties(${f} PROPERTIES
COMPILE_FLAGS ${MY_PATH})
I am not able to see -D__RELATIVE_PATH__ inside compilation flags.
What is wrong ?
--
regards
Vivek Goel
--
Powered by www.ki
On 05/01/2012 01:56, David Cole wrote:
>> Wow. Nice, quick work.
>> >
>> > Thanks for the patch. I'll get it applied and pushed to our 'next'
>> > branch so this can get into the next release...
>> >
>> >
>> > Thanks,
>> > David
> Hmmm. I've downloaded the source from SourceForge, but do not
> repr
On 4.1.2012. 17:05, David Cole wrote:
What project are you running through CMake? Is it available for us to
try to reproduce here?
I've not heard of anything like this...
Actually we've been bitten by this also: ever since 2.8.6 CMake would hang in
the generate phase on OS X. However it only
Hi,
thanks for the help!
Vlado
On Thu, Jan 5, 2012 at 5:53 AM, Fraser Hutchison
wrote:
> Hi there,
>
> This looks like a single line deletion will fix it. I've added a note to
> the issue here: http://public.kitware.com/Bug/view.php?id=8767#c28187 - it's
> probably not worth a patch :-)
>
> Ch
Le 04/01/12 16:16, Eric Noulard a écrit :
However, a general rule with CMake is to consider that cmake itself becomes
a requirement of your build system.
With CMake (at least currently) the developer/user cannot work without CMake
if the project (makefiles, IDE project files (Visual Studio, XCod
19 matches
Mail list logo
