> I've been using QNX and cmake together for a few weeks, and I've yet to
> have the problem that you indicated. In my QNX toolchain file I use the
> line:
>
> SET( CMAKE_AR
> "${QNX_HOST}/usr/bin/ntox86-ar${HOST_EXECUTABLE_SUFFIX}" CACHE PATH "QNX
ar Program" )
>
> -kito
Thanks for the help, tha
It's been my understanding that calling message() without STATUS, WARNING,
or ERROR was a STATUS by default. Considering that when I use both WARNING
and ERROR the output looks different. Dialogs will appear and such. Are
message() and message( STATUS ) not identical? If not, what are the
differenc
Would it be possible to do what compilers do: prepend status lines
with "STATUS", warning with "WARNING" and error with "ERROR". That
makes it easier to grep if needed and may help pull attention to each
type of output.
Just thinking out loud...
---
Mike Jackson www.bluequ
On Wed, Mar 25, 2009 at 9:59 PM, Clinton Stimpson wrote:
>
> The intent I get from the documentation is that its a message that is meant
> to say something important. It pops up in the CMakeSetup, shows up in the
> error section of ccmake, and stdout of cmake.
>
> Maybe cmake-gui should show it b
2009/3/25 Stephen Collyer :
> I'm building a Win32 zip package from an out-of-source build in a directory
> c:\mdpqt_HEAD\build.
>
> When the zip file is created, it has the structure:
>
> MDP-1.0.0-win32\mdpqt_HEAD\bin (and others)
>
> Can someone tell me:
>
> a) where the "-win32" is coming from
The intent I get from the documentation is that its a message that is
meant to say something important. It pops up in the CMakeSetup, shows
up in the error section of ccmake, and stdout of cmake.
Maybe cmake-gui should show it bold or something instead of red, which I
also think of as an er
The rest of the text in that box that is black is printed via
message(STATUS...). If you don't want your messages to show up red you can
use message(STATUS "Hello World").
The message() command without STATUS is supposed to be a warning, I think.
On Wed, Mar 25, 2009 at 7:59 PM, Robert Dailey w
Thank's Gregory, this is an even better answer than I was looking for lol.
On Wed, Mar 25, 2009 at 6:17 PM, Gregory Peele ARA/CFD wrote:
> Robert,
>
>
>
> Looking at your example, you might want to try out FIND_PACKAGE(Doxygen).
>
>
>
> In general, my understanding is that it’s more common in CM
Hi,
Ever since CMake 2.6.3, the CMake-gui application on Windows has been
displaying output from the message() function in red, even if it isn't an
error. For example, if I do this:
message( "Hello World" )
The text "Hello World" will show up in RED. Is this by design? I would
prefer it show up a
Would this work?
set( ENV{PATH} "ENV{PATH};${CMAKE_SOURCE_DIR}/tools/doxygen" )
On Wed, Mar 25, 2009 at 5:30 PM, Robert Dailey wrote:
> Is there a way that I can temporarily add an executable search path to PATH
> for the Linux and Windows platforms? I temporarily wish to allow CMake to
Is there a way that I can temporarily add an executable search path to PATH
for the Linux and Windows platforms? I temporarily wish to allow CMake to
find certain third party command line applications so it may execute them.
I'd be calling CMake's execute_process() function to do this. But this by
OK, I'm not sure if I can provide a reproducing case, because I'm
dealing with a large system that generates code while dynamically
maintaining dependencies.
I did, however, discover something when trying to narrow down the problem.
If I put c:\path\to\source in "Where is the source code" box in
I believe that VS is rewriting these files because of the Scc source
control stuff. When I turn that feature off, VS stops rewriting the
project files. I don't know yet exactly why VS is rewriting the
files. It could be that it wants to update the SccLocalPath attribute
to a relative path.
I be
On Wednesday 25 March 2009, Carlson Daniel wrote:
> No i do not have a toolchain file, but you are right, perhaps I need one...
>
> I am compiling with the DIAB compiler from Windriver and my target system
> is a power PC from Freescale, MPC5566. I have used the
> CMakeForceCompiler-module to chang
No i do not have a toolchain file, but you are right, perhaps I need one...
I am compiling with the DIAB compiler from Windriver and my target system is
a power PC from Freescale, MPC5566. I have used the
CMakeForceCompiler-module to change compiler from gcc to DIAB...
Regards
Daniel Carlson
200
On Wednesday 25 March 2009, Carlson Daniel wrote:
> Thank you Alexander!
>
> Although this was not the answers I wanted to hear...
>
> 1: I believe it is quite stupid to edit the platform files, right? If I do
> that I have to remember to edit the platform files in the future when I
> e.g. update t
On Wednesday 25 March 2009, Denis Scherbakov wrote:
> Alex,
>
> In CMake I can check for
>
> WIN32
> MINGW
> CYGWIN
> MSVC
> UNIX
> APPLE
>
> I don't know, how to distinguish different unix variations.
You can test the CMAKE_SYSTEM variable.
Alex
Thank you Alexander!
Although this was not the answers I wanted to hear...
1: I believe it is quite stupid to edit the platform files, right? If I do
that I have to remember to edit the platform files in the future when I e.g.
update the CMake environment to a newer version... I will have a look
I'm building a Win32 zip package from an out-of-source build in a directory
c:\mdpqt_HEAD\build.
When the zip file is created, it has the structure:
MDP-1.0.0-win32\mdpqt_HEAD\bin (and others)
Can someone tell me:
a) where the "-win32" is coming from, and can I remove it ?
b) why the generator
Alex,
In CMake I can check for
WIN32
MINGW
CYGWIN
MSVC
UNIX
APPLE
I don't know, how to distinguish different unix variations.
Denis
> Well, if you care for LD_LIBRARY_PATH, DYLD_LIBRARY_PATH
> and PATH you have
> taken care of most platforms.
> Which other platforms do you need ?
On Wednesday 25 March 2009, Carlson Daniel wrote:
> Best CMake users,
>
> I am using CMake in some smaller embedded projects which we have converted
> from traditional make scripts. After all c-files has been compiled we want
> to perform some tests on the generated object-files. The tests we are
>
On Wednesday 25 March 2009, Daniele Galdi wrote:
> Hi all,
>
> in my project during the compilation procedure a library defined in
> another CMakeList.txt (previously processed by cmake),
> is linked without problems, but when i try to define an
> install(targets) macro, the build process fails wit
On Wednesday 25 March 2009, Denis Scherbakov wrote:
> Unfortunatelly, the idea with a shell script is not portable.
>
> Here you can see all possible LD_LIBRARY_PATH combinations:
> http://www.vtk.org/Wiki/CMake_Platform_Dependent_Issues
Well, if you care for LD_LIBRARY_PATH, DYLD_LIBRARY_PATH and
Marcel Loose schrieb:
> On Wed, 2009-03-25 at 15:16 +0100, Eric Noulard wrote:
>> 2009/3/25 Marcel Loose :
>>> On Fri, 2009-03-20 at 16:34 +0100, Eric Noulard wrote:
2009/3/20 Marcel Loose :
> Perfect!
Ok fine.
> I now use add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND
Did you try EXECUTE_PROCESS and ADD_CUSTOM_COMMAND?
Denis
--- On Wed, 3/25/09, ankit jain wrote:
> From: ankit jain
> Subject: [CMake] Argument passing to shell script through cmake
> To: cmake@cmake.org
> Date: Wednesday, March 25, 2009, 5:54 AM
> Hi all,
>
> I want to run one shell script
Steven Van Ingelgem wrote:
What I did (and solved the issue) is:
file(READ "zconf.in.h" ZCONF_H)
STRING(REPLACE "HAVE_STD_HEADERS_H" ${HAVE_STD_HEADERS_H} "${ZCONF_H}")
file(WRITE "zconf.test" "${ZCONF_H}")
Especially the quotes around the variable are important as otherwise
CMake think it's an
What I did (and solved the issue) is:
file(READ "zconf.in.h" ZCONF_H)
STRING(REPLACE "HAVE_STD_HEADERS_H" ${HAVE_STD_HEADERS_H} "${ZCONF_H}")
file(WRITE "zconf.test" "${ZCONF_H}")
Especially the quotes around the variable are important as otherwise CMake
think it's an array and not a string... I t
Brad,
On Wednesday 25 March 2009 07:38:41 Brad King wrote:
> Thanks for the example. There were two bugs canceling each other out for
> this use case. One was fixed in 2.6.3 which exposed the other. I've
> committed a fix and a test (the full commit log explains everything).
>
> I'll schedule t
On Mar 25, 2009, at 11:06 AM, Marcel Loose wrote:
On Wed, 2009-03-25 at 15:16 +0100, Eric Noulard wrote:
2009/3/25 Marcel Loose :
On Fri, 2009-03-20 at 16:34 +0100, Eric Noulard wrote:
2009/3/20 Marcel Loose :
Perfect!
Ok fine.
I now use add_custom_target(check COMMAND $
{CMAKE_CTEST_C
On Wed, 2009-03-25 at 15:16 +0100, Eric Noulard wrote:
> 2009/3/25 Marcel Loose :
> > On Fri, 2009-03-20 at 16:34 +0100, Eric Noulard wrote:
> >> 2009/3/20 Marcel Loose :
> >> > Perfect!
> >>
> >> Ok fine.
> >>
> >> >
> >> > I now use add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND}) and
> >>
KSpam wrote:
I attached a small example with the problem. The problem is actually a bit
more complicated than my original explanation. I have a macro in my
top-level CMakeLists.txt file:
macro (getScriptDir _scriptDir)
get_filename_component(${_scriptDir} ${CMAKE_CURRENT_LIST_FILE} PATH)
When I've seen this sort of behavior, I can usually trace it back to a
variable set in a script or passed in on the command line...
CMake tries to preserve any case information that it is given.
If you can give an example that reproduces this behavior, but is not
attributable to a user typing "c:
";" is the CMake list element separator character. The ";" are still there
in the variable, you probably just can't see them with your processing code
that comes after reading in the file...
You can replace semi-colons like this with escaped semi-colons:
STRING(REGEX REPLACE ";" ";" ZCONF_H
Create an account at the wiki site.
Create a new page with your "tutorial"
Create a link on the main page to your new tutorial.
---
Mike Jackson www.bluequartz.net
On Mar 25, 2009, at 10:15 AM, Marcel Loose wrote:
On Fri, 2009-03-20 at 16:34 +0100, Eric Noulard wrote:
2009/3
2009/3/25 Marcel Loose :
> On Fri, 2009-03-20 at 16:34 +0100, Eric Noulard wrote:
>> 2009/3/20 Marcel Loose :
>> > Perfect!
>>
>> Ok fine.
>>
>> >
>> > I now use add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND}) and
>> > that indeed solves the parallel build issue.
>> > And yes, I have MAKEFL
2009/3/24 Allen Gooch :
> 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:
It has been reported a
On Fri, 2009-03-20 at 16:34 +0100, Eric Noulard wrote:
> 2009/3/20 Marcel Loose :
> > Perfect!
>
> Ok fine.
>
> >
> > I now use add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND}) and
> > that indeed solves the parallel build issue.
> > And yes, I have MAKEFLAGS set to "-j4".
>
>
> Now that
On Wed, Mar 25, 2009 at 2:47 AM, Denis Scherbakov
wrote:
>
> Unfortunatelly, the idea with a shell script is not portable.
>
Sorry, I forgot to mention that I've been using this script on Linux
and MacOsX only.
[...]
--
Nicolas Desprès
___
Powered by
I don't have my windows machine fired up at the moment so I can not
check this out but that _should_ have really worked.
Seems like maybe a bug with cpack?
And yes, quoting _can_ be this difficult.. at least IMO.
---
Mike Jackson www.bluequartz.net
On Mar 25, 2009, at 8:37 A
Hi all,
I want to run one shell script which requires some arguments to pass in
cmakelists file.
Simply using install command to run it does not allow to pass arguments to
it.
How to do it
ankit
___
Powered by www.kitware.com
Visit other Kitware
Benne, Kyle wrote:
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 overridi
Best CMake users,
I am using CMake in some smaller embedded projects which we have converted
from traditional make scripts. After all c-files has been compiled we want
to perform some tests on the generated object-files. The tests we are
running demands that the object files are denoted myFile.o a
2009/3/25 Robert Haines
> I have seen that only including the directories where jars exist wil not
>> solve the puprose of using those jars. we have to either extract the files
>> from it or either include the directories where the file exists from which
>> jars have been made.
>>
>
> Have you a
On 25. Mar, 2009, at 10:28, ankit jain wrote:
2009/3/25 Michael Wild
On 25. Mar, 2009, at 9:33, ankit jain wrote:
2009/3/25 Michael Wild
[...]
What I usually do is this:
add_custom_command( OUTPUT ${TARDIR}/t1
COMMAND ${CMAKE_COMMAND} -E tar xvf ${TARDIR}/mytar.tar
WORKING_DIRECTO
SET(CMAKE_INSTALL_PREFIX "$ENV{ProgramFiles}\\${PROJECT_NAME}_${VERSION}")
or
SET(CMAKE_INSTALL_PREFIX "$ENV{ProgramFiles}/${PROJECT_NAME}_${VERSION}")
Strings in CMake are like C Strings. '\' is special so it needs to be
escaped with another '\'. You can also use the normal '/' and cmake
_shoul
I've got the following code in my top-level CMakeLists.txt file:
IF (WIN32)
SET(CMAKE_INSTALL_PREFIX
"$ENV{ProgramFiles}\${PROJECT_NAME}_${VERSION}")
SET(CPACK_GENERATOR "ZIP")
ELSE(WIN32)
SET(CMAKE_INSTALL_PREFIX "/opt/${PROJECT_NAME}_${VERSION}")
SET(CPACK_GENERATOR "RPM")
ENDIF(
I have seen that only including the directories where jars exist wil
not solve the puprose of using those jars. we have to either extract
the files from it or either include the directories where the file
exists from which jars have been made.
Have you actually tried including the jars them
Hi all,,
I have seen that only including the directories where jars exist wil not
solve the puprose of using those jars. we have to either extract the files
from it or either include the directories where the file exists from which
jars have been made.
If we give that path then what is the need o
2009/3/25 Michael Wild
>
> On 25. Mar, 2009, at 9:33, ankit jain wrote:
>
> 2009/3/25 Michael Wild
>>
>
> [...]
>
>
>>> What I usually do is this:
>>>
>>> add_custom_command( OUTPUT ${TARDIR}/t1
>>> COMMAND ${CMAKE_COMMAND} -E tar xvf ${TARDIR}/mytar.tar
>>> WORKING_DIRECTORY ${TARDIR}
>>> COMME
On 25. Mar, 2009, at 9:33, ankit jain wrote:
2009/3/25 Michael Wild
[...]
What I usually do is this:
add_custom_command( OUTPUT ${TARDIR}/t1
COMMAND ${CMAKE_COMMAND} -E tar xvf ${TARDIR}/mytar.tar
WORKING_DIRECTORY ${TARDIR}
COMMENT "Extracting ${TARDIR}/mytar.tar"
VERBATIM
)
add_custom
ould like to be able to specify this in the toolchain file as it is
my
understanding that this is what this file is intended for. Am I doing
something wrong here, or is this the expected behaviour of cmake?
Thanks, Ross
-- next part --
An HTML attachment was scrubbed...
URL:
<http:
Unfortunatelly, the idea with a shell script is not portable.
Here you can see all possible LD_LIBRARY_PATH combinations:
http://www.vtk.org/Wiki/CMake_Platform_Dependent_Issues
Denis
> >> I have an external executable which requires a
> library, which is not in
> >> LD_LIBRARY_PATH. If I manu
Hi Kyle,
-static-intel would force tor to static link the intel provided libs.
is clear that you have a silly combination of options.
On one hand you ask to static link the libs on the other hand the shared libs
flags are on.
As a note for the the intel modules files developers -i_dynamic is dep
2009/3/25 Michael Wild
>
> On 25. Mar, 2009, at 7:51, ankit jain wrote:
>
> 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(TAR
Hi all,
in my project during the compilation procedure a library defined in
another CMakeList.txt (previously processed by cmake),
is linked without problems, but when i try to define an
install(targets) macro, the build process fails with message.
install TARGETS given target "core" which
On 25. Mar, 2009, at 7:51, ankit jain wrote:
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 ${CM
56 matches
Mail list logo
