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

Re: [tdf-discuss] x86_64 Windows build


2010/11/4 Frank Esposito <frankesposito@gmail.com>:
On Thu, Nov 4, 2010 at 8:36 AM, T. J. Brumfield <enderandrew@gmail.com>wrote:

There is an open OOo bug that is over 5 years old.

http://qa.openoffice.org/issues/show_bug.cgi?id=46594

It seems that OOo developers felt this was an unnecessary feature. However,
as users have commented in that bug report, the 32-bit version doesn't work
in 64-bit Terminal Servers, and Microsoft does not ship a 32-bit server
product anymore. Furthermore, Base can not connect to a 64-bit ODBC data
source.

Given that Microsoft has been shipping 64-bit operating systems for 7 years
now, and that there are legitimate use cases where OOo/LibO can't fufil
user
needs without a 64-bit Windows build, shouldn't this be reevaluated?

And from a pure perception standpoint, it looks like OOo/LibO is behind MS
Office in this regard, given that MS Office offers a 64-bit version.

Thanks!




+2 for 64-bit builds

It is on the TODO list. It needs some porting efforts, however. It is
not as simple as recompiling the source code with a 64-bit compiler.

Regards,
Andras

-- 
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***

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.