Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On Fri, Jan 27, 2012 at 06:55:38AM +0100, Lionel Elie Mamane wrote:
On Thu, Jan 26, 2012 at 02:41:06PM +0100, Alex Thurgood wrote:

Perhaps I misunderstood what François' commits were supposed to do,
but I thought that the Adabas db stuff had been pulled out of the
compilation sequence.

From what I read in the ML archives, François intended to disable only
*installation* of Adabas, and disable its compilation post-3.5.

That's right.

Master is now in post-3.5 state, so now is a good time :)

My intent was to wait some time _after_ the first 3.5 release was
made public and decide then.
That way, if some people still try to use adabas, they have time to
speak after discovering 3.5.x doesn't work for them anymore.

However, I keep seeing this in my build (and
I've not activated any sort of Adabas db switch that I know of) :

[ build CXX ] dbaccess/source/ext/adabas/Acomponentmodule.cxx
[ build CXX ] dbaccess/source/ext/adabas/AdabasNewDb.cxx
[ build CXX ] dbaccess/source/ext/adabas/adabasuistrings.cxx
[ build CXX ] dbaccess/source/ext/adabas/ANewDb.cxx
[ build CXX ] dbaccess/source/ext/adabas/Aservices.cxx
[ build CXX ] dbaccess/source/ext/adabas/ASqlNameEdit.cxx
[ build DEP ] LNK:Library/libadabasuilo.so

This looks like only the User Interface part of Adabas, and not the
driver itself; probably we just forgot to disable that, too.

Yeah, this is probably an oversight.

-- 
Francois Tigeot

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.