Hi there
The best building tool for Java I know so far seems to be maven,
but it still doesn't give so much flexibility as cmake at all!
Anyone knows a cmake-alike tool for java?
___
Powered by www.kitware.com
Visit other Kitware open-source projects
On 08/20/2010 12:42 PM, Michael Wild wrote:
>
> On 19. Aug, 2010, at 23:36 , Michael Hertling wrote:
>
>> On 08/19/2010 09:42 PM, Michael Wild wrote:
>>>
>>> In that case I recommend creating a CMake script (e.g.
>>> create_application_version.cmake) which creates the ApplicationVersion.xml
>>>
You might consider using my CreateLaunchers cmake module that will set
up the debugger for you to add whatever directories you like to the PATH
(on windows) so that it can find the dynamic libraries. I haven't tried
it in the case that the libraries are built in the same project - you'd
proba
Hello,
The path to a binary target built by cmake depends on the
configuration type when using the Visual Studio generators. Is it
possible to pass this path the ctest without having to run ctest with
the -c option?
I'd like to do the following:
I create an executable with cmake as follows, and a
My current codebase produces an executable with several dynamically linked
libraries. I can't step through the code under the debugger until I've built
the 'install' project, which copies all the binaries into the same output
directory; they then can find each other. Of course, at this point I
Ralph Barth will be out of the office starting 20.08.2010 and will be
returning on 24.08.2010.
Ich werde Ihre Nachrichten nach meiner Rückkehr beantworten.
Deutsche Börse Systems AG
Chairman of the Supervisory Board/
Hi all,
I would like to check if one piece of code generates a warning or not
(about a deprecated method). I want to use TRY_COMPILE and adds -Werror
to gcc flags.
I have tried the following:
TRY_COMPILE(VTK_FFMPEG_GUESSFORMAT
${VTK_BINARY_DIR}/CMakeTmp
${VTK_CMAKE_DIR}/vt
Hi all,
How can I use try_run with multiple source files?
Something like: gcc foo.c foo_fn.c -o newfoo
So far I've came up with the following..
try_run (RUN_RESULT_VAR COMPILE_RESULT_VAR
${CMAKE_BINARY_DIR}
${CMAKE_CURRENT_SOURCE_DIR}/foodir/foo.c
CMAKE_FLAG
On Fri, Aug 20, 2010 at 8:40 AM, Mike McQuaid wrote:
>
> On 20 Aug 2010, at 13:09, David Cole wrote:
>
> > Sorry about that. The name was chosen when the functionality was
> Mac-only, then we extended it to cover Windows/Linux. What name would you
> suggest as "more discoverable" or "better"?
>
>
On 20. Aug, 2010, at 14:29 , Diablo 666 wrote:
>
>> This sounds like a pretty oldish version of CMake to me... What version are
>> you using?
>
> "cmake version 2.6-patch 4", Compatibility mode is set to 2.6 via the
> CMakeLists.txt
Yeah, that was a problem of 2.6. 2.8 doesn't try to force t
On 20. Aug, 2010, at 14:42 , Eric Noulard wrote:
> 2010/8/20 David Cole :
>> On Fri, Aug 20, 2010 at 7:37 AM, Mike McQuaid wrote:
>>>
>>> Hi,
>>>
>>> There's been some discussion on
>>> http://public.kitware.com/Bug/view.php?id=11126 and I raised the issue about
>>> the BundleUtilities port to
2010/8/20 Mike McQuaid :
>
> On 20 Aug 2010, at 13:09, David Cole wrote:
>
>> Not a big fan of this one either. Personally, I think it's stupid even to
>> have differences between the build tree and the install tree. Now, with
>> this, you'd have differences between the "make install" tree and t
2010/8/20 David Cole :
> On Fri, Aug 20, 2010 at 7:37 AM, Mike McQuaid wrote:
>>
>> Hi,
>>
>> There's been some discussion on
>> http://public.kitware.com/Bug/view.php?id=11126 and I raised the issue about
>> the BundleUtilities port to Windows/Linux: the naming is so bad as to make
>> this (prett
On 20 Aug 2010, at 13:09, David Cole wrote:
> Sorry about that. The name was chosen when the functionality was Mac-only,
> then we extended it to cover Windows/Linux. What name would you suggest as
> "more discoverable" or "better"?
I'd go for "InstallPrerequisites" personally, it seems to fit
> This sounds like a pretty oldish version of CMake to me... What version are
> you using?
"cmake version 2.6-patch 4", Compatibility mode is set to 2.6 via the
CMakeLists.txt
___
Powered by www.kitware.com
V
On Fri, Aug 20, 2010 at 7:37 AM, Mike McQuaid wrote:
> Hi,
>
> There's been some discussion on
> http://public.kitware.com/Bug/view.php?id=11126 and I raised the issue
> about the BundleUtilities port to Windows/Linux: the naming is so bad as to
> make this (pretty cool) feature completely undisc
Hi,
There's been some discussion on http://public.kitware.com/Bug/view.php?id=11126
and I raised the issue about the BundleUtilities port to Windows/Linux: the
naming is so bad as to make this (pretty cool) feature completely
undiscoverable.
I assumed, as I'd think others would, that this woul
On 20. Aug, 2010, at 10:56 , Diablo 666 wrote:
>
> Hi,
>
> there seems to be a little bug in ccmake:
> When I start cmake like follows:
>
> cmake . -DFOO_DIR=/path/to -DVTK_DIR=/other/path/to
>
> I get the following warning:
>
> Warning: CMake is forcing CMAKE_CXX_COMPILER to "/usr/bin/g++"
On 19. Aug, 2010, at 23:36 , Michael Hertling wrote:
> On 08/19/2010 09:42 PM, Michael Wild wrote:
>>
>> In that case I recommend creating a CMake script (e.g.
>> create_application_version.cmake) which creates the ApplicationVersion.xml
>> file. It queries the current revision (have a look at
Hi,
there seems to be a little bug in ccmake:
When I start cmake like follows:
cmake . -DFOO_DIR=/path/to -DVTK_DIR=/other/path/to
I get the following warning:
Warning: CMake is forcing CMAKE_CXX_COMPILER to "/usr/bin/g++" to match that
imported from VTK. This is required because C++ project
I can't say I share this experience. We use this mechanism to substitute
"standard" flags with less or more optimization and/or other options. Usually
-O3 instead of -O2, and I don't get them both on the commandline.
Arjen
From: Brian Davis [mailto:bitmi...@gmail.com]
>>set_source_files_prope
On 08/19/2010 09:20 PM, Alexander Neundorf wrote:
On Thursday 19 August 2010, Johny wrote:
Hey,
Is there any way to increase the number of warnings and errors displayed
on CDash ? Also can we somehow suppress certain warnings and errors ?
Yes, you have to create a CTestCustom.cmake:
22 matches
Mail list logo