Just to jump in here. On OS X I also noticed that X11 libs are linked into
VTK 502 even though I am compiling with Carbon.. Is that correct? Doesn't
seem so.
Mike Jackson
On 10/20/06 3:20 PM, "Patrick D. Emond" <[EMAIL PROTECTED]> wrote:
> For those people who, like me, are primarily interested
For those people who, like me, are primarily interested in getting VTK5
built under cygwin the simplest solution seems to be to make sure that
your cygwin install has no X11 libraries installed. I completely
reinstalled cygwin making sure to not include any X11 packages and the
VTK install wen
Hi,
While trying to convert ethereal build system from autotool to cmake, I came
across a problem which may be already solved.
There are three possible prefix for defining 64bit format: "%ll", "%L"
and "%q". For instance, printing a signed decimal number could
be "%lld", "%Ld" or "%qd".
If someo
Another 'bug' is that you can edit the CMAKE_CXX_COMPILER field in
ccmake, but when you run 'c', the field is overwritten again. All
very annoying. Maybe a SET( LOCKED ...) flag could be added such that
fields are not user editable.
You could enter a bug in the bugtracker if it's not there a
> Hello all,
> I don't know if it's my system or not, but my QT_INCLUDES, don't
> include the path to QtUITools when i use the FindQt4.cmake
> Is it a way to do that properly ?
>
> thanks
> Xavier
>
FIND_PACKAGE(Qt4)
SET(QT_USE_QTUITOOLS TRUE)
INCLUDE(${QT_USE_FILE})
And if CMake didn't find th
Peter Soetens wrote:
Quoting Brad King <[EMAIL PROTECTED]>:
Any time you change the compiler you have to wipe out the build tree and
start from scratch. Try running CMake like this instead:
$ rm -rf build; mkdir build; cd build
$ CC=gcc CXX=g++ cmake ..
I had read this comment before, but
What’s the best approach to disabling optimizations
for a particular project? We still want to use release settings just with
optimizations turned off and then just for that single project.
Thanks
Reggie
___
CMake mailing list
CM
Quoting Brad King <[EMAIL PROTECTED]>:
Any time you change the compiler you have to wipe out the build tree and
start from scratch. Try running CMake like this instead:
$ rm -rf build; mkdir build; cd build
$ CC=gcc CXX=g++ cmake ..
I had read this comment before, but I couldn't believe it
By adding the INSTALL command it works fine, both for win32 and LinuxPerhaps it's an idea to add the "INSTALL" requirement to the CPack wiki page, to avoid questions by "dummies" like me. (I wrongly assumed that all targets/libraries/... that were in the build directory would end up in the install
Alexander Neundorf wrote:
> #16: the line is parsed and a vector containing the arguments is created,
> which is handed the cmSetCommand. This turns the vector into a string.
> #17: the line is parsed, ${srcs} is expanded to the string in srcs and parsed
> again into a vector.
> #08: it evaluates
Peter Soetens wrote:
> The following happened to me (cmake version 2.4-patch 2) :
>
> $ mkdir build
> $ cd build
> $ cmake .. -DCMAKE_CXX_COMPILER=g++ -DCMAKE_CC_COMPILER=gcc
> -- Check for working C compiler: gcc
> -- Check for working C compiler: gcc -- works
> -- Check size of void*
> -- Check
Peter Soetens wrote:
> Quoting Brad King <[EMAIL PROTECTED]>:
>>
>> If BUILD_X is on and SOME_OPTION is set by the user, then BUILD_X is
>> turned off, and then back on the user may expect SOME_OPTION to have
>> retained its value. You can convert it to an INTERNAL cache entry so
>> that it does n
Hello all,
I don't know if it's my system or not, but my QT_INCLUDES, don't
include the path to QtUITools when i use the FindQt4.cmake
Is it a way to do that properly ?
thanks
Xavier
begin:vcard
fn;quoted-printable:Xavier Larrod=C3=A9
n;quoted-printable:Larrod=C3=A9;Xavier
org:IRISA ;E119 Ora
The following happened to me (cmake version 2.4-patch 2) :
$ mkdir build
$ cd build
$ cmake .. -DCMAKE_CXX_COMPILER=g++ -DCMAKE_CC_COMPILER=gcc
-- Check for working C compiler: gcc
-- Check for working C compiler: gcc -- works
-- Check size of void*
-- Check size of void* - done
-- Check for worki
There are two options.
(1) Create a "*.def" file and add it as a source file to your target:
ADD_LIBRARY(... MODULE ... MyDefFile.def)
(2) In your source code, use __declspec(dllexport) to decorate the
function name... You can see examples of this in this VTK header file:
http://public.kitware.c
Well if you don't have any INSTALL commands, then there is nothing to
install, right?
CPack is simply a tool that transforms your CMakeLists INSTALL
commands into a packaged setup program... So, yes, you do need INSTALL
commands.
You have to be able to run "make install" and end up with a non-em
Okay, i have boiled it down to the fact that i need to define from cmake, a "Module definition file"
It seems to be all this needs to be done.
When i set i manually, it works perfectly, but can anyone help me with how i can set a "Module definition file" from CMAKE ? (I use VS 8.0)
2006/10/20, Pre
Hello,I would like to use CPack to make an install package with NSIS for win32.I downloaded the hello example (http://www.cmake.org/HTML/Examples.html) added "INCLUDE(CPack)"
to the CMakeLists.txt (http://www.cmake.org/Wiki/CMake:Packaging_With_CPack) and tried to run "make package"However an error
Hello. I want to use CMAKE to create mex file for matlab. But i seem to be doing something wrong.
I need to specify output as DLL. which i can use ADD_LIBRARY(... MODULE ...) for.
The problem is that apparently i also need to make sure mexFunction is an exported symbol in the dll.
The mexFunct
Quoting Brad King <[EMAIL PROTECTED]>:
If BUILD_X is on and SOME_OPTION is set by the user, then BUILD_X is
turned off, and then back on the user may expect SOME_OPTION to have
retained its value. You can convert it to an INTERNAL cache entry so
that it does not show up in the GUI when it is no
20 matches
Mail list logo
