ENABLE_TESTS=ON I think? Then "make test" will work.
- Noel
On 23 July 2013 21:48, Geoffrey Hutchison wrote:
>> Maybe I'm overlooking the obvious, but how do you run all of the tests for
>> OpenBabel? I dug around the web, in the source code, etc. but can't find
>> anything that describes how
> Maybe I'm overlooking the obvious, but how do you run all of the tests for
> OpenBabel? I dug around the web, in the source code, etc. but can't find
> anything that describes how to launch all tests. Isn't there something like
> the "make test" that comes with most systems?
Make sure you'v
Maybe I'm overlooking the obvious, but how do you run all of the tests for
OpenBabel? I dug around the web, in the source code, etc. but can't find
anything that describes how to launch all tests. Isn't there something
like the "make test" that comes with most systems?
Thanks,
Craig
Hello Chris,
I've just gotten a virtual machine of Windows 7 64-bit working (on my
Win 7 64-bit machine) using VirtualBox. You might want to try this out
- it would be useful for testing Windows releases. You just install
Win7, (install the updates), activate it, and then take a snapshot.
Then, wh
I've being setting up a Python script for testing OpenBabel's
executables, starting with a simple SMI to InChI conversion with
babel. The file is test/testbabel.py.
Unfortunately, on some non-Windows systems, the executable won't run
without BABEL_LIBDIR being set. Could testers add the following
After some head-scratching, here's one that does automatic checkout
(the trick is that the variables are all still called CVS, except for
one...nice). I think the update is implicit and you don't need to
specify anything.
I need a bit more work to get the tests running properly (some
environment p
> Don't you mean BUILD_GUI:BOOL=ON? If there's a problem I'll fix it,
> but it works for me.
There's a bug with the Mac version of wxWidgets, so on Mac, I don't build the
GUI.
Cheers,
-Geoff
--
SOLARIS 10 is the OS for D
Don't you mean BUILD_GUI:BOOL=ON? If there's a problem I'll fix it,
but it works for me.
On 9 February 2010 20:01, Noel O'Boyle wrote:
> Marcus just gave me a heads up on this:
>
> "I put my slides from Camp KDE up on
> slideshare,
>
> http://www.slideshare.net/cryos/cmake-improving-software-qual
Marcus just gave me a heads up on this:
"I put my slides from Camp KDE up on
slideshare,
http://www.slideshare.net/cryos/cmake-improving-software-quality-and-process
This goes into some of the testing features etc. Essentially all you
really need to do is write a batch script that calls ctest.ex
On Feb 9, 2010, at 6:59 AM, Noel O'Boyle wrote:
> We really need to get CDash set up as soon as possible. There's no way
> to stop these sorts of regressions without automated tests.
Yes, we need many more tests. They're not hard to write. We also need to fix
the tests we have. There are a few
On Mon, Oct 5, 2009 at 6:05 PM, Geoffrey Hutchison
wrote:
>> When a test fails (e.g. file formats not available), it still
>> continues and can easily segfault. Is it possible to make OB_ASSERT
>
> I think we'd want something like OB_FATAL for that case.
We have OB_REQUIRE for this:
void report_
> When a test fails (e.g. file formats not available), it still
> continues and can easily segfault. Is it possible to make OB_ASSERT
I think we'd want something like OB_FATAL for that case.
-Geoff
--
Come build with us!
When a test fails (e.g. file formats not available), it still
continues and can easily segfault. Is it possible to make OB_ASSERT
immediately return or even exit if it fails?
- Noel
--
Come build with us! The BlackBerry®
13 matches
Mail list logo
