I attached my dirty but working solution: I just override the default command
line in each case. Do some people care about this problem or do I really have
to write a bug report?
Thank you for your help, it works fine now ;)
___
Frédéric Sagnes, AD
Sagnes, Frederic wrote:
I attached my dirty but working solution: I just override the default command
line in each case. Do some people care about this problem or do I really have
to write a bug report?
Thank you for your help, it works fine now ;)
That's exactly what I suggested and
How about:
INSTALL(CODE MAKE_DIRECTORY(\lib/chicken/1\))
Brandon J. Van Every wrote:
In CMake 2.4.2, to install an empty directory I tried
# Destination for eggs. No eggs to install though.
INSTALL(FILES DESTINATION lib/chicken/1)
but it doesn't do anything. Is there a way?
Cheers,
Thanks a lot jan for the script.
However i tried the FORCE option but nothing changed.
Is it a way when it's write Building CXX objet to see all the command line ?
Thanks
Jan Woetzel a écrit :
Xavier Larrode wrote:
SET(CMAKE_CXX_FLAGS ${OSG_CFLAGS})
I think you need FORCE here.
However,
David Cole wrote:
How about:
INSTALL(CODE MAKE_DIRECTORY(\lib/chicken/1\))
Almost! Needs a ${CMAKE_INSTALL_PREFIX} qualifier, then it works.
# Destination for eggs. No eggs to install though.
INSTALL(CODE
MESSAGE(STATUS \Installing ${CMAKE_INSTALL_PREFIX}/lib/chicken/1\)
Am I correct inferring from this thread that the chicken actually did
come first?
Brad King wrote:
Brandon J. Van Every wrote:
David Cole wrote:
How about:
INSTALL(CODE MAKE_DIRECTORY(\lib/chicken/1\))
Almost! Needs a ${CMAKE_INSTALL_PREFIX} qualifier, then it works.
#
Francesco Montorsi wrote:
Hi all,
I'm involved in a project (about a package manager) which needs to
be able to build source packages which are using a cmake-based build
system.
Since I'm quite new to cmake, I'm asking you some help about the
following question:
is it possible to
Brandon J. Van Every wrote:
Brandon J. Van Every wrote:
Can a CMake script invoked with
EXECUTE_PROCESS(
COMMAND ${CMAKE_COMMAND} -P myscript.cmake
RESULT_VARIABLE myresult
)
return a value? I don't really want to use stdout. I need that for
status messages. I could regex the stdout
Alan W. Irwin wrote:
I believe you need more information than -L and -l options; you also
need to
know the special link options that are required (for rpath, shared versus
static, bundle or whatever) on the particular platform that is being used
for the build.
Bill mentioned above the
David Cole wrote:
Am I correct inferring from this thread that the chicken actually did
come first?
Brad King wrote:
Brandon J. Van Every wrote:
# Destination for eggs. No eggs to install though.
INSTALL(CODE
MESSAGE(STATUS \Installing \${CMAKE_INSTALL_PREFIX}/lib/chicken/1\)
Brad King wrote:
Brandon J. Van Every wrote:
Brandon J. Van Every wrote:
Can a CMake script invoked with
EXECUTE_PROCESS(
COMMAND ${CMAKE_COMMAND} -P myscript.cmake
RESULT_VARIABLE myresult
)
return a value? I don't really want to use stdout. I need that for
Brad King wrote:
Actually to be completely correct you need to account for DESTDIR
installs. Also you do not want the install prefix or destdir to
evaluate until install time, so you need to escape the $ tokens too:
INSTALL(CODE "
MESSAGE(STATUS \"Installing
Hi Alexander,
Thank you again!
I wrote a macro (MY_QT_WRAP_UI) to solve my problem. As a suggestion, I
think CMake could have two variables to set those extensions, something
like CMAKE_QT_UI_HEADER_EXTENSION and CMAKE_QT_UI_DECLARATION_EXTENSION.
Flavio
Alexander Neundorf wrote:
Hi,
Brad King wrote:
CMAKE_COLOR_MAKEFILE OFF
What is the value of TERM in the compilation window?
(1) I think XEmacs is using an xterm but doing his own extar coloring to mark e.g. errors in red.
Is that the problem?
M-x compile / Compile command: / printenv
contains:
...
Jan Woetzel wrote:
CMAKE_COLOR_MAKEFILE OFF
(1) I think XEmacs is using an xterm but doing his own extar coloring
to mark e.g. errors in red. Is that the problem?
OK,
an xterm running inside (X-)Emacs can be determined via EMACS
environment variable
printenv inside Emacs contains
Jan Woetzel wrote:
(1) I think XEmacs is using an xterm but doing his own extar coloring
to mark e.g. errors in red. Is that the problem?
for the records:
This is a workaround for the color problems:
Use compile-command
make -C dir | tee
tee removes all the undesired escape sequences :)
Hi,
I've been trying to build CMake on Digital Unix (V4.0f), and have
encountered a couple of problems.
The first problem was that bootstrapping failed due to usleep() not
being defined.
I managed to get past that fairly easily by temporarily #defining
_XOPEN_SOURCE_EXTENDED for the duration of
17 matches
Mail list logo