date:20130319

[CMake] Cross Compile MySQL Connector/C for Linux/PowerPC architecture using CMake - Failure

2013-03-19 Thread Niranjan M

Hi All,
I am trying to cross compile MySql Connector/C for Linux/PowerPC
architecture and I am getting the below error.

PS: CMAKE Version used is 2.8.7

Command:
Step 1: Setup my tool chain for PowerPC
Step 2: Cmake command

cmake -G "Unix Makefiles"
-DCMAKE_INSTALL_PREFIX=~/NewDataBaseStuff/mysqlclient_c/lib
-DCMAKE_C_COMPILER="ppc_4xx-gcc" -DCMAKE_CXX_COMPILER="ppc_4xx-g++"
-DCMAKE_C_FLAGS="-c -g -static -I. -I/opt/ELDK/4.2/ppc_4xx/usr/include/"
--debug-trycompile

debug trycompile on
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-gcc
-- Check for working C compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-gcc -- works
-- Detecting C compiler ABI info
CMake Error at
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:31
(TRY_COMPILE):
  Cannot copy output executable

''

  to destination specified by COPY_FILE:

'DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeDetermineCompilerABI_C.bin'

  Unable to find the executable at any of:

DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/cmTryCompileExec
DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec

DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Development/cmTryCompileExec

Call Stack (most recent call first):
  /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:71
(CMAKE_DETERMINE_COMPILER_ABI)
  CMakeLists.txt:21 (PROJECT)


-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-g++
-- Check for working CXX compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-g++ --
works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
.
.
.
CMake Error at /usr/share/cmake-2.8/Modules/TestBigEndian.cmake:44
(MESSAGE):
  no suitable type found
Call Stack (most recent call first):
  CMakePlatformTests.txt:200 (TEST_BIG_ENDIAN)
  CMakeLists.txt:267 (INCLUDE)


-- Configuring incomplete, errors occurred!

So I have 2 problems:

1. Failure in detecting Compiler ABI information
2. Failing in Big Endianess test: I checked couple of posts online and
tried to suppress the endianess check by modifying CMakePlatformTests.txt,
but the build process still failed. Below is the log:

debug trycompile on
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-gcc
-- Check for working C compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-gcc -- works
-- Detecting C compiler ABI info
CMake Error at
/usr/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:31
(TRY_COMPILE):
  Cannot copy output executable

''

  to destination specified by COPY_FILE:

'DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeDetermineCompilerABI_C.bin'

  Unable to find the executable at any of:

DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/cmTryCompileExec
DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec

DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Development/cmTryCompileExec

Call Stack (most recent call first):
  /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:71
(CMAKE_DETERMINE_COMPILER_ABI)
  CMakeLists.txt:21 (PROJECT)


-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-g++
-- Check for working CXX compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-g++ --
works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
.
.
.
-- Check size of int8
-- Check size of int8 - failed
-- Check size of uint8
-- Check size of uint8 - failed
-- Check size of int16
-- Check size of int16 - failed
-- Check size of uint16
-- Check size of uint16 - failed
-- Check size of int32
-- Check size of int32 - failed
-- Check size of uint32
-- Check size of uint32 - failed
-- Check size of u_int32_t
-- Check size of u_int32_t - done
-- Check size of int64
-- Check size of int64 - failed
-- Check size of uint64
-- Check size of uint64 - failed
-- Check size of socklen_t
-- Check size of socklen_t - done
-- Performing Test HAVE_TIMESPEC_TS_SEC
-- Performing Test HAVE_TIMESPEC_TS_SEC - Failed
-- Performing Test QSORT_TYPE_IS_VOID
-- Performing Test QSORT_TYPE_IS_VOID - Success
-- Performing Test SIGNAL_RETURN_TYPE_IS_VOID
-- Performing Test SIGNAL_RETURN_TYPE_IS_VOID - Success
-- Performing Test HAVE_ISNAN
-- Performing Test HAVE_ISNAN - Success
-- Performing Test HAVE_RINT
-- Performing Test HAVE_RINT - Success
-- Performing Test C_HAS_inline
-- Performing Test C_HAS_inline - Success
-- Configuring incomplete, errors occurred!

I am attaching the build logs along the mail.

With Regards,
Neo


Make_With_Endianess_Check.log
Description: Binary data


Make_Without_Endianess_Check.log
Description: Binary data
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link

[CMake] Cross Compile MySQL Connector/C for Linux/PowerPC architecture using CMake

2013-03-19 Thread Neo

Hi All,
  I am cross compiling MySQL Connector/C for Linux/PowerPC architecture.
When I run cmake I get the below errors and build process stops.

Command:
Step 1: Setup my toolchain for PowerPC
Step 2: Cmake

cmake -G "Unix Makefiles"
-DCMAKE_INSTALL_PREFIX=~/NewDataBaseStuff/mysqlclient_c/lib
-DCMAKE_C_COMPILER="ppc_4xx-gcc" -DCMAKE_CXX_COMPILER="ppc_4xx-g++"
-DCMAKE_C_FLAGS="-c -g -static -I. -I/opt/ELDK/4.2/ppc_4xx/usr/include/"
--debug-trycompile

