Alan wrote:
> Isn't that the complete issue? My experience (under Wine, but the
principle
> is the same) is you must have mingw32-make.exe on your
PATH in order for -G
> "MinGW Makefiles" to work. So you will
have to be careful of dependencies,
> but you should be able to
download and unpa
On 06/15/2010 05:07 PM, Kevin Fitch wrote:
> I have been converting an existing make based build system over to cmake,
> and overall I am loving it so far.
>
> I happened to run across CheckForPthreads.c, and was a little surprised to
> see that it was basically a classic example of racy code.
>
On 2010-06-16 19:04-0700 Alok Govil wrote:
Hi all,
I am unable to build using MinGW-W64, but chances are there would be some
configuration issues.
Here is how I am setup right now:
1. Download latest "automatic" builds (W64 and W32) from here:
http://mingw-w64.sourceforge.net/
2. Removed p
Hi David,
You have raised the right concern. My intention is not to compare various
MinGW builds but to understand how to configure Cmake 2.8.2 to build with
MinGW-W64, since this support is being added to CMake. As it stands now, given
lack of understanding of how to do this with CMake, I a
On Wed, Jun 16, 2010 at 10:04 PM, Alok Govil wrote:
> Hi all,
>
> I am unable to build using MinGW-W64, but chances are there would be some
> configuration issues.
>
> Here is how I am setup right now:
>
> 1. Download latest "automatic" builds (W64 and W32) from here:
> http://mingw-w64.sourcef
Hi all,
I am unable to build using MinGW-W64, but chances are there would be some
configuration issues.
Here is how I am setup right now:
1. Download latest "automatic" builds (W64 and W32) from here:
http://mingw-w64.sourceforge.net/
2. Removed prefixes: For example, renamed file "x86_64
The CMake 2.8.2 release candidate stream continues!
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/.
Since we switched to git, and a new workflow, we're
expecting to do more frequent releases. Because of
that, our release candidate phases will be shorter
than they have
On Wednesday 16 Jun 2010 8:51:27 am you wrote:
> On Tuesday 15 Jun 2010 11:32:17 pm Andreas Pakulat wrote:
> > On 15.06.10 22:18:04, Kishore wrote:
> > > How do i inform cmake when building a module that it depends on another
> > > module? Does cmake need to even know that?
> > >
> > > I am buildi
>From the bug Description at
http://public.kitware.com/Bug/view.php?id=3796:
Visual Studio has "Solution Folders" for grouping Projects (i.e. build
targets). Large software projects would benefit from this feature. I
suppose the appropriate command would be PROJECT_GROUP, to parallel
SOURCE_GRO
Hi Bill:
I suspect the questions below got lost in the stack of e-mail over last
weekend. Anyhow, I am still very much interested in the answers since all
questions concern possible limitations in the MinGW/MSYS/CMake/Wine
platform, and I am currently putting together a writeup of that platform i
So what is PROJECT_GROUP then? I don't see it in the help pages in branch
'next'.
James
On Tue, Jun 15, 2010 at 10:29 AM, David Cole wrote:
> The patch in issue #3796 has not been applied to the CMake 'next' branch
> yet. I think it is too late to consider for the 2.8.2 release, but it could
>
I finally got everything working with cmake 2.8.1, there is just one
glitch, one cannot set CTEST_BUILD_COMMAND for CTEST_BUILD_TARGET to
work.
I added a bug report here:
http://cmake.org/Bug/view.php?id=10838
I simply had to comment out my setting:
#SET (CTEST_BUILD_COMMAND "make -i")
HTH
On
Hi,
On Mon, Jun 14, 2010 at 05:00:47PM +0200, Andreas Mohr wrote:
> On Mon, Jun 14, 2010 at 09:54:58AM -0400, Bill Hoffman wrote:
> > To be compatible with CMake, I would say a BSD license would be the
> > best. gitorious might be a good starting place. We tried the converter
> > here, and i
On Tue, 15 Jun 2010 18:05:06 -0400, Michael Jackson said:
>Just FYI that Apple released the OS X 10.6.4 update today that among
>other things _should_ have fixed the messed up ncurses library that
>stopped the arrow keys from working with ccmake.
> As usual use the usual update mechanisms th
On Tue, Jun 15, 2010 at 11:10:37AM +0200, Jesper Eskilson wrote:
> On 06/14/2010 05:00 PM, Andreas Mohr wrote:
>
>> Frankly the entire distinction between CMAKE_CONFIGURATION_TYPES
>> and CMAKE_BUILD_TYPE remains one of the more confusing things,
>> as can be witnessed in several confused postings
I am trying to remove the "Install Options" and "" page from the install
script. The "Install Options" is not required since I do not plan on adding
this project installation directory to the system PATH environment variable.
Also since I am installing a static library I don't see the need for a
Am Mittwoch, den 16.06.2010, 06:56 -0400 schrieb David Cole:
> On Wed, Jun 16, 2010 at 1:26 AM, Micha Renner
> wrote:
> There still some problems with the Express version of VS
> I started the gui-version of CMake and generated the solution
> files
> (empty build di
On 6/15/10 11:13 PM, ben...@cs.its.ac.id wrote:
Hi, I'm currently using some projects that solutions are built from CMake.
They are Delta 3D, Open Scene Graph, osgOcean, and dtOcean. So what I
wanted is to combine a few of those projects into one solution so I don't
have to make them separately a
On Wed, Jun 16, 2010 at 1:26 AM, Micha Renner wrote:
> There still some problems with the Express version of VS
> I started the gui-version of CMake and generated the solution files
> (empty build directory). No errors.
>
> First run in the IDE generates a lot of CMake errors (see appendix).
>
CM
19 matches
Mail list logo
