I help contribute to Stellarium, which is a cross-platfor planetarium
app, written using Qt. It uses cmake for the build system; it just doesn't do
it well. I think the files are much more complex than they need to be, and as
usual, the Mac stuff doesn't really work. I've looked at th
Hi Everyone,
I'm currently having a problem with generated headers in a Visual Studio
2005/2008 project generated with CMake.
Visual Studio is regenerating the headers even when nothing has changed.
The project requires headers generated by a tool called 'tracewpp',
which is part of th
Guillaume Duhamel wrote:
> file(MAKE_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/c68k)
> execute_process(COMMAND cmake ${CMAKE_CURRENT_SOURCE_DIR}/c68k
> WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/c68k)
> add_custom_target(c68kinc COMMAND cmake --build
> ${CMAKE_CURRENT_BINARY_DIR}/c68k)
>
> It d
Update: currently crying uncle ... and switching to ExternalProject_Add.
CMake and the third party libs were simply not designed for this.
Question on ExternalProject_Add above:
ExternalProject_Add(
DOWNLOAD_COMMAND ""
CMAKE_ARGS
-DMYPROJ_UBERBUILD:BOOL=OFF
SOURCE_DIR ${CMAKE_CURRENT_SO
> (3)
> Use execute_process() to run the CMake command line tool and configure the
> host-only project during the configuration step of the main project. This
> will make the results of the export() command from the subproject available
> for loading by the main project. Then add a custom target
Kitware launched
its first developer
blog today
with contributions from Company technical and business leaders.
Following the
blog is a great way to obtain early access to evolving technology and
provide
commentary feedback. Blog postings may be followed by topic area, or on
an
individual basis
On 28. Jan, 2010, at 19:01 , Anton Deguet wrote:
> Hello,
>
> Besides digging in the existing UseVTK, UseITK, UseOpenIGTLing, ... is there
> a short description of the philosophy and basic commands to use? Any
> pointer is welcome. This would be for a project with multiple external
> depe
Anton Deguet wrote:
> Hello,
>
> Besides digging in the existing UseVTK, UseITK, UseOpenIGTLing, ...
> is there a short description of the philosophy and basic commands to
> use? Any pointer is welcome. This would be for a project with
> multiple external dependencies, i.e. libxml, openCV, Pyth
On Thursday 28 January 2010, Hendrik Sattler wrote:
> Zitat von Yegor Yefremov :
> > are these two statements not doubled?
> >
> > +#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEL__)
> > +# define ABI_ID "ELF ARM"
> > +#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEL__)
>
Hello,
Besides digging in the existing UseVTK, UseITK, UseOpenIGTLing, ... is there a
short description of the philosophy and basic commands to use? Any pointer
is welcome. This would be for a project with multiple external dependencies,
i.e. libxml, openCV, Python, numpy, ...
Thanks,
Ant
Hi Brad,
I will try the new patch tomorrow.
I tried printing it as an ordinary variable or constant, but that did
not work: variable names are not allowed to start with an underscore.
Regards,
Arjen
On 2010-01-28 17:18, Brad King wrote:
Arjen Markus wrote:
Perhaps this means that _DF_VERSIO
Arjen Markus wrote:
>> Perhaps this means that _DF_VERSION_ is available only as a Fortran
>> language symbol.
>
> It would look that way, but what use would it have then?
Perhaps it can be used in regular (runtime) IF tests? Of course other
compilers won't define it, so it's useful only in vend
The wiki page that lists module maintainers is found here:
http://www.itk.org/Wiki/CMake:Module_Maintainers
For FindSubversion.cmake, Tristan Carel is listed as the maintainer.
Perhaps patches for FindSubversion.cmake would more appropriately be added
to patch files attached to a bug report / fea
Zitat von Yegor Yefremov :
are these two statements not doubled?
+#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEL__)
+# define ABI_ID "ELF ARM"
+#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEL__)
+# define ABI_ID "ELF ARM"
One of them should be __ARMEB__ instead of
Hi Brad,
Perhaps this means that _DF_VERSION_ is available only as a Fortran
language symbol.
It would look that way, but what use would it have then?
So we conclude that the compiler provides no way to identify itself
using the preprocessor. This will need non-trivial work in CMake to
re
Arjen Markus wrote:
> the program is compiled and linked without a problem. But
> it writes:
> INFO:compiler[]
> INFO:platform[Windows]
>
> I have examined the preprocessed source code and re-read the
> online documentation: all the macros defined in the table I
> looked at are available to the pr
Hi Brad,
the program is compiled and linked without a problem. But
it writes:
INFO:compiler[]
INFO:platform[Windows]
I have examined the preprocessed source code and re-read the
online documentation: all the macros defined in the table I
looked at are available to the preprocessor, except, indee
On Thu, Jan 28, 2010 at 3:28 AM, Marcel Loose wrote:
> Hi all,
>
> For my project, I'm working on automatic 'svn update' of (parts of) my
> source tree, prior to building. I was wondering whether someone else
> might be interested in that kind of functionality. If so, maybe it could
> be added as
Arjen Markus wrote:
> it does not work - I get a message that the Fortran compiler
> identification is unknown. Does CMake run the compiler with the
> /fpp option? If not, then that is the cause (without there is
> no particular macro defined)
In CMakeDetermineFortranCompiler.cmake we list the pos
Hi Brad,
it does not work - I get a message that the Fortran compiler
identification is unknown. Does CMake run the compiler with the
/fpp option? If not, then that is the cause (without there is
no particular macro defined)
Regards,
Arjen
On 2010-01-28 14:27, Brad King wrote:
Arjen Markus wr
O.K. Here are some lines of my CMakeLists.txt:
set (CMAKE_C_COMPILER arm-linux-gcc)
set (CMAKE_STRIP arm-linux-strip)
>
> Oh, if you do that in CMakeLists.txt this is quite late. You should use a
> toolchain file as described in the wiki.
I'll try it later.
message (ST
Arjen Markus wrote:
> If you turn on the preprocessor option, then a number of macros
> are defined, the most useful being:
>
> _DF_VERSION_=660 and _VF_VERSION_==660
Please try out the patch below (applies to CMake from CVS HEAD).
With it, CMake should recognize the Compaq compiler out of the bo
Hi Brad,
see my answers below
On 2010-01-27 19:18, Brad King wrote:
Brad King wrote:
As a first step, we can add Compaq to CMakeFortranCompilerId.F.in.
What is the preprocessor macro that identifies it?
I'd like to teach CMake upstream to recognize the Compaq Fortran
compiler even if we do n
On 28. Jan, 2010, at 11:19 , Micha Renner wrote:
> There is a library, which has the suffix d, if it is compiled in
> Debug-Mode
>
> ADD_LIBRARY(${_targetname} SHARED ${_src} ${_imIncludeFiles})
> SET_TARGET_PROPERTIES(${_targetname} PROPERTIES DEBUG_OUTPUT_NAME
> ${_targetname}d)
> INSTALL(TARG
There is a library, which has the suffix d, if it is compiled in
Debug-Mode
ADD_LIBRARY(${_targetname} SHARED ${_src} ${_imIncludeFiles})
SET_TARGET_PROPERTIES(${_targetname} PROPERTIES DEBUG_OUTPUT_NAME
${_targetname}d)
INSTALL(TARGETS ${_targetname} EXPORT SLibName
RUNTIME DESTINATION d
Dude, you really are in some need of RTFM! E.g. here
http://lmgtfy.com/?q=cmake+documentation
Flaming, swearing and strong language won't get you much help here!
find_library(a ...) creates a variable in the cache called "a". Next time you
call find_library(a ...) it just won't do anything, bec
It would be best if you explained your use case in more detail. Anyway, this
might be a helpful read
http://cmake.org/cmake/help/cmake-2-8-docs.html#module:FindGTK2
Best,
Adolfo.
On Thu, Jan 28, 2010 at 10:30 AM, jojelino wrote:
> i want to include gtk dependency libraries with gtk itself. b
i want to include gtk dependency libraries with gtk itself. but
followings was error-prone.
set(a "")
find_library(a NAMES gdk_pixbuf-2.0)
set(GTKLIBS ${GTKLIBS} ${a})
set(a "")
find_library(a NAMES gdk-win32-2.0)
set(GTKLIBS ${GTKLIBS} ${a})
set(a "")
find_library(a NAMES gtk-win32-2.0)
set(GTKL
Why not write your own Makefile and use make, then YOU can do all the
dependency stuff yourself. Then you don't have to use CMake, which you
appear to dislike so much.
You apparently don't appreciate all the hard work that CMake does for
you, and seem not willing to put effort into learning this.
There's a bug in the current FindSubversion.cmake, which causes it to
ignore the REQUIRED option, when option QUIET is not given. The
following patch solves this. IMHO, it would be even better to use FPHSA
for this.
Furthermore, I'm not sure whether it's desirable to conditionally define
macros. T
I DONT WANT 'CMAKE' DO DEPENDENCY STUFF. because it sucks very much.
instead of letting cmake do MORON stuff to piss me off, i want to give
it wise and toleable solution by giving LDFLAGS stuff by hand after
source files (surely it is external library)
such as gcc -shared -o out.exe a.o b.o c.o.
Hi all,
For my project, I'm working on automatic 'svn update' of (parts of) my
source tree, prior to building. I was wondering whether someone else
might be interested in that kind of functionality. If so, maybe it could
be added as a macro to FindSubversion?
Best regards,
Marcel Loose.
___
Hi,
I need to use ${CMAKE_CXX_FLAGS} variable, but it contains unneeded char: "\".
I tried to remove it:
STRING(REPLACE '\\' " " FLAGS ${CMAKE_CXX_FLAGS})
but it didn't work. How can I do this?
Br.
Marek
___
Powered by www.kitware.com
Visit other Kitwa
33 matches
Mail list logo