debug trycompile on
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-gcc
-- Check for working C compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-gcc -- works
-- Detecting C compiler ABI info
CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:31
(TRY_COMPILE):
  Cannot copy output executable

''

  to destination specified by COPY_FILE:

   
'DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeDetermineCompilerABI_C.bin'

  Unable to find the executable at any of:

   
DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/cmTryCompileExec
   
DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec
   
DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Development/cmTryCompileExec

Call Stack (most recent call first):
  /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:71
(CMAKE_DETERMINE_COMPILER_ABI)
  CMakeLists.txt:21 (PROJECT)


-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-g++
-- Check for working CXX compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
.
.
.
.
-- Check size of unsigned long - done
CMake Error at /usr/share/cmake-2.8/Modules/TestBigEndian.cmake:44 (MESSAGE):
  no suitable type found
Call Stack (most recent call first):
  CMakePlatformTests.txt:200 (TEST_BIG_ENDIAN)
  CMakeLists.txt:267 (INCLUDE)


-- Configuring incomplete, errors occurred!

Basically there are two errors

1. Detecting C compiler ABI info: I checked online for solving this error but
couldn't solve it.
2. Testing Big Endian: Again I checked online and one person who had the similar
problem prevented endianess check which resolved his build issue. I too tried
it. I commented the endianess check in CMakePlatformTests.txt, but my build
still failed because of the first issue. Below is the log.

PS: The same command is run

debug trycompile on
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-gcc
-- Check for working C compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-gcc -- works
-- Detecting C compiler ABI info
CMake Error at /usr/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:31
(TRY_COMPILE):
  Cannot copy output executable

''

  to destination specified by COPY_FILE:

   
'DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeDetermineCompilerABI_C.bin'

  Unable to find the executable at any of:

   
DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/cmTryCompileExec
   
DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec
   
DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Development/cmTryCompileExec

Call Stack (most recent call first):
  /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:71
(CMAKE_DETERMINE_COMPILER_ABI)
  CMakeLists.txt:21 (PROJECT)


-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-g++
-- Check for working CXX compiler: /opt/ELDK/4.2/usr/bin/ppc_4xx-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
.
.
.
-- Check size of int8
-- Check size of int8 - failed
-- Check size of uint8
-- Check size of uint8 - failed
-- Check size of int16
-- Check size of int16 - failed
-- Check size of uint16
-- Check size of uint16 - failed
-- Check size of int32
-- Check size of int32 - failed
-- Check size of uint32
-- Check size of uint32 - failed
-- Check size of u_int32_t
-- Check size of u_int32_t - done
-- Check size of int64
-- Check size of int64 - failed
-- Check size of uint64
-- Check size of uint64 - failed
-- Check size of socklen_t
-- Check size of socklen_t - done
-- Performing Test HAVE_TIMESPEC_TS_SEC
-- Performing Test HAVE_TIMESPEC_TS_SEC - Failed
-- Performing Test QSORT_TYPE_IS_VOID
-- Performing Test QSORT_TYPE_IS_VOID - Success
-- Performing Test SIGNAL_RETURN_TYPE_IS_VOID
-- Performing Test SIGNAL_RETURN_TYPE_IS_VOID - Success
-- Performing Test HAVE_ISNAN
-- Performing Test HAVE_ISNAN - Success
-- Performing Test HAVE_RINT
-- Performing Test HAVE_RINT - Success
-- Performing Test C_HAS_inline
-- Performing Test C_HAS_inline - Success
-- Configuring incomplete, errors occurred!

CMAKE version used is 2.8.7

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] Running tests on remote machine

2013-03-19 Thread Eric Noulard

