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


Hello

Under windows native (don't know about cygwin), there is one limit at 250 characters, depending on the way you store the path (seen with an old version of sqlite dll). This kind of error is more prone when you have a long series of folder, like java components etc.

HTH

regards
Le Sat, 14 Apr 2012 09:42:16 +0200, Lubos Lunak <l.lunak@suse.cz> a écrit:

On Friday 13 of April 2012, Matúš Kukan wrote:
On 12 April 2012 13:38, Caolán McNamara <caolanm@redhat.com> wrote:
> On Thu, 2012-04-12 at 12:57 +0200, Michael Stahl wrote:
>> rumor has it that putting the source in Cygwin home has never ever
>> worked, but i have no idea why.

Heh, so I may be the first person in the world who have done that ? :-)
...
Anyway with this patch I was able to build in /home, install and also
write some text in Draw.
Hopefully it will work also for others (for all ?).

Could someone, please, try ?

Works for me too. I have changed the Win-x86_6-fast tinderbox to build in
~/libreoffice , so this should not go unnoticed the next time.

I think we could remove new warning from
http://wiki.documentfoundation.org/Development/Windows_Build_Dependencies

 I wonder about the part about the length of the path.
(c:/cygwin)/home/tinderbox/libreoffice is not that short, but the build has finished successfully, the resulting .msi installed without problems, and I didn't notice any problems when running it. Has that been fixed somehow as
well?



--
Mat M

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.