Hello Alan,
2013/11/5 Alan Higginson <alan.higginson@gmail.com>
Hello list members,
Is 1.13.1 the latest official released version of CPPUnit? I am noticing
in the git log that Markus Mohrhard made some commits in May that talk
about the 1.13.2 release but I don't see a download link anywhere for this
on the freedesktop.org CPPUnit website. Would anyone here be able to
provide a rough estimate of when I might be able to expect CPPUnit 1.13.2
to be officially released?
So I don't have any rough estimations but if it helps you I can tag the
current HEAD of the cppunit-1.13 branch and release it as 1.13.2. I think
the only change is the support for 64 bit on Windows. I just did not
release it yet because I was hoping for a bug report at some point that
would qualify for a new release.
Background:
I'm hoping to make use of the 64-bit Visual Studio build configuration
changes that Mr. Mohrhard introduced since CPPUnit 1.13.1. I've tried the
head revision of the master branch in git and it seems to build for me
(thanks to Mr. Mohrhard's changes in May) but I need to be able to specify
an official release version number to my organization in order to get
approval to use it in our development environment. Availability of an
official 1.13.2 release would solve this issue for me!
Ok. I'll try to provide a release in a few days. I'll just need to check
that it actually builds on Windows and Linux and that all the defines and
config values reflect 1.13.2
Regards,
Markus
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.