2013/3/19 Stefan Reuschl :
> If you don't already have a wrapper for add_test(), you can just overwrite
> the add_test() function once without having to change every call to
> add_test(), e.g.:
>
> function(add_test name cmd)
>   _add_test(name ${CMAKE_COMMAND} -P testDriver.cmake -DCOMMAND=${cmd})
> endfunction()
>
> The test driver script can start the remote debugger. That approach worked
> fine for me (I'm only using ssh). The tricky part with that approach was to
> upload/download input/output data files for the test binary.

AFAIK this is not needed for Robert because the VM has the executable
and data files on a network drive.

The only issue may be to translate drive name/prefix if they are different
on the host or on the VM.

>
>
> 2013/3/19 David Cole 
>>
>> Can you run ctest on your development machine, but have each test invoke
>> the remote debugger separately? i.e. -- write a wrapper around add_test
>> which invokes the command via the remote debugger on the VM instead of
>> locally...
>>
>> That might be painful to do if you have lots of tests, and you don’t
>> already have an add_test wrapper. But if you do have a wrapper, it should be
>> easy enough in theory. (Assuming you can drive a remote debugger session via
>> a command line of some sort. Or via a script.)
>>
>>
>> From: Robert Dailey
>> Sent: March 19, 2013 3:33 PM
>> To: Eric Noulard
>> CC: CMake
>> Subject: Re: [CMake] Running tests on remote machine
>>
>> It simply uses TCP connection to the remote machine, using the Windows
>> Remote Debugger service. it handles the details of remote debugging,
>> all I do is point it to the correct executable to run from my project
>> settings on the host machine. No authe
>>
>> The only thing that the program needs on the VM is the runtime
>> libraries, which are available as a separate installer
>> (redistributable package). Basically my VM simulates a production
>> environment for the most part, where if you had installed the program
>> via installer on that machine, it would run in a similar fashion.
>>
>> Looks like I'm stuck making my VM into a dev machine so I can build
>> the code from scratch & run tests :( ... unless anyone has some ideas.
>>
>> On Mon, Mar 18, 2013 at 1:39 PM, Eric Noulard 
>> wrote:
>> > 2013/3/18 Robert Dailey :
>> >> Hi,
>> >>
>> >> I currently have a VM that I use to debug my executables. It has the
>> >> environment setup that is needed by the programs. Naturally, the tests
>> >> also depend on this environment (nothing was really mocked).
>> >>
>> >> The machine hosting the VM is my dev machine, it only has CMake &
>> >> Visual Studio. I set it up to remote debug on the VM, which accesses
>> >> the compiled binaries via network shared folder.
>> >
>> > Does remote debug with Visual enables the host to "run" something on the
>> > remote target without having some part of Visual installed on the
>> > remote target  ?
>> >
>> >> Is there a way I can just run the tests on the VM with CTest? I don't
>> >> want to have to install Perforce, Visual Studio, and CMake on my VM if
>> >> I can avoid it. Note both machines are running Windows.
>> >
>> > AIFAIK CTest has no 'remote run' capability, so you'll need at least
>> > to have CTest
>> > installed on the VM.
>> >
>> > That said I do have a not so different usage.
>> > I need to to distributed testing on a CMake enabled project.
>> > What I currently do is to write a (python)
>> > "test driver script" which does one (or several) remote connection to
>> > the target(s)
>> > and launch the CMake built binaries (and possibly tests inputs) which
>> > are available
>> > through network drive (host mounted on the target(s)).
>> >
>> > That way CTest runs on my host and the executable runs on the remote
>> > targets.
>> > The drawback is that I need to have a relatively "intelligent" scripts
>> > which is able
>> > to remote login and monitor/connect to  stderr, stdin, stdout on the
>> > remote execution.
>> >
>> > My solution currently only works on Unixes or on a remote host which has
>> > an SSH server (ssh is my "generic" remote logion solution).
>> >
>> > Thus my question, how does Visual do the remote login/connection for
>> > debugging?
>> >
>> > --
>> > Erk
>> > Le gouvernement représentatif n'est pas la démocratie --
>> > http://www.le-message.org
>> --
>>
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
>>
>> --
>>
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cm

Re: [CMake] Running tests on remote machine

2013-03-19 Thread David Cole

Can you run ctest on your development machine, but have each test invoke the 
remote debugger separately? i.e. -- write a wrapper around add_test which 
invokes the command via the remote debugger on the VM instead of locally...

That might be painful to do if you have lots of tests, and you don’t already 
have an add_test wrapper. But if you do have a wrapper, it should be easy 
enough in theory. (Assuming you can drive a remote debugger session via a 
command line of some sort. Or via a script.)

From: Robert Dailey
Sent: ‎March‎ ‎19‎, ‎2013 ‎3‎:‎33‎ ‎PM
To: Eric Noulard
CC: CMake
Subject: Re: [CMake] Running tests on remote machine

It simply uses TCP connection to the remote machine, using the Windows
Remote Debugger service. it handles the details of remote debugging,
all I do is point it to the correct executable to run from my project
settings on the host machine. No authe

The only thing that the program needs on the VM is the runtime
libraries, which are available as a separate installer
(redistributable package). Basically my VM simulates a production
environment for the most part, where if you had installed the program
via installer on that machine, it would run in a similar fashion.

Looks like I'm stuck making my VM into a dev machine so I can build
the code from scratch & run tests :( ... unless anyone has some ideas.

On Mon, Mar 18, 2013 at 1:39 PM, Eric Noulard  wrote:
> 2013/3/18 Robert Dailey :
>> Hi,
>>
>> I currently have a VM that I use to debug my executables. It has the
>> environment setup that is needed by the programs. Naturally, the tests
>> also depend on this environment (nothing was really mocked).
>>
>> The machine hosting the VM is my dev machine, it only has CMake &
>> Visual Studio. I set it up to remote debug on the VM, which accesses
>> the compiled binaries via network shared folder.
>
> Does remote debug with Visual enables the host to "run" something on the
> remote target without having some part of Visual installed on the
> remote target  ?
>
>> Is there a way I can just run the tests on the VM with CTest? I don't
>> want to have to install Perforce, Visual Studio, and CMake on my VM if
>> I can avoid it. Note both machines are running Windows.
>
> AIFAIK CTest has no 'remote run' capability, so you'll need at least
> to have CTest
> installed on the VM.
>
> That said I do have a not so different usage.
> I need to to distributed testing on a CMake enabled project.
> What I currently do is to write a (python)
> "test driver script" which does one (or several) remote connection to
> the target(s)
> and launch the CMake built binaries (and possibly tests inputs) which
> are available
> through network drive (host mounted on the target(s)).
>
> That way CTest runs on my host and the executable runs on the remote targets.
> The drawback is that I need to have a relatively "intelligent" scripts
> which is able
> to remote login and monitor/connect to  stderr, stdin, stdout on the
> remote execution.
>
> My solution currently only works on Unixes or on a remote host which has
> an SSH server (ssh is my "generic" remote logion solution).
>
> Thus my question, how does Visual do the remote login/connection for 
> debugging?
>
> --
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Running tests on remote machine

2013-03-19 Thread Robert Dailey

It simply uses TCP connection to the remote machine, using the Windows
Remote Debugger service. it handles the details of remote debugging,
all I do is point it to the correct executable to run from my project
settings on the host machine. No authe

The only thing that the program needs on the VM is the runtime
libraries, which are available as a separate installer
(redistributable package). Basically my VM simulates a production
environment for the most part, where if you had installed the program
via installer on that machine, it would run in a similar fashion.

Looks like I'm stuck making my VM into a dev machine so I can build
the code from scratch & run tests :( ... unless anyone has some ideas.

On Mon, Mar 18, 2013 at 1:39 PM, Eric Noulard  wrote:
> 2013/3/18 Robert Dailey :
>> Hi,
>>
>> I currently have a VM that I use to debug my executables. It has the
>> environment setup that is needed by the programs. Naturally, the tests
>> also depend on this environment (nothing was really mocked).
>>
>> The machine hosting the VM is my dev machine, it only has CMake &
>> Visual Studio. I set it up to remote debug on the VM, which accesses
>> the compiled binaries via network shared folder.
>
> Does remote debug with Visual enables the host to "run" something on the
> remote target without having some part of Visual installed on the
> remote target  ?
>
>> Is there a way I can just run the tests on the VM with CTest? I don't
>> want to have to install Perforce, Visual Studio, and CMake on my VM if
>> I can avoid it. Note both machines are running Windows.
>
> AIFAIK CTest has no 'remote run' capability, so you'll need at least
> to have CTest
> installed on the VM.
>
> That said I do have a not so different usage.
> I need to to distributed testing on a CMake enabled project.
> What I currently do is to write a (python)
> "test driver script" which does one (or several) remote connection to
> the target(s)
> and launch the CMake built binaries (and possibly tests inputs) which
> are available
> through network drive (host mounted on the target(s)).
>
> That way CTest runs on my host and the executable runs on the remote targets.
> The drawback is that I need to have a relatively "intelligent" scripts
> which is able
> to remote login and monitor/connect to  stderr, stdin, stdout on the
> remote execution.
>
> My solution currently only works on Unixes or on a remote host which has
> an SSH server (ssh is my "generic" remote logion solution).
>
> Thus my question, how does Visual do the remote login/connection for 
> debugging?
>
> --
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] How to add a folder to a jar with add_jar?

2013-03-19 Thread Pol

Hi,

how can I add "win64/HelloWorld.dll" located under build/Debug to a jar
using the add_jar command?

if I run

add_jar(HelloWorldPlugin src/java/Foo/HelloWorld.java
build/Debug/win64/HelloWorld.dll)

the whole path is added and otherwise the library is not found.

on command-line I would add the option "-C build/Debug/
win64/NativeWrapper.dll" to the jar command

Should I change the CMAKE running directory or so? WHat would be the best
way to do so?

btw, it's cool that CMake is offering support for java, JNI really asked
for it :)

Running CMake 2.8.10 on windows and linux

Thanks!
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CPack RPM with COMPONENTS packaging

2013-03-19 Thread Eric Noulard

2013/3/19 Theodore Papadopoulo :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I cannot manage to make COMPONENT packaging with RPM to work.
> I clearly see that the CPackRPM.cmake module contains stuff to do so,
> but I cannot manage to make it work at all.
>
> Even the ComponentExampleStart that is given on some of CMake wiki
> page does not work for me and always generates a single package. Am I
> missing something ?

Yes.
For backward compatibility reason component packaging is not the default
behavior for most CPack generator (but NSIS).
See:
cpack --help-variable "CPACK__COMPONENT_INSTALL"

  CPACK__COMPONENT_INSTALL
   Enable/Disable component install for CPack generator .

   Each CPack Generator (RPM, DEB, ARCHIVE, NSIS, DMG, etc...) has a
   legacy default behavior.  e.g.  RPM builds monolithic whereas NSIS
   builds component.  One can change the default behavior by setting this
   variable to 0/1 or OFF/ON.


You have to enable it in you CMakeLists.txt or on the command line:
So for RPM:

cpack -D CPACK_RPM_COMPONENT_INSTALL=1 -G RPM


> If the support is not yet here, what is the best path to obtain this.

It is there but incomplete as the list of pending bugs/features
request can show,
see e.g.:
http://public.kitware.com/Bug/view.php?id=13176
http://public.kitware.com/Bug/view.php?id=12997
and related ones.

> I can easily provide a spec file, but I would at least wish that the
> files corresponding to the components be configured. How can I get them.

Try what is already working and see if it already suits your needs.
If not browse the pending bugs in order to see if any of them is related
to your specific need.
Then ask question here on the concerned bug and you'll certainly get
specific answer.

> And I cannot even see a clean way to provide CPackRPM with my own
> template.

You can use CPACK_RPM_USER_BINARY_SPECFILE in order to provide your template
(see cpack --help-variable CPACK_RPM_USER_BINARY_SPECFILE)

but the spec file used by CPackRPM is a "short-cutted" one.

So that you first need to use:
CPACK_RPM_GENERATE_USER_BINARY_SPECFILE_TEMPLATE
in order to generate a template CPackRPM can handle then modify it
and use CPACK_RPM_USER_BINARY_SPECFILE.

> Any help will be appreciated.

Hope this helps.

-- 
Erk
Le gouvernement représentatif n'est pas la démocratie --
http://www.le-message.org
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] use add_executable AND cuda_add_executable

2013-03-19 Thread landa

Dear all,

I'm working on a visual studio project that is developed in c++ and I have
to integrate a new module developed in cuda. There is an existing cmake file
that I need to update but the problem is that it uses the command
"ADD_EXECUTABLE" for all *.cpp files and I need to use "CUDA_ADD_EXECUTABLE"
for my *.cu files. There is a way to use both of them in the same cmake
file? I found a patch for CMAKE to add native cuda support
(http://www.cmake.org/Bug/print_bug_page.php?bug_id=11887). Someone already
used it?

Thanks for your help.



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/use-add-executable-AND-cuda-add-executable-tp7583730.html
Sent from the CMake mailing list archive at Nabble.com.
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] CPack RPM with COMPONENTS packaging

2013-03-19 Thread Theodore Papadopoulo

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I cannot manage to make COMPONENT packaging with RPM to work.
I clearly see that the CPackRPM.cmake module contains stuff to do so,
but I cannot manage to make it work at all.

Even the ComponentExampleStart that is given on some of CMake wiki
page does not work for me and always generates a single package. Am I
missing something ?

If the support is not yet here, what is the best path to obtain this.
I can easily provide a spec file, but I would at least wish that the
files corresponding to the components be configured. How can I get them.

And I cannot even see a clean way to provide CPackRPM with my own
template.

Any help will be appreciated.

Theo.

rangiroa-> cpack -G RPM -V
CPack: Enable Verbose
CPack Verbose: Read CPack config file:
CPack Verbose: Read CPack configuration file:
/tmp/ComponentExampleStart/build/CPackConfig.cmake
CPack Verbose: Specified generator: RPM
CPack Verbose: Use generator: cmCPackRPMGenerator
CPack Verbose: For project: MyLib
CPack: Create package using RPM
CPack Verbose: Read description file:
/usr/share/cmake/Templates/CPack.GenericDescription.txt
CPack Verbose: [RPM] requested component grouping = ONE_PER_GROUP
CPack Verbose: Remove toplevel directory:
/tmp/ComponentExampleStart/build/_CPack_Packages/Linux/RPM
CPack: Install projects
CPack: - Run preinstall target for: MyLib
CPack: - Install project: MyLib
CPack Verbose: Install configuration: ""
CPack Verbose: Installing:
/tmp/ComponentExampleStart/build/_CPack_Packages/Linux/RPM/MyLib-1.0.0-Linux/usr/lib/libmylib.a
CPack Verbose: Installing:
/tmp/ComponentExampleStart/build/_CPack_Packages/Linux/RPM/MyLib-1.0.0-Linux/usr/bin/mylibapp
CPack Verbose: Installing:
/tmp/ComponentExampleStart/build/_CPack_Packages/Linux/RPM/MyLib-1.0.0-Linux/usr/include/mylib.h
CPack: Create package
CPack Verbose: Package files to:
/tmp/ComponentExampleStart/build/_CPack_Packages/Linux/RPM/MyLib-1.0.0-Linux.rpm
CPackRPM: Will use GENERATED spec file:
/tmp/ComponentExampleStart/build/_CPack_Packages/Linux/RPM/SPECS/mylib.spec
CPack Verbose: Copying final package(s) [1]:
CPack: - package:
/tmp/ComponentExampleStart/build/MyLib-1.0.0-Linux.rpm generated.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFIedMACgkQEr8WrU8nPV3ceACcCTePIgXjLUXB4zORARCkt7Xc
0AAAoLLEdypGsN0ezFujY6cUX/LAKLbj
=G3+k
-END PGP SIGNATURE-
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Do not build targets whose dependencies are not available

2013-03-19 Thread Ansis Māliņš

find_package(a)
if(a_FOUND)
ExternalProject_Add(b PREFIX blabla ...)
endif()


On Mon, Mar 18, 2013 at 7:57 PM, Chris Stankevitz  wrote:

> Hello,
>
> I have a library target ("a") that is a dependency of an executable
> ("b").  I have many more libraries and many more executable, some with
> "complex" dependencies on the others.  Sometimes target "a" cannot be
> built either because the user does not want it built or because
> FIND_PACKAGE failed to find a dependency of "a".
>
> Q: Can cmake automatically not build "b" when "a" is not available?
>
> I hope the answer is "yes" otherwise I will have to add IF(HAVE_A)
> code throughout my CMakeLists.txt file.  Worse, in my complex file I
> will have to add lots of IF(HAVE_C), IF(HAVE_D) etc.
>
> Thank you,
>
> Chris
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] -rdynamic causing problems for compiler checks

