I am trying to escape having to untar all of the 3rd parties and see which
ones are missing win32 debug libs and dlls.
On first pass of building Libreoffice with:
--enable-dbgutil.
build complained that
ExternalPackage_icu.mk:24 ...file icudtd53.dll does not exist in the
tarball.
So reading configure help. I can set
--with-system-icu and do a debug build there.
My question: Who can send me instructon for how many of these third party
tools have to be built that way? And what about boost? Libreoffice names
its boost libraries not in "boost naming style" How do I handle that.
My dev environment
Cygwin64.
A git clone of Libreoffice from trunk.
Windows 7, SDK 7.0A, DirectX SDK, MSBuild, Visual Studio 2010 Pro (trial
version)
Context
- enable-dbgutil · nicholas ferguson
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.