Excerpts from David Abrahams's message of Fri Jun 05 23:09:44 +0200 2009:
> However, the way CMake reports failures really doesn't fit in with my
> development workflow. I'm doing
>
> make Python-test
>
> and what I get back looks something like this:
>
> ...
>
> 67/ 79 Testing Pyt
Excerpts from troy d. straszheim's message of Sun Sep 06 23:02:53 +0200 2009:
> Sean Chittenden wrote:
> > Hello. I'm trying to use 1.40 in a fresh dev environment using cmake
> > and am having significant difficulties getting it to work. 1.39 works
> > flawlessly with cmake, but 1.40 not
Excerpts from troy d. straszheim's message of Wed Sep 16 17:08:44 +0200 2009:
> Thanks for the patches. I tested and pushed to 1.40.0 branch of cmake repo.
>
> -t
Will these patches land in boost SVN & its next release too?
--
Exherbo KDE, X.org maintainer
_
---
tools/build/CMake/BoostCore.cmake |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Try the following patch.
Use 'cmake -DLIB_SUFFIX=64 .' if you want libraries to be installed to
/usr/lib64.
diff --git a/tools/build/CMake/BoostCore.cmake
b/tools/build/CMake/BoostCore.cmake
inde
Excerpts from troy d. straszheim's message of Mon Oct 26 21:37:58 +0100 2009:
> Ingmar Vanhassel wrote:
> > ---
> > tools/build/CMake/BoostCore.cmake |2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > Try the following patch.
> &g
Excerpts from troy d. straszheim's message of Mon Oct 26 22:35:13 +0100 2009:
> Ingmar Vanhassel wrote:
> > Excerpts from troy d. straszheim's message of Mon Oct 26 21:37:58 +0100
> > 2009:
> >> Ingmar Vanhassel wrote:
> >>> ---
> >>>
Excerpts from troy d. straszheim's message of Mon Oct 26 22:43:16 +0100 2009:
> Sean Chittenden wrote:
> > Take:
> > http://www.gnu.org/software/hello/manual/autoconf/Makefile-Substitutions.html#Makefile-Substitutions
> >
> >
> >
> > Your:
> > http://www.gnu.org/software/hello/manual/autoconf/I
Excerpts from troy d. straszheim's message of Tue Oct 27 17:44:56 +0100 2009:
> Food for thought, I'm interested in any comments.
This sounds like it should be handled by boost upstream, or by ones
distributor. Not really by a project creating a CMake buildsystem for
boost.
--
Exherbo KDE, X.org
Excerpts from Sean Chittenden's message of Wed Oct 28 20:39:59 +0100 2009:
> Avoid pkg-config, it's very Linux and drags in a ton of dependencies
> (most of the time, never required, but that's the way it goes with
> everyone's packaging system of choice). A cmake variable would be
> preferr
Excerpts from Sean Chittenden's message of Wed Oct 28 21:08:19 +0100 2009:
> >> Avoid pkg-config, it's very Linux and drags in a ton of dependencies
> >> (most of the time, never required, but that's the way it goes with
> >> everyone's packaging system of choice). A cmake variable would be
> >> p
Excerpts from troy d. straszheim's message of Wed Oct 28 21:23:26 +0100 2009:
> Ingmar Vanhassel wrote:
> > Excerpts from Sean Chittenden's message of Wed Oct 28 21:08:19 +0100 2009:
> >>>> Avoid pkg-config, it's very Linux and drags in a ton of depen
Excerpts from troy d. straszheim's message of Thu Oct 29 21:03:01 +0100 2009:
> Brad King wrote:
> > troy d. straszheim wrote:
> >> Michael Jackson wrote:
> >>> This is THE SINGLE IMPROVEMENT someone could make for those of us
> >>> using CMake and are dependent on the boost libraries.
> >> I did s
Excerpts from Ingmar Vanhassel's message of Thu Oct 29 21:11:16 +0100 2009:
> Also, some users may want to install multiple versions of boost, so I'd
> shove $BOOST_VERSION in the filename too.
On that note, it would be a good help if our includes were installed in
a versioned directory.
--
Exhe
Excerpts from troy d. straszheim's message of Thu Oct 29 23:18:12 +0100 2009:
> Ingmar Vanhassel wrote:
> > Excerpts from troy d. straszheim's message of Thu Oct 29 21:03:01 +0100
> > 2009:
> >> Brad King wrote:
> >>> troy d. straszheim wrote:
>
14 matches
Mail list logo