2013-03-19 Thread Magnus Therning

Oups, this was due to my own ignorance.  I really shouldn't set
CMAKE_SYSTEM_NAME to "Linux" when cross-compiling for an ARM system
with an RTOS :)  Sorry for the noise.

/M

On Tue, Mar 19, 2013 at 10:44 AM, Magnus Therning  wrote:
> I'm using CMake (2.8.10.2) in an embedded project, which so far has
> worked great.  However, now I'm trying out a newer version of the
> compiler and I'm running into issues with '-rdynamic' when CMake
> checks the compiler.  The issue I see is this:
>
> 
> -- Check for working C compiler:
> /opt/rt-tools/compilers/arm-eabi/bin/arm-eabi-gcc -- broken
> CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61
> (message):
>   The C compiler "/opt/rt-tools/compilers/arm-eabi/bin/arm-eabi-gcc" is not
>   able to compile a simple test program.
>
>   It fails with the following output:
>
>Change Dir: 
> /home/semth/HBwork/floydi/floyd-build/floyd-ninja/CMakeFiles/CMakeTmp
>
>
>
>   Run Build Command:/usr/bin/make "cmTryCompileExec1091315603/fast"
>
>   /usr/bin/make -f CMakeFiles/cmTryCompileExec1091315603.dir/build.make
>   CMakeFiles/cmTryCompileExec1091315603.dir/build
>
>   make[1]: Entering directory
>   `/home/semth/HBwork/floydi/floyd-build/floyd-ninja/CMakeFiles/CMakeTmp'
>
>   /usr/bin/cmake -E cmake_progress_report
>   
> /home/semth/HBwork/floydi/floyd-build/floyd-ninja/CMakeFiles/CMakeTmp/CMakeFiles
>   1
>
>   Building C object
>   CMakeFiles/cmTryCompileExec1091315603.dir/testCCompiler.c.o
>
>   /opt/rt-tools/compilers/arm-eabi/bin/arm-eabi-gcc -o
>   CMakeFiles/cmTryCompileExec1091315603.dir/testCCompiler.c.o -c
>   
> /home/semth/HBwork/floydi/floyd-build/floyd-ninja/CMakeFiles/CMakeTmp/testCCompiler.c
>
>
>   Linking C executable cmTryCompileExec1091315603
>
>   /usr/bin/cmake -E cmake_link_script
>   CMakeFiles/cmTryCompileExec1091315603.dir/link.txt --verbose=1
>
>   /opt/rt-tools/compilers/arm-eabi/bin/arm-eabi-gcc
>   CMakeFiles/cmTryCompileExec1091315603.dir/testCCompiler.c.o -o
>   cmTryCompileExec1091315603 -rdynamic
>
>   arm-eabi-gcc: error: unrecognized option '-rdynamic'
> 
>
> I have the following lines in my tool chain file:
>
> 
> set( CMAKE_SHARED_LIBRARY_LINK_C_FLAGS "" )
> set( CMAKE_SHARED_LIBRARY_LINK_CXX_FLAGS "" )
> 
>
> which does remove the '-rdynamic' argument when compiling the
> *project*, however they don't seem remove the flag on the *compiler
> check*.  I found an old issue that seems related,
> http://www.cmake.org/Bug/view.php?id=9985, it's been closed for years.
>
> Is there some way to remove the flag on compiler checks, or is my only
> option to disable compiler checks alltogether?
>
> /M
>
> --
> Magnus Therning  OpenPGP: 0xAB4DFBA4
> email: mag...@therning.org   jabber: mag...@therning.org
> twitter: magthe   http://therning.org/magnus



-- 
Magnus Therning  OpenPGP: 0xAB4DFBA4
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe   http://therning.org/magnus
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] MinGW Link with -l instead of path?

2013-03-19 Thread J Decker

I'm using MinGW Makefiles as a base and a toolchain file.

I made a (somewhat) simple cmakelists that makes a library, and an
executable that links against it.

Without specifying the toolchain, the link command looks something like

gcc test1.c.obj -o test1 -ltest2
(hmm no, that's what I want it to say)

what it does say is more like

gcc test1.c.obj -o test1 test2.dll.a
or
gcc test1.c.obj -o test1 libtest2.so


can I convince Cmake to generate references to libraries with -l instead of
the path to the library it linked?

; or, the warnings (potential errors?) I'm getting say like...
/bin/ld.exe: warning: libbag.so, needed by ..\..\..\..\libbag.psi++.so,
not found (try using -rpath or -rpath-link)
.../bin/ld.exe: warning: libbag++.so, needed by
..\..\..\..\libbag.psi++.so, not found (try using -rpath or -rpath-link)
.../bin/ld.exe: warning: libbag.externals.so, needed by
..\..\..\..\libbag.psi++.so, not found (try using -rpath or -rpath-link)

these libraries appear in the actual link line several times, both before
and after the libraries in question...

so do I apply the rpath (or rpath-link to the executable or the component
library... (it's actually a program:lib:lib:lib dependency)
(I tried both, and it helped, but only for a little while; probably because
it didn't need to rebuilt, so it wasn't an error. THere aren't any
unresolved symbols (but could there be?)


- a cmake to make a lib and executable ---

cmake_minimum_required(VERSION 2.8)

FILE( WRITE ${CMAKE_CURRENT_SOURCE_DIR}/test1.c "int main() { return f(); }
" )
FILE( WRITE ${CMAKE_CURRENT_SOURCE_DIR}/test2.c "int f() { return 1; } " )

add_library( test2 SHARED test2.c )
add_executable( test1 test1.c )
target_link_libraries( test1 test2 )

--
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] -rdynamic causing problems for compiler checks

2013-03-19 Thread Magnus Therning

I'm using CMake (2.8.10.2) in an embedded project, which so far has
worked great.  However, now I'm trying out a newer version of the
compiler and I'm running into issues with '-rdynamic' when CMake
checks the compiler.  The issue I see is this:


-- Check for working C compiler:
/opt/rt-tools/compilers/arm-eabi/bin/arm-eabi-gcc -- broken
CMake Error at /usr/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61
(message):
  The C compiler "/opt/rt-tools/compilers/arm-eabi/bin/arm-eabi-gcc" is not
  able to compile a simple test program.

  It fails with the following output:

   Change Dir: 
/home/semth/HBwork/floydi/floyd-build/floyd-ninja/CMakeFiles/CMakeTmp



  Run Build Command:/usr/bin/make "cmTryCompileExec1091315603/fast"

  /usr/bin/make -f CMakeFiles/cmTryCompileExec1091315603.dir/build.make
  CMakeFiles/cmTryCompileExec1091315603.dir/build

  make[1]: Entering directory
  `/home/semth/HBwork/floydi/floyd-build/floyd-ninja/CMakeFiles/CMakeTmp'

  /usr/bin/cmake -E cmake_progress_report
  
