On Mon, Oct 11, 2010 at 11:26 PM, Joseph Powers <jpowers27@cox.net> wrote:
I'm building for the Mac and the vos:: removal patch didn't include the mac files.
I found three files that have issues:
vcl/aqua/inc/salinst.h
vcl/aqua/source/app/salinst.cxx
vcl/aqua/source/gdi/salgdi.cxx
A patch would be nice; however, suggestions on how to patch are also welcome.
salinst.h:#include "vos/mutex.hxx"
salinst.h:class SalYieldMutex : public vos::OMutex
salinst.h:#define YIELD_GUARD vos::OGuard aGuard( GetSalData()->mpFirstInstance->GetYieldMutex() )
salinst.h: virtual vos::IMutex* GetYieldMutex();
salinst.cxx: vos::OGuard aGuard( *mpSalYieldMutex );
salinst.cxx: maMainThread = vos::OThread::getCurrentIdentifier();
salinst.cxx:vos::IMutex* AquaSalInstance::GetYieldMutex()
salinst.cxx: return vos::OThread::getCurrentIdentifier() == maMainThread;
salgdi.cxx:#include "vos/mutex.hxx"
I'm thinking salgdi.cxx would be just the removal of the #include.
What where vos:IMutex, vos::OMutex, vos::OGuard & vos::OThread replaced with?
OMutex and OGuard have not be replcaed yet.
vos::OThread is replaced by osl:Thread in commit
57ba3a55b9a9c7668cbc30a8ea7ffcadd162e9b4
but I apparently missed a couple in aqua.
I pushed a fix: commit f49028b1bd734cb7ccfcad82df0acf8a950454ae in libs-gui
Norbert
Joe P.
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.