Hi Tino,
Tino Rachui - Sun Germany - Development - Software Engineer a écrit :
Hi Eric,
because we cooperated already on i47888 and a solution for 47888 seems
to be unavoidable I think it is a good idea to continue this work. So
I'm willing to help with 47888 and 48216.
Thank you for your help :-)
Could you give me an update of where you are with 47888.
I'll send you directly what I have. Just be patient :-)
In fact, the problem with pluby's proposed code seems to be the build :
why is the linking not possible ? Everything was perfect before ?
We changed nothing in any makefile, and after investigations (if I'm not
wrong), vcl_dummy.obj (and all .obj around ) are not build -> some infos
are missing. Maybe this is the cause.
But why are vcl_dummy* not build ?
When I compare the build logs ( build -v | tee log.log > 2>&1 ), the
order of the build is not the same (between before change/after changes).
Nothing else. These files are hard to analyse, because around 8Mb every.
Other try, to eventually see a syntax/contruction problem : export
CXX="ccache g++ -option" with option=E or c or v.
But it was not helpfull neither...
I have read again and again the changes, and found no syntax problem.
Could this be a bad implementation/definition of SVMainThread class or
around ? The problem who is causing the breakage seems to be caused by
ExecuteApplicationMain() method, because undefined.
Another solution I have thought (not sure it's possible, probably not
clean), was to adapt Florian's code where Objective-C++ was used in
desktop. This time, we could try to use it in vcl, where we could :
add : source/app/svmainmac.mm -> just use CFRunLoop() like if we were
using Cocoa
modify vcl/source/app/makefile.mk to take care of MACOSX &&
(BUILD_OS_MAJOR==10) && (BUILD_OS_MINOR>=3)
replacing svmain.obj with svmainmac.obj in case of MACOSX && ...
modify rules in solenv/inc to add Objective-C++ flags. Cannot be bad.
My problem is where exactlly start the CFRunLoop in SVMainmac.mm and
where exactly stop it
My last rememberance is that we had a solution but it was not possible
to shutdown the OOo when AWT was used so that only an 'exit(0)' helped.
Yes, I remember. Again, thank you for your help :-)
Regards,
eric bachard
--
<[EMAIL PROTECTED]>
Francophone OpenOffice.org Community developer ( Linux PPC and Mac OS X
/ X11)
See : <http://fr.openoffice.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