/home/semth/HBwork/floydi/floyd-build/floyd-ninja/CMakeFiles/CMakeTmp/CMakeFiles
  1

  Building C object
  CMakeFiles/cmTryCompileExec1091315603.dir/testCCompiler.c.o

  /opt/rt-tools/compilers/arm-eabi/bin/arm-eabi-gcc -o
  CMakeFiles/cmTryCompileExec1091315603.dir/testCCompiler.c.o -c
  
/home/semth/HBwork/floydi/floyd-build/floyd-ninja/CMakeFiles/CMakeTmp/testCCompiler.c


  Linking C executable cmTryCompileExec1091315603

  /usr/bin/cmake -E cmake_link_script
  CMakeFiles/cmTryCompileExec1091315603.dir/link.txt --verbose=1

  /opt/rt-tools/compilers/arm-eabi/bin/arm-eabi-gcc
  CMakeFiles/cmTryCompileExec1091315603.dir/testCCompiler.c.o -o
  cmTryCompileExec1091315603 -rdynamic

  arm-eabi-gcc: error: unrecognized option '-rdynamic'


I have the following lines in my tool chain file:


set( CMAKE_SHARED_LIBRARY_LINK_C_FLAGS "" )
set( CMAKE_SHARED_LIBRARY_LINK_CXX_FLAGS "" )


