What I really want is a simple text substitution macro, of the form:
MACRO(SIMPLE_SCM_TO_C root)
${VALID_CHICKEN} ${Chicken_SOURCE_DIR}/${root}.scm -output-file
${Chicken_BINARY_DIR}/${root}.c ${CHICKEN_FLAGS})
ENDMACRO(SIMPLE_SCM_TO_C)
and then put this inside of a custom command so I don't
Hi,
I have a problem using cmake in combination with QT. QT_WRAP_CPP works
perfectly.
But when I use QT_WRAP_UI no .h and .cxx files are generated. Is there
anything I forgot regarding QT_WRAP_UI?
--snip--
SET(IMEDGINE_UI_SOURCELIST gui/ui/TestDialog.
Brandon J. Van Every wrote:
If there's no way to perform a simple text substitution on a custom
build rule's COMMAND line, then that's really really irritating.
I still would like a text substitution macro, but I did find a
semi-elegant way around being stuck with DEPENDS in ADD_CUSTOM_COMMA
At 06:37 AM 5/19/2006, Christian Koerner wrote:
>Hi,
>
>I have a problem using cmake in combination with QT. QT_WRAP_CPP works
>perfectly.
>
>But when I use QT_WRAP_UI no .h and .cxx files are generated. Is there
>anything I forgot regarding QT_WRAP_UI?
>
>--snip
Since this issue has come up in several posts (the chicken problem,
and the qt header file problem), I thought I would try to explain
how generated files work in CMake 2.4.
In CMake 2.4, you should not have to specify OBJECT_DEPENDS, or even set
PROPERTIES GENERATED true. You should just make sur
Brandon J. Van Every wrote:
What I really want is a simple text substitution macro, of the form:
MACRO(SIMPLE_SCM_TO_C root)
${VALID_CHICKEN} ${Chicken_SOURCE_DIR}/${root}.scm -output-file
${Chicken_BINARY_DIR}/${root}.c ${CHICKEN_FLAGS})
ENDMACRO(SIMPLE_SCM_TO_C)
[snip]
If there's no way to
On Thu 18 May 2006, William A. Hoffman wrote:
> I am not even sure we always have that information. For example,
> someone might do LINK_DIRECTORIES() LINK_LIBRARIES(A).
In principle, CMake has enough knowledge to look for it by scanning
the current LINK_DIRECTORIES for libA.
> Maybe we coul
At 10:44 AM 5/19/2006, Amitha Perera wrote:
>On Thu 18 May 2006, William A. Hoffman wrote:
>> I am not even sure we always have that information. For example,
>> someone might do LINK_DIRECTORIES() LINK_LIBRARIES(A).
>
>In principle, CMake has enough knowledge to look for it by scanning
>the c
At 11:09 AM 5/19/2006, William A. Hoffman wrote:
>Yea, I think that is what is needed.
>
>The other option is to use the Microsoft linker
I have another idea. Write a small program or .bat file
to run the link command and add the -L ability to it.
It would basically setenv LIB to the parse
Brad King wrote:
Try using FOREACH:
FOREACH(root batch-driver ...)
ADD_CUSTOM_COMMAND(
OUTPUT ${Chicken_BINARY_DIR}/${root}.c
MAIN_DEPENDENCY ${root}.scm
DEPENDS parameters.scm
COMMAND ${VALID_CHICKEN} ${Chicken_SOURCE_DIR}/${root}.scm
-output-file ${Chicken_BINARY_DIR}/${root}.c
Brandon J. Van Every wrote:
DEPLIST(chicken build chicken-ffi-macros chicken-more-macros tweaks)
SIMPLE_SCM_TO_C(chicken)
You could take advantage of variable macro arguments. The token
"${ARGN}" will be replaced by arguments beyond those explicitly named.
Try something like this (untested):
The QT_QTMAIN_LIBRARY and QT_USE_QTMAIN variables are broken as of CMake
2.4.1. They should be fixed on the trunk and when CMake 2.4.2 is
released.
-Ken
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:cmake-
> [EMAIL PROTECTED] On Behalf Of Cristian Adam
> Sent: Wednesday, May 17,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Martin wrote:
> I incorporated some changes from Lloyd's patch and committed it to CVS.
> Basically if a project sets CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS on then you
> can leave off the arguments for the endif endwhile, else and endforeach
> commands
Brad King wrote:
Brandon J. Van Every wrote:
DEPLIST(chicken build chicken-ffi-macros chicken-more-macros tweaks)
SIMPLE_SCM_TO_C(chicken)
You could take advantage of variable macro arguments. The token
"${ARGN}" will be replaced by arguments beyond those explicitly named.
Try something lik
Upon trying to compile cmake with uClibc-0.9.28 (on linux-2.6.14.3 on i686 pc),
I encountered an error, caused by a slight typo. The patch is simple and is
included here.
Just thought the cmake devs would like to know,
Osor
--
Osor Hirutonis
Case Western Reserve University
This is supposed to fi
At 03:42 PM 5/19/2006, Osor wrote:
>-#if !defined( WIN32) || defined(__UCLIBC__) /* not needed on win32 */
>+#if !(defined( WIN32) || defined(__UCLIBC__)) /* not on win32 or uClibc */
> extern int fputc(int, FILE *);
> #endif
>
Thanks, I have put the change in cvs, should be in CMake 2.4.3.
Ch
Hi,
> Von: Andreas Beckermann <[EMAIL PROTECTED]>
...
> In order to fix this problem, I propose to forward QT_MOC_EXECUTABLE to
> the
> kde3uic.cmake script and then use that variable, instead of the
hardcoded
> binary name. Just like it is done with the KDE_UIC_CPP and _H and _FILE
>
Hi,
I am trying to use ctest as a Dart2 client,starting with a very simple
settings. I wrote a CMake script "script.cmake" following a guidance on
the Cmake WIKI pages, and made it run. But I got following error messages.
--
Hi,
We're building teem against VTK 4 and VTK 5, and it looks like we're going
to build it with different flags depending on the VTK version to get it to
compile. Is there a good way to test for the VTK version in CMake so we
can use the same CMakeLists.txt for both cases?
Thanks,
Katie
__
19 matches
Mail list logo