Thanks for this Noel.
I realise there was no java build flag in CTest after I last emailed you,
have added it now.
Will be in touch again soon
Dave
On 17 June 2012 11:41, Noel O'Boyle wrote:
> Sounds good.
>
> It should take the same time as in the GUI. But on subsequent builds,
> it will o
Sounds good.
It should take the same time as in the GUI. But on subsequent builds,
it will only recompile components that have been updated, along with
dependencies. So modifications to atom.h (a core header file) will be
slower to recompile than modifications to smilesformat.cpp (a plugin).
The
One more question for you: where can I find openbabel.jar in SVN? I'd like
to configure the POM to download the latest version when building, to
accompany the latest sources that ctest pulls in.
Dave
On 17 June 2012 00:27, N David Brown wrote:
> ..so I'm back home again and have checked, it a
..so I'm back home again and have checked, it appears that script is
compiling the project; the bin/Release folder is generated. I'm just amazed
how fast it is compared to building through the Visual Studio GUI. Why is
this? Because the OB gui isn't being built?
I'm hoping to finalise the POM with
Hi Noel,
Forgive the delay, this work is for my PhD which I'm completing in my spare
time outside of work.
I've configured a POM that contains redefinable properties for all paths
and ON/OFF flags in the .make, then generates a .make with values
substituted in. Then it executes the .make . This s
Fantastic, thank you Noel. I'll get back to you towards the end of the week
assuming no issues using it in the meantime. I'll try to create an OB pom
by then.
David
On 12 June 2012 10:04, Noel O'Boyle wrote:
> Please find attached a ctest script you can run as follows:
> ctest -S ob-win-tmp.c
Please find attached a ctest script you can run as follows:
ctest -S ob-win-tmp.cmake -VV > cmake-build.out
("-VV" is verbose output, which is useful in case of problems)
If you look through the script it should make sense, apart from the
reference to CVS which is a quirk of ctest. BTW, before
If it's not much trouble that would be great, Noel. I'd not heard of CTest
but have looked it up now - it makes perfect sense to have CMake perform
the build.
This is actually ideal, as it should allow me to create a complete pom.xml
for OB that you can include in the JAR from now on. If done prop
Sounds good.
Sorry - I just realised something that should make things easier.
Perhaps the best way to do this is actually via a ctest script as you
don't have to hardcode the compiler path. The one we use for our
nightly builds does 4 things: (1) check out of SVN (or else update),
(2) build, (3)
Hi Noel,
I've built it the standard way several times before. I'm now configuring my
own maven project to build the latest version from SVN automatically if
it's not found locally. The configuration's set up for CMake, it's just the
build command I need to get right.
Thank you for providing that
Have you tried first of all compiling it as per the instructions?
http://openbabel.org/docs/dev/Installation/install.html#windows-msvc
Here is the command that ctest uses on my machine to compile
everything at the command-line:
C:\PROGRA~2\MICROS~1.0\Common7\IDE\VCExpress.exe openbabel.sln /build
Hello all,
I created the following batch script to run CMake on OpenBabel sources
(located in checkout/OpenBabel), then build the generated project:
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" x86
&& mkdir checkout\OpenBabel\build && cd checkout\OpenBabel\build && cmake
12 matches
Mail list logo