which does remove the '-rdynamic' argument when compiling the
*project*, however they don't seem remove the flag on the *compiler
check*.  I found an old issue that seems related,
http://www.cmake.org/Bug/view.php?id=9985, it's been closed for years.

Is there some way to remove the flag on compiler checks, or is my only
option to disable compiler checks alltogether?

/M

-- 
Magnus Therning  OpenPGP: 0xAB4DFBA4
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe   http://therning.org/magnus
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] REGEX REPLACE help

2013-03-19 Thread Petr Kmoch

Hi all,

I've recently found a nice site for regex trouble: http://regexpal.com/

Maybe you can find it useful.

Petr

On Mon, Mar 18, 2013 at 7:48 PM, Andreas Schneider  wrote:
> On Monday 18 March 2013 18:00:29 David Cole wrote:
>> Use “^.*” at the beginning of the regex and “.*$” at the end of it.
>>
>>
>>
>> The ^ and $ anchor the beginning and end of the input string in CMake, not
>> the beginning and end of a line.
>
> Ok, so it needs to look like this:
>
> +# openjdk
> +find_program(JAVA_EXE java)
> +if (JAVA_EXE)
> +execute_process(
> +COMMAND ${JAVA_EXE} -XshowSettings:properties
> +OUTPUT_QUIET
> +ERROR_VARIABLE __JAVA_SETTINGS
> +ERROR_STRIP_TRAILING_WHITESPACE
> +)
> +
> +string(REPLACE "\n" ";" _JAVA_SETTINGS_LIST "${__JAVA_SETTINGS}")
> +foreach (_line ${_JAVA_SETTINGS_LIST})
> +if ("${_line}" MATCHES ".*java.home")
> +string(REGEX REPLACE "^ *java.home = (.+)/jre$" "\\1"
> _JAVA_PROPERTIES_HOME "${_line}")
> +endif()
> +endforeach()
> +endif()
>
> --
> Andreas Schneider   GPG-ID: F33E3FC6
> www.cryptomilk.orga...@cryptomilk.org
>
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Testing Qt 5 RC 1 CMake files

