LibreOffice build succesfully finished.
It took 3 hours on a non-dedicated machine.
Best,
walter
Da: libreoffice-bounces+w.guerrieri=ranocchilab.com@lists.freedesktop.org
[mailto:libreoffice-bounces+w.guerrieri=ranocchilab.com@lists.freedesktop.or
g] Per conto di walter
Inviato: lunedì 20 febbraio 2012 08:52
A: libreoffice@lists.freedesktop.org
Oggetto: cygwin 1.7.10 - LO-3-5 - the compiler error in npwin.cpp reappears
On Fri, 2012-02-17 at 22:10 +0100, walter wrote:
Compiling: np_sdk/mozsrc/npwin.cpp
C:/LO35/np_sdk/mozsrc/npwin.cpp(171) : error C2440: 'return' : cannot
convert from 'const char *' to 'char *'
I just pushed an explicit cast to master that (I hope) 'fixes'
this, at least it probably hides the underlying problem more than a fix.
Can anyone help me ?
So hopefully a git pull -r ; and a re-build would help there,
or you can clobber it yourself ;-) extra points for getting to the root of
the
problem: what changed, what is the correct fix etc.
HTH,
Michael.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------------------------
have removed my local directory and I have re-cloned the project.
The error remains the same.
I dont understand why my local copy of npwin.cpp is not updated !!
Any idea ?
Best regards
walter
Context
- R: cygwin 1.7.10 - LO-3-5 - the compiler error in npwin.cpp reappears [SOLVED] · walter
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.