On 13. Aug, 2009, at 1:14, Calder Coalson wrote:
I have been torturing myself over the following short bit of code all
day to no avail, so I'm sending out an email to this list in the hopes
that someone can catch whatever stupid mistake I'm making. The code,
which is supposed to find two depen
Mathieu Malaterre wrote:
Hi there,
I do not understand why the following ctest script (*) does not
work. I am not seeing the updated files on my cdash server
(*)
SET(CTEST_CHECKOUT_COMMAND "${CTEST_UPDATE_COMMAND} co
https://path/to/csmtk/ csmtk")
CTEST_EMPTY_BINARY_DIRECTORY(${
I have been torturing myself over the following short bit of code all
day to no avail, so I'm sending out an email to this list in the hopes
that someone can catch whatever stupid mistake I'm making. The code,
which is supposed to find two dependencies for a project is run using
find_package(MacDe
Make VERBOSE=1
Sent from my iPod
On Aug 12, 2009, at 18:15, Hai Nguyen wrote:
Is there some kind of magic to using this other than turning it on?
The behavior seems really inconsistent or it just flat out doesn't
work.
Thanks,
- Hai
___
Powered
Exactly what i want!
Thanks!
On Wed, Aug 12, 2009 at 3:44 PM, Sergey Nikulov wrote:
> Hai,
>
> Just generate makefile as usual without any CMAKE_VERBOSE_MAKEFILE then
> run
> #make VERBOSE=1
> and see if it what you want.
>
>
> 2009/8/13 Hai Nguyen
>
>> I have:
>> set( CMAKE_VERBOSE_MAKEFILE 1
Hi,
My svn repository requires a password. How do I pass the password to
ctest in order to do a "ctest -D Nightly" from a cron job?
Thanks,
Dave
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/openso
Hai,
Just generate makefile as usual without any CMAKE_VERBOSE_MAKEFILE then run
#make VERBOSE=1
and see if it what you want.
2009/8/13 Hai Nguyen
> I have:
> set( CMAKE_VERBOSE_MAKEFILE 1 )
> or
> set( CMAKE_VERBOSE_MAKEFILE ON )
>
> in my CMakeLists.txt
>
> When I generate the build files a
I have:
set( CMAKE_VERBOSE_MAKEFILE 1 )
or
set( CMAKE_VERBOSE_MAKEFILE ON )
in my CMakeLists.txt
When I generate the build files and run make. I don't see any verbosity. It
just shows "Building CXX"
However, I've noticed that when I run make a few times all the sudden
verbosity happensI'
Could you please be more precise in your description?
Thank you,
Sergey
http://catb.org/~esr/faqs/smart-questions.html
2009/8/13 Hai Nguyen
> Is there some kind of magic to using this other than turning it on? The
> behavior seems really inconsistent or it just flat out doesn't work.
>
> Than
Is there some kind of magic to using this other than turning it on? The
behavior seems really inconsistent or it just flat out doesn't work.
Thanks,
- Hai
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com
Hi there,
I do not understand why the following ctest script (*) does not
work. I am not seeing the updated files on my cdash server
(*)
SET(CTEST_CHECKOUT_COMMAND "${CTEST_UPDATE_COMMAND} co
https://path/to/csmtk/ csmtk")
CTEST_EMPTY_BINARY_DIRECTORY(${CTEST_BINARY_DIRECTORY})
FI
On 12. Aug, 2009, at 15:33, avner cohen wrote:
Eric,
I may have used wrong terminolegy there, my IDLs are indeed part of
the the project, It's only that the project is a C++ based project,
so the IDLs are not being "compiled" in any way, they are used to
generated a set of .h and .cpp fil
On 12. Aug, 2009, at 15:27, Julien Michel wrote:
Dear Cmake users,
I would like to add a custom command to be run on each target (in
fact on each target source file). Is there any way to do this with
cmake ? I found the ADD_CUSTOM_COMMAND function, but it must be
called for each target t
Dear Cmake users,
I would like to add a custom command to be run on each target (in fact
on each target source file). Is there any way to do this with cmake ? I
found the ADD_CUSTOM_COMMAND function, but it must be called for each
target to be processed, and I am still missing a way to get the
2009/8/12 avner cohen :
> Eric,
> I may have used wrong terminolegy there, my IDLs are indeed part of the the
> project, It's only that the project is a C++ based project, so the IDLs are
> not being "compiled" in any way, they are used to generated a set of .h and
> .cpp files (which in term, a
Eric,
I may have used wrong terminolegy there, my IDLs are indeed part of the the
project, It's only that the project is a C++ based project, so the IDLs are not
being "compiled" in any way, they are used to generated a set of .h and .cpp
files (which in term, are patr of the project.
As soon as
Hallo, thank you very much.
Of course, the correct sequence (alternative to 'make install') is
cmake OPTIONS path_to_CMakeLists_dir
make
cmake -D COMPONENT=dist -P cmake_install.cmake path_to_CMakeLists_dir
Now it is working for the installation.
Also thank you for the links, they are very useful
Thank you! I have overlooked the -D. I am sorry for this useless message
...
- PŮVODNÍ ZPRÁVA -
Od: "Tyler Roscoe"
Komu: roze...@volny.cz
Předmět: Re: [CMake] Conditional install
Datum: 11.8.2009 - 23:45:06
> On Tue, Aug 11, 2009 at 11:37:54PM +0200, roze...@volny.cz
> wrote:
> > >$ cmak
2009/8/12 avner cohen :
>
> Thanks Tyler.
>
> I'm not sure I'm following how this is related to my question.
>
> The solution I'm looking for is to be able to execute or generate a file,
> ONLY when an out-of-project file is being modified (which is why I tried to
> use checksum caching). How is
2009/8/11 :
> Hallo,
>
> thank you for your reply. I have tried to set the COMPONENT in the INSTALL()
> command, but it did not lead to the expected result. The install command
> I changed to (ONLY for the target I want to install, inspired by
> http://www.cmake.org/pipermail/cmake/2006-October/0
20 matches
Mail list logo