2013-03-19 Thread lonka

Hi Stephen,

I have tried to build vtk from master (applying your patch) with qt5 but I
can not succeed.
What I get is:

In file included from
/home/rlonka/Qt5.0.1/5.0.1/gcc_64/include/QtCore/qobject.h:55:0,
 from
/home/rlonka/Qt5.0.1/5.0.1/gcc_64/include/QtWidgets/qwidget.h:46,
 from
/home/rlonka/Qt5.0.1/5.0.1/gcc_64/include/QtWidgets/QWidget:1,
 from
/home/rlonka/VTK/GUISupport/Qt/vtkQtDebugLeaksView.h:28,
 from
/home/rlonka/VTK/GUISupport/Qt/vtkQtDebugLeaksView.cxx:15:
/home/rlonka/Qt5.0.1/5.0.1/gcc_64/include/QtCore/qmetatype.h: In
instantiation of
‘QtPrivate::IsPointerToTypeDerivedFromQObject’:
/home/rlonka/Qt5.0.1/5.0.1/gcc_64/include/QtCore/qmetatype.h:557:14:  
instantiated from ‘QtPrivate::QMetaTypeTypeFlags’
/home/rlonka/Qt5.0.1/5.0.1/gcc_64/include/QtCore/qmetatype.h:590:71:  
instantiated from ‘int qRegisterNormalizedMetaType(const QByteArray&, T*,
typename QtPrivate::MetaTypeDefinedHelper::Defined &&
(! QMetaTypeId2::IsBuiltIn))>::DefinedType) [with T = vtkObjectBase*,
typename QtPrivate::MetaTypeDefinedHelper::Defined &&
(! QMetaTypeId2::IsBuiltIn))>::DefinedType =
QtPrivate::MetaTypeDefinedHelper::DefinedType]’
/home/rlonka/Qt5.0.1/5.0.1/gcc_64/include/QtCore/qmetatype.h:618:77:  
instantiated from ‘int qRegisterMetaType(const char*, T*, typename
QtPrivate::MetaTypeDefinedHelper::Defined && (!
QMetaTypeId2::IsBuiltIn))>::DefinedType) [with T = vtkObjectBase*,
typename QtPrivate::MetaTypeDefinedHelper::Defined &&
(! QMetaTypeId2::IsBuiltIn))>::DefinedType =
QtPrivate::MetaTypeDefinedHelper::DefinedType]’
/home/rlonka/VTK/GUISupport/Qt/vtkQtDebugLeaksView.cxx:208:1:   instantiated
from here
/home/rlonka/Qt5.0.1/5.0.1/gcc_64/include/QtCore/qmetatype.h:464:9: error:
invalid application of ‘sizeof’ to incomplete type ‘vtkObjectBase’ 
make[2]: ***
[GUISupport/Qt/CMakeFiles/vtkGUISupportQt.dir/vtkQtDebugLeaksView.cxx.o]
Error 1
make[1]: *** [GUISupport/Qt/CMakeFiles/vtkGUISupportQt.dir/all] Error 2
make: *** [all] Error 2


