<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1>I found a working solution to an issue, that I posted today, to this list …. About using an option feature in autogen.input <o:p></o:p>–enable-dgbutil<o:p></o:p> on a windows platform. My builds were failing… An initial error msg was that build failed because it could find debug libs for icu . My question today to this list was “what do I need to correct ? And get good builds”.<o:p></o:p><o:p> </o:p>A solution I worked out today, corrected issues I was having with building LibreOffice with “–enable-dbgutil”, on a Windows platform. I verified that correct debug lib files even for icu, were being generated. I looked into the /workdir/UnpackedTarBall/icu/source/lib and the debug versions of its range of libs had been built by this LibreOffice build system. <o:p></o:p><o:p> </o:p>My methodology<o:p></o:p><![if !supportLists]>· <![endif]>I searched the list.freedesktop.org archives for “problems with --enable-dbgutil on Windows” and <o:p></o:p><![if !supportLists]>· <![endif]>I did not find an expected series of posts answering previous questions on how to make it work on windows. …Really…. <o:p></o:p><![if !supportLists]>· <![endif]>Nor did I find a series of post to this issue that answered with “we are NOT having any issues building LibreOffice with option feature ‘—enable-dbgutil’ on windows”. <o:p></o:p><![if !supportLists]>· <![endif]>Nor did I get a quick answer with a solution from this list. <o:p></o:p><![if !supportLists]>· <![endif]>Started a review of LibreOffice’s makefile design, and Library<>.mk file interdependencies to discover why I was having this problem… <o:p></o:p><o:p> </o:p>I tossed that investigation aside thinking that that route had been poured over by LibreOffice experts; and took another look.….<o:p></o:p> <o:p></o:p>I didn’t understand why I had to clean up this mess, with an open source product that has been on the market, for years…. <o:p></o:p><o:p> </o:p>Boost libs that were built with LibreOffice’s makefile system were not conforming to boost lib naming conventions. Checking, LibreOffice was working with Boost v 1 55 0. <o:p></o:p><o:p> </o:p>So I decided to independently build Boost v 1_55_0, all of it. This insured that boost libs would have a correct naming convention. That took several hours. and then referred to a lib path in autogen.input. <o:p></o:p>--with-boost-libdir=/home/lo/master/issues/boost_1_55_0/stage/lib <o:p></o:p><o:p> </o:p><![if !supportLists]>· <![endif]>Autogen worked with that option feature “–with-boost-libdir”, as per its explicit design features spelled out in configure.<o:p></o:p><o:p> </o:p><![if !supportLists]>· <![endif]>autogen.input had this option feature:<o:p></o:p>--enable-dbgutil<o:p></o:p><o:p> </o:p><o:p> </o:p>I will post instructions at <a href="https://github.com/nicholasferguson/LibreOffice-Inx-for-VS2010-VS2012-dev-env">https://github.com/nicholasferguson/LibreOffice-Inx-for-VS2010-VS2012-dev-env</a><o:p></o:p><o:p> </o:p>Regards<o:p></o:p>Nicholas<o:p></o:p><o:p> </o:p><o:p> </o:p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>From: nicholas ferguson [mailto:nicholasferguson@wingarch.com] Sent: Tuesday, September 16, 2014 9:29 AM To: 'libreoffice@lists.freedesktop.org' Subject: enable-dbgutil<o:p></o:p></div></div><o:p> </o:p>I am trying to escape having to untar all of the 3rd parties and see which ones are missing win32 debug libs and dlls.<o:p></o:p><o:p> </o:p>On first pass of building Libreoffice with:<o:p></o:p>--enable-dbgutil.<o:p></o:p><o:p> </o:p>build complained that <o:p></o:p>ExternalPackage_icu.mk:24 ...file icudtd53.dll does not exist in the tarball.<o:p></o:p><o:p> </o:p>So reading configure help. I can set<o:p></o:p>--with-system-icu and do a debug build there.<o:p></o:p><o:p> </o:p>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.<o:p></o:p><o:p> </o:p>My dev environment<o:p></o:p>Cygwin64. <o:p></o:p>A git clone of Libreoffice from trunk.<o:p></o:p>Windows 7, SDK 7.0A, DirectX SDK, MSBuild, Visual Studio 2010 Pro (trial version)<o:p></o:p><o:p> </o:p></div></body></html>