Re: [GERRIT] gbuild migration: pyuno module

2012-06-19 Thread David Ostrovsky
Hi David, On 19.06.2012 07:23, David Tardon wrote: Hi, On Fri, Jun 08, 2012 at 09:22:12AM +0200, David Ostrovsky wrote: Hi, with the last change set https://gerrit.libreoffice.org/#/c/179/ clean build on linux x86_64 with --enable-python=internal is working. Two questions: The thing is on un

Re: [GERRIT] gbuild migration: pyuno module

2012-06-18 Thread David Tardon
Hi, On Fri, Jun 08, 2012 at 09:22:12AM +0200, David Ostrovsky wrote: > Hi, > > with the last change set https://gerrit.libreoffice.org/#/c/179/ > clean build on linux x86_64 with --enable-python=internal is working. > > Two questions: > The thing is > on unix: > python.sh is get copied to bin/py

Re: [GERRIT] gbuild migration: pyuno module

2012-06-13 Thread Stephan Bergmann
On 06/12/2012 03:07 PM, Stephan Bergmann wrote: On 06/11/2012 12:17 AM, David Ostrovsky wrote: Still have to test it on Windows and ask somebody to test it in MacosX. Quick update: Attached windows.patch allowed me to at least build on Windows (on to

Re: [GERRIT] gbuild migration: pyuno module

2012-06-13 Thread Stephan Bergmann
On 06/13/2012 08:52 AM, Stephan Bergmann wrote: On 06/12/2012 11:37 PM, David Ostrovsky wrote: May I ask somebody to check this gerrit-patch on MacOsX? Or may be it would be simplier to send a file-patch or create a feature branch? Just let me know. For the record, I'm currently looking into t

Re: [GERRIT] gbuild migration: pyuno module

2012-06-12 Thread Stephan Bergmann
On 06/12/2012 11:37 PM, David Ostrovsky wrote: May I ask somebody to check this gerrit-patch on MacOsX? Or may be it would be simplier to send a file-patch or create a feature branch? Just let me know. For the record, I'm currently looking into the gerrit patch on Mac. Stephan

Re: [GERRIT] gbuild migration: pyuno module

2012-06-12 Thread David Ostrovsky
On 12.06.2012 15:07, Stephan Bergmann wrote: On 06/11/2012 12:17 AM, David Ostrovsky wrote: Still have to test it on Windows and ask somebody to test it in MacosX. Quick update: Attached windows.patch allowed me to at least build on Windows (on top

Re: [GERRIT] gbuild migration: pyuno module

2012-06-12 Thread Stephan Bergmann
On 06/11/2012 12:17 AM, David Ostrovsky wrote: Still have to test it on Windows and ask somebody to test it in MacosX. Quick update: Attached windows.patch allowed me to at least build on Windows (on top of recent master). "Tools - Macros - Organi

Re: [GERRIT] gbuild migration: pyuno module

2012-06-11 Thread Stephan Bergmann
On 06/11/2012 12:17 AM, David Ostrovsky wrote: On 08.06.2012 15:21, Stephan Bergmann wrote: * SAL_DLLPUBLIC_EXPORT was missing from pyuno/source/module/pyuno_dlopenwrapper.c, so that the pyuno.so wrapper did not export initpyuno. Well it was done intentionally, my understanding was that it is

Re: [GERRIT] gbuild migration: pyuno module

2012-06-10 Thread David Ostrovsky
On 08.06.2012 15:21, Stephan Bergmann wrote: On 06/08/2012 09:49 AM, Stephan Bergmann wrote: On 06/08/2012 09:22 AM, David Ostrovsky wrote: 2. on Linux I'm testing the clean build with --enable-python=internal, and it seems not to work: opening Tools=>Macros=>Organize Macros=>Python and tryin

Re: [GERRIT] gbuild migration: pyuno module

2012-06-10 Thread David Ostrovsky
On 08.06.2012 09:49, Stephan Bergmann wrote: On 06/08/2012 09:22 AM, David Ostrovsky wrote: with the last change set https://gerrit.libreoffice.org/#/c/179/ clean build on linux x86_64 with --enable-python=internal is working. Great to hear. 1. What do you mean by this TODO comment in scp2/s

Re: [GERRIT] gbuild migration: pyuno module

2012-06-08 Thread Stephan Bergmann
On 06/08/2012 09:49 AM, Stephan Bergmann wrote: On 06/08/2012 09:22 AM, David Ostrovsky wrote: 2. on Linux I'm testing the clean build with --enable-python=internal, and it seems not to work: opening Tools=>Macros=>Organize Macros=>Python and trying to open Hello World python Macor. I do not see

Re: [GERRIT] gbuild migration: pyuno module

2012-06-08 Thread Stephan Bergmann
On 06/08/2012 10:51 AM, Bjoern Michaelsen wrote: On Fri, Jun 08, 2012 at 09:49:06AM +0200, Stephan Bergmann wrote: on wnt: native python executable wrapper is built in pyuno/Executable_python.mk now and is delivered by default to bin/python.exe. But then we have a collision with native python ex

Re: [GERRIT] gbuild migration: pyuno module

2012-06-08 Thread Bjoern Michaelsen
On Fri, Jun 08, 2012 at 09:49:06AM +0200, Stephan Bergmann wrote: > >on wnt: > >native python executable wrapper is built in pyuno/Executable_python.mk > >now and is delivered by default to bin/python.exe. > >But then we have a collision with native python executable artifact > >which get build in

Re: [GERRIT] gbuild migration: pyuno module

2012-06-08 Thread Stephan Bergmann
On 06/08/2012 09:49 AM, Stephan Bergmann wrote: But what source do I need exactly for this? Is it still a feature branch? And from above only gives me a "Not Found." Ah, found it now. The wonderful and frightening world of gerrit... ;) Stephan __

Re: [GERRIT] gbuild migration: pyuno module

2012-06-08 Thread Stephan Bergmann
On 06/08/2012 09:22 AM, David Ostrovsky wrote: with the last change set https://gerrit.libreoffice.org/#/c/179/ clean build on linux x86_64 with --enable-python=internal is working. Great to hear. 1. What do you mean by this TODO comment in scp2/source/ooo/common_brand.scp [...] //TODO: This

[GERRIT] gbuild migration: pyuno module

2012-06-08 Thread David Ostrovsky
Hi, with the last change set https://gerrit.libreoffice.org/#/c/179/ clean build on linux x86_64 with --enable-python=internal is working. Two questions: 1. What do you mean by this TODO comment in scp2/source/ooo/common_brand.scp [...] //TODO: This actually belongs into a module of its own: #i