I am not sure if it has anything to do with the fact that the type argument
to the Q_DECLARE_METATYPE macro must be fully defined, not forward declared
as described here:
porting-from-qt-4-to-qt-5/   

In GUISupport/Qt/vtkQtDebugLeaksView.cxx:208 
Q_DECLARE_METATYPE(vtkObjectBase*);

I am using Ubunty 12.10. x86_64. 
gcc version 4.6.3

Do you have any idea if there is anything I can do to get it compiled? 



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/Testing-Qt-5-Beta-2-CMake-files-tp7582503p7583723.html
Sent from the CMake mailing list archive at Nabble.com.
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Cross Compile MySQL Connector/C for Linux/PowerPC architecture using CMake - Failure

[CMake] Cross Compile MySQL Connector/C for Linux/PowerPC architecture using CMake

Re: [CMake] Running tests on remote machine

Re: [CMake] Running tests on remote machine

Re: [CMake] Running tests on remote machine

[CMake] How to add a folder to a jar with add_jar?

Re: [CMake] CPack RPM with COMPONENTS packaging

[CMake] use add_executable AND cuda_add_executable

[CMake] CPack RPM with COMPONENTS packaging

Re: [CMake] Do not build targets whose dependencies are not available

Re: [CMake] -rdynamic causing problems for compiler checks

[CMake] MinGW Link with -l instead of path?

[CMake] -rdynamic causing problems for compiler checks

Re: [CMake] REGEX REPLACE help

Re: [CMake] Testing Qt 5 RC 1 CMake files

15 matches

Site Navigation

Mail list logo

Footer information