On Wed, Nov 2, 2011 at 11:52 AM, Carlo Strata <firstname.lastname@example.org> wrote:
Will win64 native build exist on 3.5.0 or at least 3.5.x releases?
Are we using the Microsoft Free Developer Tools like Visual Studio 2010
for Windows builds (win32 and win64 ones)?
No. You can't use the Free Developer Tools if you want to compile
everything, as some components require ATL, for example, which is not
supported in the Free Compilers. There are a few workarounds to this
and you can make it work, but the safest way is to compile LibO with
the Visual Studio Professional version if you want to distribute the
version. If you are just experimenting, it doesn't matter.
We could think about it (win64 native build) like a GSoC project? Or like a
project to be financed by a local Community?
What's the real cause not to reach this waste Windows platform (win64)? We
could imagine a big data processing / simulation / ..., but also a more
efficient platform usage than WoW64...
The real causes is that is complicated and nobody is working on it, we
added compiler support (the shell extensions are using it), etc. but
some serious work has to be done in the C++/UNO bridges and other
bits. None of them are trivial.
If your client is interested in this, he might consider funding the Win64 port.
Deputy of the Board of Directors
The Document Foundation
Mobile: +34 661 11 38 26
Skype: jcorrius | Twitter: @jcorrius
Unsubscribe instructions: E-mail to email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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