Re: [CMake] CMake Digest, Vol 99, Issue 61

Hi Christian, Mike's comment about setting BOOST_ROOT should work. If this doesn't, make sure that your directories look like this: C:\boost C:\boost\include C:\boost\include\boost-1_50 C:\boost\include\boost-1_50\boost C:\boost\lib With the above arrangement of directories, FindBoost.cmake s

Re: [CMake] stderr and stdout in cmake

On 07/30/2012 04:12 PM, luxInteg wrote: > Greetings > > I have a bash script (from an auto-tools Makefile ) to translate > to cmake > > > My 'translation might go something like thios > > execute_process(COMMAND ${some_command} '2>&1' INPUT_FILE > ${someFile2} OUTPUT_FILE/dev/nul

Re: [CMake] Recommended Multilib Build Approach?

On 07/30/2012 11:28 PM, Xavier Besseron wrote: On Mon, Jul 30, 2012 at 9:44 PM, Alexander Neundorf wrote: On Monday 30 July 2012, Xavier Besseron wrote: To build i386 binaries on my 64-bit system with multilib, I just do something like this: mkdir build-i386 cd build-i386 CFLAGS="-m32" CXXFLA

Re: [CMake] Problems with FindBoost.cmake

Where is your boost installed at? What operating system are you using? Is this boost precompiled or compiled by you? If you set BOOST_ROOT as a cmake variable and point it to the top level directory of your boost installation does that help? For example if you boost is installed in C:\Boost then

[CMake] Problems with FindBoost.cmake

Hi there, I'm trying to figure why cmake cannot find my boost installation. Actually, I'm working of some outdated boost's trunk version ( 1.50 ). I'm setting various variables, like BOOST_ROOT, BOOST_INCLUDEDIR, etc. But findBoost.cmake always comes up with Boost_FOUND = FALSE. Here is the output

[CMake] VC++10 change WIN32_EXECUTABLE per configuration

I need a way to have the WIN32_EXECUTABLE property set off for debug builds and on for release builds when using the IDE. Here's the deal: For debug our code uses the standard main() construct, and for release we use the WinMain(). Lets just say there's a reason and leave it at that... The obvious

Re: [CMake] Recommended Multilib Build Approach?

On Mon, Jul 30, 2012 at 9:44 PM, Alexander Neundorf wrote: > On Monday 30 July 2012, Xavier Besseron wrote: >> To build i386 binaries on my 64-bit system with multilib, I just do >> something like this: >> >> mkdir build-i386 >> cd build-i386 >> CFLAGS="-m32" CXXFLAGS="-m32" LDFLAGS="-melf_i386" c

[CMake] Mastering CMake 6th edition?

Hi, I'm curious as to whether there will be a 6th edition of this wonderful book. If so, any (rough?) estimate on when it will be published? Thanks so much! Xu -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please k

Re: [CMake] Recommended Multilib Build Approach?

On Monday 30 July 2012, Xavier Besseron wrote: > Hello Greg, > > > To build i386 binaries on my 64-bit system with multilib, I just do > something like this: > > mkdir build-i386 > cd build-i386 > CFLAGS="-m32" CXXFLAGS="-m32" LDFLAGS="-melf_i386" cmake ../src/ > > And to build x86-64 binaries

[CMake] Automating package installion if not there

I have a project. Which is getting build-ed from different developers on different system. Is there a way I can automate package installation of not found for packages like: - gcc - yacc If not is there a way I can pre check if particular tool is installed or not. If not show a good message

[CMake] How to automate building of third party library using cmake

What I am looking for: - Download library - Extract It - Apply custom patch - Run configure - Run build command What library I am trying to build are: - Openssl - Boost - Thrift - C-ares - Curl - Pcre - Nginx - ICU - JsonCPP I think I can do these thi

Re: [CMake] Recommended Multilib Build Approach?

On Monday 30 July 2012, Gregory Peele ARA/CFD wrote: > From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net] > Sent: Saturday, July 28, 2012 11:48 AM > To: cmake@cmake.org > Cc: Gregory Peele ARA/CFD > Subject: Re: [CMake] Recommended Multilib Build Approach? > > On Thursday 21 June 2012, Greg

Re: [CMake] Recommended Multilib Build Approach?

Hello Greg, To build i386 binaries on my 64-bit system with multilib, I just do something like this: mkdir build-i386 cd build-i386 CFLAGS="-m32" CXXFLAGS="-m32" LDFLAGS="-melf_i386" cmake ../src/ And to build x86-64 binaries on my 64-bit system, I don't need to specify anything since it is th

Re: [CMake] Recommended Multilib Build Approach?

From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net] Sent: Saturday, July 28, 2012 11:48 AM To: cmake@cmake.org Cc: Gregory Peele ARA/CFD Subject: Re: [CMake] Recommended Multilib Build Approach? On Thursday 21 June 2012, Gregory Peele ARA/CFD wrote: >> Hi all, >> >> I want to be able to bu

[CMake] stderr and stdout in cmake

Greetings I have a bash script (from an auto-tools Makefile ) to translate to cmake My 'translation might go something like thios execute_process(COMMAND ${some_command} '2>&1' INPUT_FILE${someFile2} OUTPUT_FILE/dev/null

Re: [CMake] multiple line of comment howto

Hi. I think you're looking for ... COMMENT "${line0}\n${line1}\n${line2}\n${line1}\n${line0}" ... Petr On Mon, Jul 30, 2012 at 11:42 AM, luxInteg wrote: > Greetings > > I am learniong cmake. From the documentation:- > add_custom_target(Name [ALL] [command1 [args1...]] > [C

[CMake] multiple line of comment howto

Greetings I am learniong cmake. From the documentation:- add_custom_target(Name [ALL] [command1 [args1...]] [COMMAND command2 [args2...] ...] [DEPENDS depend depend depend ... ] [WORKING_DIRECTORY dir] [COMMENT comme

Re: [CMake] Disabling C for C++-only projects

Am 26.07.2012, 17:53:01 schrieb Alexander Neundorf: > On Thursday 26 July 2012, Johannes Zarl wrote: > > On Wednesday 25 July 2012 22:20:55 Clinton Stimpson wrote: > > > This has already been fixed in FindQt4 since CMake 2.8.6. > > > > ...using cmake 2.8.9-rc1 from debian. > > if you use it toget