| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
ms_sleep() calls and adjust expectations accordingly
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It appears that our trouble was due to a cygwin-style path in the AUTOBUILD
environment variable, and that changeset 0e0bd8b546ad fixed it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
match those in package
|
|
|
|
|
|
|
|
|
|
There was a comment in CMakeLists.txt left over from 2009 (!) about commenting
out the unit test for llcapabilitylistener. Fortunately we've since reinstated
the test as an integration test, but the comment was never removed -- until now.
|
|
|
|
|
|
|
|
|
|
A traceback from a Python script always makes people think there's a bug in
your script. Even when a test program fails to build, CMake often (always?)
tries to run it anyway, via our run_build_test.py script. For that case,
produce a straightforward error message -- rather than an OSError traceback
that doesn't even mention the program name!
|
|
We use boost::phoenix::placeholders::arg1 to imply a whole lambda expression,
replacing boost::lambda. But to bind a plain function in a more
straightforward way, seems classic boost::bind() works while
boost::phoenix::bind() does not.
|
|
Visual Studio 2013 evidently does provide std::fpclassify(), so we no longer
need the funky local alias.
|
|
|
|
It's very irritating that Visual Studio produces a warning for unrecognized
#pragmas, which we then merrily turn into an error -- #pragma is inherently
compiler-specific!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
