2010/9/24 Michael Wild :
>
> Oh, wow, hardy is REALLY, *REALLY* old. It still contains only cmake-2.4.7
> which was released more than 3 years ago!
>
> I would recommend downloading a pre-built binary. It is self-contained and
> you can just drop it anywhere you want (e.g. somewhere in your home
Oh, wow, hardy is REALLY, *REALLY* old. It still contains only cmake-2.4.7
which was released more than 3 years ago!
I would recommend downloading a pre-built binary. It is self-contained and you
can just drop it anywhere you want (e.g. somewhere in your home directory) and
simply update your
On 09/23/2010 10:56 AM, Brad King wrote:
On 09/23/2010 12:20 PM, Clinton Stimpson wrote:
I've got a source files for a mixed C/fortran going into one library.
If the library is shared, -lgfortran is added to the link line, and I'm good
to go.
If it is static, -lgfortran is not added to any exec
Don't do that. :-)
Seriously.
But perhaps there should be a name-collision detection since these folders
have to live in the same "namespace" as CMake targets. And what shall we do
in the event of a name-collision... error? Automatic rename of the folder
(perhaps append " folder")?
Or maybe we c
There appears to be a bug in the new solution folders support with VS
2008: if a folder has the same name as a target, the folder appears
empty in the solution, and the targets that were assigned to the folder
appear at the top-level of the solution tree.
In the solution file, it looks like t
Thanks all, for the replies...
I now know that I need to install cmake-curses-gui. However (on my Ubuntu
hardy)
apt-get does not find this package. Do I have to specify a repository in my
sources.list
where it can find this package? I am also ready to compile from source, if
that
is the only way...
On Thursday 23 September 2010, Eric Noulard wrote:
> 2010/9/23 edA-qa mort-ora-y :
> > On 09/23/2010 12:12 AM, Ryan Pavlik wrote:
> >>> If anybody has a good resource, or can recommend some best practices,
> >>> that would be great.
> >>
> >> Use CMake and CPack? See the wiki, and elsewhere on the
On Thursday 23 September 2010, Andrea Galeazzi wrote:
> Hi everybody,
> I've got a project with two configuration (Debug and Release) and two
> target: win32 and ARM.
> In your opinion what's the best way to manage a such kind of project?
> As an example, in my CmakeList I have the following piece
On 09/23/2010 12:20 PM, Clinton Stimpson wrote:
> I've got a source files for a mixed C/fortran going into one library.
> If the library is shared, -lgfortran is added to the link line, and I'm good
> to go.
> If it is static, -lgfortran is not added to any executable or shared library
> that lin
See here for information on build/source directories:
http://www.paraview.org/Wiki/CMake_FAQ#Out-of-source_build_trees
For your example compiler flag (is that gcc only?) and all other info you've
provided so far, you'd probably want to do something like this:
if(CMAKE_CONFIGURATION_TYPES)
se
On 9/23/2010 12:17 PM, J Decker wrote:
The last one may not be supported. You can not give CMake windows paths for
variable and expect it to work... :)
Why put so much emphasis that a / is a path seperator? it's not like
a \ is any more of a valid character for paths and files. I mean I
wo
I would definitely like the build system for the FreeEOS software
project to work properly on Windows. I have no access to that
platform so I was very happy that Arjen was willing to test that build
on Windows for me. However, he cannot finish that effort until the
questions below are addressed s
Hi,
I've got a source files for a mixed C/fortran going into one library.
If the library is shared, -lgfortran is added to the link line, and I'm good
to go.
If it is static, -lgfortran is not added to any executable or shared library
that links with this static library.
Should I add
target_li
>>
> The last one may not be supported. You can not give CMake windows paths for
> variable and expect it to work... :)
Why put so much emphasis that a / is a path seperator? it's not like
a \ is any more of a valid character for paths and files. I mean I
would imagine since it's treating it as
But where could I put the custom options for the compiler, for example
in arm-debug I'd like to have
CMAKE_CXX_FLAGS -no-rtti
what do you mean with build directory, the source directory?
Citando Ryan Pavlik :
Keep these lines, if they are necessary for your system:
if(CMAKE_CONFIGURATION_TYPE
Keep these lines, if they are necessary for your system:
if(CMAKE_CONFIGURATION_TYPES)
set(CMAKE_CONFIGURATION_TYPES Debug Release)
set(CMAKE_CONFIGURATION_TYPES "${CMAKE_CONFIGURATION_TYPES}" CACHE
STRING "Reset the configurations to what we need" FORCE)
endif()
Remove the other lines
On 9/23/2010 10:45 AM, Eric Noulard wrote:
2010/9/23 Bill Hoffman:
On 9/23/2010 3:13 AM, Eric Noulard wrote:
2010/9/23 J Decker:
using 2.8.3-rc1 I decided to throw the project against visual studio
and see what I got.
clicking on the install target
I am responsible for this regression :-(
Hi everybody,
I've got a project with two configuration (Debug and Release) and two
target: win32 and ARM.
In your opinion what's the best way to manage a such kind of project?
As an example, in my CmakeList I have the following piece of code that
works fine only for visual studio.
if(CMAKE_
2010/9/23 Bill Hoffman :
> On 9/23/2010 3:13 AM, Eric Noulard wrote:
>>
>> 2010/9/23 J Decker:
>>>
>>> using 2.8.3-rc1 I decided to throw the project against visual studio
>>> and see what I got.
>>>
>>> clicking on the install target
>>
>> I am responsible for this regression :-(
>
> Not so sure i
On 9/23/2010 3:13 AM, Eric Noulard wrote:
2010/9/23 J Decker:
using 2.8.3-rc1 I decided to throw the project against visual studio
and see what I got.
clicking on the install target
I am responsible for this regression :-(
Not so sure it is the same thing...
Note, the whole path is wrong:
On 9/23/2010 2:27 AM, norulez wrote:
Hello,
is there a way to add additional informations to cdash like Qt version,
database version and such things to the build time. The thing is that i want to
know under which version a build fails.
You can add Notes.
-Bill
_
On 9/23/2010 2:20 AM, J Decker wrote:
using 2.8.3-rc1 I decided to throw the project against visual studio
and see what I got.
clicking on the install target
-- Build started: Project: INSTALL
(CMakePredefinedTargets\INSTALL), Configuration: Debug Win32 --
3> CMake Warning (dev) at cm
Hello,
I think I found the answer: it is only when actually building the
program that the source files get scanned and therefore the depend.make
file gets filled. That, of course, does make sense.
Regards,
Arjen
On 2010-09-23 10:18, Arjen Markus wrote:
Hello,
I am trying to create CMake-base
Hello,
I am trying to create CMake-based build system for a program
that uses both C and Fortran source files. While expanding the
CMakeLists.txt files to include a custom build step for one
C header file, I stumbled on something I do not understand.
The makefiles generated from my first version
I hope there is a "real" answer to this question, but I've solved a similar
problem for us by setting the "Site name" (CTEST_SITE in ctest scripts) to
something which indicates the OS/version/bit-depth/etc. This obviously
doesn't scale to more than a couple key pieces of information, but it may
hel
Once again, thank you very much for your contribution Hannes!
For the completeness of the thread, I post the solution here. This solution is
general for all compilers that fails with rdynamic (e.g. if you try to compile
windows binaries in linux, where you want -shared, not -rdynamic)
Apply this
2010/9/23 J Decker :
> using 2.8.3-rc1 I decided to throw the project against visual studio
> and see what I got.
>
> clicking on the install target
I am responsible for this regression :-(
The issue is known, see those thread;
http://www.cmake.org/pipermail/cmake/2010-September/039668.html
http:
27 matches
Mail list logo
