2009/3/25 Alexander Neundorf
> On Tuesday 24 March 2009, ankit jain wrote:
> > hi all,
> >
> > Iam doing the following through my cmakelist.txt
> >
> > add_custom_target(mytarget)
> > add_custom_command(TARGET mytarget POST_BUILD
> > COMMAND ${CMAKE_COMMAND} -E tar xvf ${CMAKE_CURRENT_SOURCE_DIR}
Hello All,
I have been experimenting with CMake to compile a large Fortran project with
the Intel Fortran compiler ifort. I am having trouble getting the executable
to link with the static intel libraries, because CMake is adding the linker
flag "i_dynamic" and it is overriding my --static-int
On Tue, Mar 24, 2009 at 12:11 PM, Nadir SOUALEM wrote:
> Tyler wrote:
> Not so bad, but it would be very nice to do some things such adding
> preprocessing on command line calls:
> cmake -DPREPROCCESSING_VAR
>
You could certainly file a feature request that did something like this but
I think it
I'm having a problem creating a toolchain file for use with cmake 2.6.3. I'd
like to generate a UnixMakefile compatible with the QNX Momentics cross
platform development tools. The problem is cmake doesn't seem to find the
archiver which is named ntox86-ar.exe (as QNX runs on multiple platforms
the
Ha, ok I see I was thinking of this the wrong way...
Thanks a lot :-)
--
Alex
2009/3/25 Brad King
> Andreas Pakulat wrote:
>
>> The easiest way to achieve what you want (having targets of
>> projectB+projectC available to projectA) is by having the
>> FindProjectB.cmake file simply do a fi
Daniel Nelson wrote:
So it sounds like the only way to fix this would be to write a separate
flags.make file for every object file that has compile/define flags set? I opened
this as issue 8787 in the bug tracker.
We tried that, it was way to slow with all those files. Especially on
Windo
I have noticed that CMake can be a little inconsistent with how drive
letters are managed.
Sometimes I get paths with "C:\" sometimes with "c:\". When I
generate custom build time scripts using configure_file, often the
files change with only this letter change?
Even the CMakeCache.txt can chang
On Tuesday 24 March 2009 4:46:29 pm Clinton Stimpson wrote:
> Daniel Nelson wrote:
> > On Tuesday 24 March 2009 3:16:27 pm Alexander Neundorf wrote:
> >> On Tuesday 24 March 2009, Alexander Neundorf wrote:
> >>> On Friday 20 March 2009, Daniel Nelson wrote:
> It looks like the projects flags.m
Daniel Nelson wrote:
On Tuesday 24 March 2009 3:16:27 pm Alexander Neundorf wrote:
On Tuesday 24 March 2009, Alexander Neundorf wrote:
On Friday 20 March 2009, Daniel Nelson wrote:
It looks like the projects flags.make is updated every time any compile
flag or definition changes
On Tuesday 24 March 2009 3:16:27 pm Alexander Neundorf wrote:
> On Tuesday 24 March 2009, Alexander Neundorf wrote:
> > On Friday 20 March 2009, Daniel Nelson wrote:
> > > It looks like the projects flags.make is updated every time any compile
> > > flag or definition changes, and every object file
On Tuesday 24 March 2009, Alexander Neundorf wrote:
> On Friday 20 March 2009, Daniel Nelson wrote:
> > It looks like the projects flags.make is updated every time any compile
> > flag or definition changes, and every object file in the project depends
> > on flags.make. In the case of properties s
I'm trying to create an RPM installer for my project using CPack. My
environment is cmake-2.7 prerelease built from CVS on 2009-03-05 on a Fedora
Core 10 32-bit x86 host. At the bottom of my top-level CMakeLists.txt file
I have the following:
# build an installer
include (InstallRequiredSystemLib
On Tue, Mar 24, 2009 at 2:39 PM, Alexander Neundorf
wrote:
> On Tuesday 24 March 2009, Denis Scherbakov wrote:
>> Dear CMake Community,
>>
>> I have an external executable which requires a library, which is not in
>> LD_LIBRARY_PATH. If I manually set ENV{LD_LIBRARY_PATH} and then execute a
>> co
KSpam wrote:
My build system relies heavily on CMAKE_CURRENT_LIST_FILE. For instance, I
typically get a variable for the directory containing the current list file
as follows:
get_filename_component(scriptDir ${CMAKE_CURRENT_LIST_FILE} PATH)
This has worked in prior versions of CMake; howeve
On Tuesday 24 March 2009, Denis Scherbakov wrote:
> Dear CMake Community,
>
> I have an external executable which requires a library, which is not in
> LD_LIBRARY_PATH. If I manually set ENV{LD_LIBRARY_PATH} and then execute a
> command, it works.
>
> But the problem is that the executable is insi
My build system relies heavily on CMAKE_CURRENT_LIST_FILE. For instance, I
typically get a variable for the directory containing the current list file
as follows:
get_filename_component(scriptDir ${CMAKE_CURRENT_LIST_FILE} PATH)
This has worked in prior versions of CMake; however, it does not
On Tuesday 24 March 2009, ankit jain wrote:
> hi all,
>
> Iam doing the following through my cmakelist.txt
>
> add_custom_target(mytarget)
> add_custom_command(TARGET mytarget POST_BUILD
> COMMAND ${CMAKE_COMMAND} -E tar xvf ${CMAKE_CURRENT_SOURCE_DIR}/t1.tar)
> this cmakelist is written in subfold
On Monday 23 March 2009, Andreas Pakulat wrote:
> On 23.03.09 16:29:24, Bob Tanner wrote:
> > On 2009-03-23 02:36:37 -0500, Andreas Pakulat said:
> >>> Looking into cmake files, I do see my name all over :-)
> >>
> >> Seems like you did an in-source build. CMake suggests to use
> >> out-of-source
On Sunday 22 March 2009, Steven Van Ingelgem wrote:
> Hi,
>
>
> I'm trying to read in a C-header file with "file(READ)":
> file(READ "zconf.in.h" ZCONF_H)
>
> !! But this variable contains no ";" whatsoever?
>
> How can I ask to read it in completely?
Can you please explain what problem you have
On Friday 20 March 2009, Daniel Nelson wrote:
> It looks like the projects flags.make is updated every time any compile
> flag or definition changes, and every object file in the project depends on
> flags.make. In the case of properties set using set_property() the only
> part of the flags.make th
Andreas Pakulat wrote:
The easiest way to achieve what you want (having targets of
projectB+projectC available to projectA) is by having the
FindProjectB.cmake file simply do a find_package(ProjectC REQUIRED) call
and then make sure that FindProjectC.cmake (or the ConfigProjectC.cmake)
load the f
Robert Dailey wrote:
What exactly does this mean:
- Enforce unique binary directories
Does this mean instead of all executables going inside bin/debug, that
they go inside of something like bin//debug (For the debug
configuration, it would be likewise for release)?
No, it means that
ad
What exactly does this mean:
> - Enforce unique binary directories
Does this mean instead of all executables going inside bin/debug, that they
go inside of something like bin//debug (For the debug
configuration, it would be likewise for release)?
___
P
Bartlett, Roscoe A wrote:
Hello,
Does anyone know if the XCode generator for CMake support Fortran as a
compiler? We have a Trilinos developer that tried to use CMake to
generate an XCode project but it does not know how to handle the Fortran
files.
Xcode itself does not support Fortran
Hello,
Does anyone know if the XCode generator for CMake support Fortran as a
compiler? We have a Trilinos developer that tried to use CMake to generate an
XCode project but it does not know how to handle the Fortran files.
Thanks,
- Ross
-
On 25.03.09 00:01:02, Asmodehn Shade wrote:
> Hi,
>
> I am assuming it is at the moment (cmake 2.6.2 ) not possible to export an
> imported target...
No.
> What about having the imported target and its properties transitively
> exported again ?
> Has this been planned for the future or ruled out
Hi,
I am assuming it is at the moment (cmake 2.6.2 ) not possible to export an
imported target...
When I do :
# ${MyProject_EXPORT_CMAKE} contains the file path to a cmake script
generated by export,
# declaring ADD_LIBRARY(MyProject SHARED IMPORTED) ( among other stuff )
include(${MyProject_EXP
Hi, Brad,
Yes I think the second call was using the correct target...
sorry I cant be sure or provide a test example, it was quite some time
ago...
I've been a bit busy implementing some cmake script for automated
dependencies detection and propagation in a chain of project depending on
each ot
> > Specifying the lib4 dependency in the exe? But what about
dependencies
> > order in the link line? In my example, lib4-A or lib4-B must appear
> > after lib3, if I want lib4 symbols required by lib3 to be added. In
your
> > solution, lib4 might as well be added by cmake just after lib1 and
> >
On Tue, Mar 24, 2009 at 04:37:31PM +0100, Jonatan Bijl wrote:
> To compile the native part, a c header file is generated from the java
> class, using the "javah -jni" command. This header file should only be
> generated if:
>
> It does not exist yet
>
> The java class changes
>
>
>
> My first
Tyler wrote:
On Tue, Mar 24, 2009 at 04:55:53PM +0100, Nadir SOUALEM wrote:
Thank you Tyler , i use the same method for linking, but i thought there
was a better way than:
if (WITH_OPENGL)
add_definitions (-DOPENGL)
else (WITH_OPENGL)
add_definitions (-DNO_OPENGL)
endif (WITH_OPENGL)
for p
On Tue, Mar 24, 2009 at 04:55:53PM +0100, Nadir SOUALEM wrote:
> Thank you Tyler , i use the same method for linking, but i thought there
> was a better way than:
>
> if (WITH_OPENGL)
> add_definitions (-DOPENGL)
> else (WITH_OPENGL)
> add_definitions (-DNO_OPENGL)
> endif (WITH_OPENGL)
>
> for
Tyler Roscoe wrote:
On Tue, Mar 24, 2009 at 09:18:01AM +0100, Nadir SOUALEM wrote:
I would like to use precompilation directive such NO_OPENGL
Is there a way to use it with this command line ?
cmake -DCMAKE_BUILD_TYPE=Debug
or must i use something like:
cmake -DCMAKE_BUILD_TYPE=Debug -DWITH_
I am setting up a jni project (Java Native Interface). A java class is
supposed to call native methods, and the native methods are to be
compiled into a dll/so.
To compile the native part, a c header file is generated from the java
class, using the "javah -jni" command. This header file should onl
On Tue, Mar 24, 2009 at 09:18:01AM +0100, Nadir SOUALEM wrote:
> I would like to use precompilation directive such NO_OPENGL
> Is there a way to use it with this command line ?
> cmake -DCMAKE_BUILD_TYPE=Debug
>
> or must i use something like:
> cmake -DCMAKE_BUILD_TYPE=Debug -DWITH_OPENGL=0
>
>
Mostly to fix the issue with Visual Studio and header files that was
introduced with CMake 2.6.3, I am working on 2.6.4. I have a release
candidate that can be found here:
http://www.cmake.org/files/v2.6
Specifically, the windows one with the visual studio fix is here:
http://www.cmake.org/fi
I just generated an Xcode project for one of my own projects that uses
boost and the OP is correct, code completion doesn't seem to work for
boost. Odd.
Fortunately I use Eclipse CDT for C++ instead of Xcode which seems
to work reasonably well on OS X. At least I get boost code
completi
Nadir SOUALEM wrote:
I would like to use precompilation directive such NO_OPENGL
Is there a way to use it with this command line ?
cmake -DCMAKE_BUILD_TYPE=Debug
or must i use something like:
cmake -DCMAKE_BUILD_TYPE=Debug -DWITH_OPENGL=0
with an if statement:
if(NOT WITH_OPENGL)
ADD_DEFINITION
Alastair Rankine wrote:
Hi,
I must be blind but I can't see a way for CTest to pass a command line
argument to a test executable?
I've tried using
--test-command "testExe myargs"
... but this causes it to not find the executable.
Any help appreciated, thanks.
Just put --test-command last
I do not know about Xcode, but Visual Studio code completion depends on the
header files being added to the project files. Are the headers in question
included in the project file?
Do you have an example non-CMake generated Xcode project that demonstrates
code completion working with boost headers?
On 3/24/09 10:20 AM, Doug Henry said:
>Quick question about the cmake xcode project generator. I can run cmake and
>build my project just fine using cmake under Leopard from the terminal and
>from xcode, so there is no build problem. I was wondering if anyone has
>code completion working for the
Thanks Bill, effectively part of a project was setting a -D flag based on
the value of BUILD_TESTING. Refactored some code and everything is behaving
as expected now :)
Cheers
2009/3/23 Bill Hoffman
> Adolfo Rodríguez wrote:
>
>> I'm not setting any -D flags that depend on BUILD_TESTING. I only
Quick question about the cmake xcode project generator. I can run cmake and
build my project just fine using cmake under Leopard from the terminal and
from xcode, so there is no build problem. I was wondering if anyone has
code completion working for their project? To be more specific, when usin
I am not sure, but I think you could also look into ADD_CUSTOM_COMMAND
and it's PRE_LINK feature. You could run your own script before linking
is done and replace lib4 target with what you want - lib4a version or lib4b.
Denis
___
Powered by www
> Specifying the lib4 dependency in the exe? But what about
> dependencies
> order in the link line? In my example, lib4-A or lib4-B
> must appear
> after lib3, if I want lib4 symbols required by lib3 to be
> added. In your
> solution, lib4 might as well be added by cmake just after
> lib1 and
> b
It should as long as both file names are files (as opposed to
directories...)
Both use SystemTools::FilesDiffer to determine the difference status.
HTH,
David
On Mon, Mar 23, 2009 at 6:32 PM, James Bigler wrote:
> Could someone tell me if the logic behind compare_files and
> copy_if_different
Try:--test-command "testExe" "myarg1" "my arg 2"
(double quotes only necessary if there are spaces in the argument...)
Multiple args after "--test-command" are used to construct the proper
command line, not just the following arg...
On Mon, Mar 23, 2009 at 11:51 PM, Alastair Rankine
wrote:
> H
Specifying the lib4 dependency in the exe? But what about dependencies
order in the link line? In my example, lib4-A or lib4-B must appear
after lib3, if I want lib4 symbols required by lib3 to be added. In your
solution, lib4 might as well be added by cmake just after lib1 and
before lib3, which w
On 24. Mar, 2009, at 12:30, Alexandre Feblot wrote:
Dependency graph example: "->" means "depends on"
exe1-A -> lib1 -> lib3 -> lib4-A -> lib5 -> lib7
exe1-B -> lib1 -> lib3 -> lib4-B -> lib6 -> lib8
exe2-A -> lib2 -> lib3 -> lib4-A -> lib5 -> lib7
exe2-B -> lib2 -> lib3 -> lib4-B -> lib6
Just curious, what would be the inconvenience of using an if statement
around target_link_libraries to link against one or another target?
On Tue, Mar 24, 2009 at 12:30 PM, Alexandre Feblot <
alexandre.feb...@thomsonreuters.com> wrote:
> Hi,
>
>
>
> I'm facing an issue while trying to port my c
I think you don't need a new feature, you just have to use IF-ELSE mechanism
and then TARGET_LINK_LIBRARIES(target ${RESULT_OF_IF_ELSE})
Denis
> * lib3 CMakeLists.txt:
>
> add_library(lib3 some source)
> target_link_libraries(lib3,
> SELECTOR A_OR_B A lib4-A
> SELECTOR A_OR_B B lib4-B
Hi,
I'm facing an issue while trying to port my current build system to
cmake, and it seems there is no way to solve it currently. At least,
nobody in the mailing list found one. The only suggestion was to totally
recode the dependency mechanism with macros instead of relying on the
Cmake stand
Dear CMake Community,
I have an external executable which requires a library, which is not in
LD_LIBRARY_PATH.
If I manually set ENV{LD_LIBRARY_PATH} and then execute a command, it works.
But the problem is that the executable is inside ADD_CUSTOM_COMMAND and even if
I set environment variabl
Hi all,
when trying to build the source in this directory:
http://svn.berlios.de/svnroot/repos/fc-solve/trunk/fc-solve/source/
using CMake-2.6.3/CPack/NSIS and make package on Win32, the package is built
successfully, but the installed says "CMake . Setup" as the title and "Welcome
to CMake .
Clemens Arth wrote:
Hi,
I got a rather simple question. To add some special optimization flags
to a custom build for one of our projects, I followed the guide to add
a custom build type to my project using the example found here:
http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_extend_the_build
On Mon, 2009-03-23 at 11:25 -0500, Robert Dailey wrote:
> On Fri, Mar 20, 2009 at 9:33 AM, Marcel Loose wrote:
> Hi Robert,
>
> I am planning to use (but haven't implemented and tried yet):
>
> - add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND})
>
I would like to use precompilation directive such NO_OPENGL
Is there a way to use it with this command line ?
cmake -DCMAKE_BUILD_TYPE=Debug
or must i use something like:
cmake -DCMAKE_BUILD_TYPE=Debug -DWITH_OPENGL=0
with an if statement:
if(NOT WITH_OPENGL)
ADD_DEFINITIONS(-DNO_OPENGL)
endif
Christian Ehrlicher wrote:
Von: Nadir SOUALEM
In my CMakeLists.txt, i use such things like:
FIND_LIBRARY(LIB_UMFPACK LIB_UMFPACK
/opt/UMFPACK5.0.3/build/linux_eclipse/LIB_UMFPACK/${CMAKE_BUILD_TYPE})
So when i run:
cmake -DCMAKE_BUILD_TYPE=Debug
in my CMakeCache.txt, i find
//Path to a libr
58 matches
Mail list logo
