Repost of a snippet of Doug Gregor's original announcement of this list
and call for volunteers:
A small group of volunteers has been working on a new build system for
Boost based on CMake, a cross-platform, open-source build system. We
have reached the point where our core build system has
Evan Wheeler wrote:
Okay, so if you call this windows API function:
SetErrorMode( SEM_NOGPFAULTERRORBOX );
Evan sent a way to do this in python to me offline, it appears to work,
checked in, problem solved for now.
-t
___
Boost-cmake mailing list
On Tue, Jun 17, 2008 at 3:37 PM, Beman Dawes <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, Jun 17, 2008 at 10:43 AM, troy d. straszheim <[EMAIL PROTECTED]>
> wrote:
>
>> Beman Dawes wrote:
>>
>>> I'm still hung at the step that says " Enable BOOST_BUILD_SLAVE and
>>> BOOST_BUILD_TESTING."
>>>
>>> There
On Tue, Jun 17, 2008 at 10:43 AM, troy d. straszheim <[EMAIL PROTECTED]>
wrote:
> Beman Dawes wrote:
>
>> I'm still hung at the step that says " Enable BOOST_BUILD_SLAVE and
>> BOOST_BUILD_TESTING."
>>
>> There are no such entries to enable.
>>
> >
>
> Does this help?
>
> http://svn.boost.org/tra
Beman,
On Tuesday 17 June 2008 05:04:05 Beman Dawes wrote:
> I'm still hung at the step that says " Enable BOOST_BUILD_SLAVE and
> BOOST_BUILD_TESTING."
>
> There are no such entries to enable.
You might have to show "advanced" configuration options. You should see a
checkbox on the GUI for thi
Justins's suggestion:
It seems like it would be easier to have a testing
configuration file that specifies the necessary configuration options. For
example, we could have "BoostTestingSlave.cmake"
was a good one, you can hide details and reduce the number of steps and
avoid editing the cach
KSpam wrote:
I can see how these CMake specifics can be very confusing to someone that is
not used to CMake. It seems like it would be easier to have a testing
configuration file that specifies the necessary configuration options. For
example, we could have "BoostTestingSlave.cmake" with the
On Mon, Jun 16, 2008 at 5:38 PM, KSpam <[EMAIL PROTECTED]> wrote:
> On Monday 16 June 2008 12:58:23 Beman Dawes wrote:
> > * The "Configuration testing" section is totally opaque to someone (me!)
> > who has never used edit_cache. Any why is it called "edit_cache"? It
> > appears to be configurati
Beman Dawes wrote:
I'm still hung at the step that says " Enable BOOST_BUILD_SLAVE and
BOOST_BUILD_TESTING."
There are no such entries to enable.
>
Does this help?
http://svn.boost.org/trac/boost/wiki/CMakeWindowsRegressionQuickstart
it's BUILD_TESTING, not BOOST_BUILD_TESTING, my fault.
On Mon, Jun 16, 2008 at 7:14 PM, troy d. straszheim <[EMAIL PROTECTED]>
wrote:
> Beman Dawes wrote:
>
>> Troy,
>>
>> Here is some initial feedback"
>>
>
> Hey Beman,
>
> All good feedback. I neglected to mention that the documents assume
> that the reader is familiar with building/configuring via
On Monday 16 June 2008 12:58:23 Beman Dawes wrote:
> * The "Configuration testing" section is totally opaque to someone (me!)
> who has never used edit_cache. Any why is it called "edit_cache"? It
> appears to be configuration settings that are being edited.
>
> Specifically, say that running nmake
Okay, so if you call this windows API function:
SetErrorMode( SEM_NOGPFAULTERRORBOX );
It will suppress that error message. I don't know about calling it
from Python. You should read up on this before using it. I wrote a
quick test in C++ where I open a program with a pipe that does a divide
b
12 matches
Mail list logo
