I always think I solved the problem by chance. So I go back to think the
reason why the old repo code configured failed. It is not possible to cause
the problem by the renamed path and the branch of libreoffice-5-0-6. Over
the next three days, there was no progress on this matter. An accidental
op
Thanks to both for a very good explanation.
I have converted the information into a wiki page (referenced from our
GetInvolved page):
https://wiki.documentfoundation.org/Development/GetInvolved/windowsProblems
Feel free to update the page if needed.
keep up the good work
rgds
jan i.
> On 06 Ma
> fsutil file setshortname "Program Files (x86)" PROG~1
> fsutil file setshortname "Microsoft Visual Studio 12.0" msvc~120
> fsutil file setshortname "Windows Kits" W~Kits
>
If you have the chance to choose shortnames yourself, why not use some
readable ones then instead of mimicking the OS algori
Thanks Norbert.
I have remembered that I renamed the path from "D:\sources\core" to
"D:\sources\libre-core" after you told me to check the path.
Furthermore, I checkouted the branch from master to libreoffice-5-0-6.
Then I git cloned again to "D:\sources" and configured on the master branch.
shi
On Tue, May 3, 2016 at 4:09 AM, jemmy wrote:
> Hello, everyone!
> I'm a new developer of libreoffice. I have followed the instructions from
> https://wiki.documentfoundation.org/Development/BuildingOnWindows and used
> the recommended settings and paths. I use Win10 x64 system 、 64-bit
> Cygwin、32
Hello, everyone!
I'm a new developer of libreoffice. I have followed the instructions from
https://wiki.documentfoundation.org/Development/BuildingOnWindows and used
the recommended settings and paths. I use Win10 x64 system 、 64-bit
Cygwin、32-bit Java JDK、VS2013_RTM_PRO.
./autogen.sh --with-exte
