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


Hi,

I'd like to share my experience since I didn't see this on Developer's wiki.
When I was trying to build LibreOffice in Windows,  autogen.sh was not able
to finish its job, with message below:

checking cl.exe... found Visual C++ 2013  (E:/Program Files (x86)/Microsoft
Visual Studio 12.0/VC/bin/cl.exe)
cygpath: cannot create short name of 12.0\VC\Include
realpath: '12.0/VC': No such file or directory
configure: WARNING: realpath failed for "12.0/VC", not necessarily a
problem.
checking the dependency generation prefix (cl.exe -showIncludes)...
configure: error: cannot determine the -showIncludes prefix
Error running configure at ./autogen.sh line 269.

Apparently path for Visual Studio broke into parts out of expectation.
After investigation I found that cygpath -d doesn't convert it into 8.3
file name format as it's manual describe. It still generates long file
name.

The solution is simple, the partition has to enable 8.3
format support *BEFORE* you install Visual Studio, with following command:

fsutil 8dot3name set e: 0

0.represents active. Change the drive letter e to whatever you use.

I use Windows8 to build LibreOffice ( A surface3 tablet ). I had built
successfully on Windows7 VM without tuning mentioned above. Both Visual
Studio and LO source code are installed in a VHD disk image on a microSDHC.
I  guess that one of them makes the difference.


-- 
Mark Hung

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.