Hi Vincenzo,
it looks like CMake regards your gcc compiler as being similar
to the MS Visual C/C++ compiler, as the options it gets are
typical for that compiler.
Could you check that gcc is the first compiler in the path?
...
Oh! Can you try running CMake with the option -G MinGW Makefiles,
If you are using prebuilt Qt binaries from Nokia there are two flavors, 1
built with mingw and the other built with VS 2008. Try the one built with VS
2008.
http://qt.nokia.com/downloads/windows-cpp-vs2008
On Wed, Mar 17, 2010 at 10:57 PM, Mike Jackson
mike.jack...@bluequartz.netwrote:
Did you
Hi all,
I ran into a problem with FindBoost where it fails to find the correct
version of a component library. The cause is pretty clear to me.
There's a system-wide (rather old) version of Boost installed and
there's my latest-greatest version of Boost. The FindBoost macro
searches for a
Can CMake/CTest handle testing distributed applications? For example, I've got
a Socket based server and client. I want to test various combinations of
server and client on the same machine, on distributed homogeneous machines (all
win or all Linux), and on distributed heterogeneous machines
I thought there was now an option the boost build system to NOT add
all the very specific naming of each library which is now the
default. There is a way to turn that back on. You will have to search
through the boost-build docs for that info.
On Mar 18, 2010, at 7:47 AM, Marcel Loose wrote:
I ran into a problem with FindBoost where it fails to find the correct
version of a component library. The cause is pretty clear to me.
This isn't an answer to your question, but have you tried the CMake version of
boost? I have found it much
This is done with ParaView by creating a test driver that knows how to
start the distributed application and wait for it to do its thing and
give the results to ctest.
Clint
On 03/18/2010 07:53 AM, Caron, Michael C. (US SSA) wrote:
Can CMake/CTest handle testing distributed applications?
Hi all,
I want to compile 32bit app in 64 bit windows 7.
I can compile with vs2008 but
when i try to configures for compile with cmake it gives. i use cmake 2.8
How can i solve that error ?
ERROR
The C compiler
Ugh. This is a *horrible* bug. And it looks like it's my fault... Sometimes
it only takes 18 months or so for these things to come to light. :-(
To get it to work, put FOLLOW_SYMLINKS *before* the RELATIVE keyword. The
implementation has a bug that treats FOLLOW_SYMLINKS as one of the globbing
Zitat von Ramazan Girgin ramazangir...@gmail.com:
I want to compile 32bit app in 64 bit windows 7.
Did you install the SDK?
HS
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
i have installed sdk.
ı can compile 32 bit application with visual studio 2008
On Thu, Mar 18, 2010 at 5:52 PM, Bill Hoffman bill.hoff...@kitware.comwrote:
Ramazan Girgin wrote:
Hi all,
I want to compile 32bit app in 64 bit windows 7.
I can compile with vs2008 but
when i try to configures
Hello,
You were right the fortran compiler was the first one on the path. Now
I put MinGw on the first position. The behaviour is somehow changed
but I still get errors.
When I type C:\plplot-5.9.5 cmake -G MinGW Makefiles on CMD
here is what I get:
I'm just starting to try and get CMake and SWIG to play nice together. All
I've done is add:
FIND_PACKAGE(SWIG REQUIRED)
to an existing CMakeLists.txt file that has worked before now. With only this
addition I get:
CMake Error at C:/Program Files/CMake
If you open the file C:/Program Files/CMake
2.8/share/cmake-2.8/Modules/FindSWIG.cmake and read through it, you will
see exactly where CMake is looking for SWIG.
It uses:
FIND_PROGRAM(SWIG_EXECUTABLE swig)
(which means it's only looking in the PATH...)
So you can either:
set(SWIG_EXECUTABLE
I am working on some CMake Code where I would like some libraries to
be placed inside a plugins folder in the following path:
${PROJECT_BINARY_DIR}/bin/plugins.
Works fine with Makefiles. Problem is on Visual Studio. I get my
executables in ${PROJECT_BINARY_DIR}/bin/Debug/myexe.exe
but the
CMAKE_CFG_INTDIR is what you want. It expands to a variable reference which
gets expanded at build-time by the respective multi-config IDE (i.e. Debug,
Release, etc.)
Michael
On 18. Mar, 2010, at 21:39 , Mike Jackson wrote:
I am working on some CMake Code where I would like some libraries to
If ${PROJECT_BINARY_DIR}/bin/plugins is used in an add_custom_command
context, you can use ${PROJECT_BINARY_DIR}/bin/${CMAKE_CFG_INTDIR}/plugins
instead to get what you want. If it's something else besides
add_custom_command, then elaborate with some more details...
${CMAKE_CFG_INTDIR} evaluates
Guys, thanks for the suggestions. I'll give them a try in the morning.
Hacking on ParaView currently...
_
Mike Jackson mike.jack...@bluequartz.net
On Thu, Mar 18, 2010 at 5:09 PM, David Cole david.c...@kitware.com wrote:
This page:
http://www.cmake.org/Wiki/CPack:Generator_Information
redirects to a page called:
VTK/Tutorials/PythonEnvironmentSetup
which AFAICT has nothing at all to do with CPack generators. The topics
are so different that I can't even guess what someone was trying to
accomplish by enacting
On Thursday 18 March 2010, Tyler Roscoe wrote:
This page:
http://www.cmake.org/Wiki/CPack:Generator_Information
redirects to a page called:
VTK/Tutorials/PythonEnvironmentSetup
which AFAICT has nothing at all to do with CPack generators. The topics
are so different that I can't even guess
I have been hanging out for 2.8.1 because I needed this feature to
provide seamless integration with our current build system. On testing
yesterday no dice I couldn't decompress a bzip2 archive. I even looked
through the source code but couldn't find it.
I feel I have missed the boat on this
Hey all,
I have a large project whose source files start as files with an alternate
extension (.bc). Those files are mostly generic C files that have some C++
like features that are preprocessed into vanilla C files using a custom C
pre-processor. My project uses an add_custom_command() call
Hugh Sorby wrote:
I have been hanging out for 2.8.1 because I needed this feature to
provide seamless integration with our current build system. On testing
yesterday no dice I couldn't decompress a bzip2 archive. I even looked
through the source code but couldn't find it.
It would be nice
Hugh Sorby wrote:
I have been hanging out for 2.8.1 because I needed this feature to
provide seamless integration with our current build system. On testing
yesterday no dice I couldn't decompress a bzip2 archive. I even looked
through the source code but couldn't find it.
I feel I have missed
Steven Wilson wrote:
Hey all,
I have a large project whose source files start as files with an
alternate extension (.bc). Those files are mostly generic C files that
have some C++ like features that are preprocessed into vanilla C files
using a custom C pre-processor. My project uses an
That's an interesting idea. Would this step attach the dependencies to the
.c file or the .bc file?
On Thu, Mar 18, 2010 at 7:49 PM, Bill Hoffman bill.hoff...@kitware.comwrote:
I have a hack of an idea that might work
If you could changed your bc - c generator to put in the #include
26 matches
Mail list logo
