Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Alex Thurgood
Le 08/10/2012 18:15, Michael Stahl a écrit : Me again, > seems to work here. maybe try "make scp2.clean scripting.clean" and > build again if that improves anything... > Did that, but still no entries in Organize Macros. I can however see them listed in the "LibreOffice Macros" when I click the

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Alex Thurgood
Le 08/10/2012 18:15, Michael Stahl a écrit : > seems to work here. maybe try "make scp2.clean scripting.clean" and > build again if that improves anything... Ah, had no idea that scp2 needed to be rebuilt :-) Trying again now. Thanks, Alex ___ Libre

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Alex Thurgood
Le 07/10/2012 22:59, Alex Thurgood a écrit : Content of the Scripts directories : ls /home/Development/libo/solver/unxlngi6.pro/installation/opt/presets/Scripts/ alex@Aspire-X1430 /home/Development/libo $ ls /home/Development/libo/solver/unxlngi6.pro/installation/opt/share/Scripts/ java python

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Michael Stahl
On 08/10/12 18:05, Alex Thurgood wrote: > Le 08/10/2012 13:25, Michael Stahl a écrit : > > Hi Michael, > >> >> ... but the configure options have not been updated and still call it an >> extension. i've fixed that on master now, you will now get an error >> with the deprecated options. the scri

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Alex Thurgood
Le 08/10/2012 13:28, David Tardon a écrit : Hi David, > > These two script providers have been changed from extensions to optional > components, which means there are no oxt files. For javascript provider, > you should have solver/unx*/bin/js.jar, > solver/unx*/bin/ScriptProviderForJavaScript.j

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Alex Thurgood
Le 08/10/2012 13:25, Michael Stahl a écrit : Hi Michael, > > ... but the configure options have not been updated and still call it an > extension. i've fixed that on master now, you will now get an error > with the deprecated options. the script providers are enabled by > default and can be dis

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread David Tardon
Hi, On Mon, Oct 08, 2012 at 09:30:48AM +0200, Alexander Thurgood wrote: > Le 07/10/12 22:59, Alex Thurgood a écrit : > > > Just to clarify : > > > I tried building master today with the following switches : > > > > ./autogen.sh --enable-binfilter --enable-extra-template > > --enable-extra-samp

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Michael Stahl
On 08/10/12 09:30, Alexander Thurgood wrote: > Le 07/10/12 22:59, Alex Thurgood a écrit : > > > Just to clarify : > >> I tried building master today with the following switches : >> >> ./autogen.sh --enable-binfilter --enable-extra-template >> --enable-extra-sample --enable-ext-scripting-beanshe

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Alex Thurgood
Le 08/10/2012 12:58, d.ostrov...@idaia.de a écrit : > > make VERBOSE=true beanshell.clean BUILD SUCCESSFUL Total time: 14 seconds [build PRJ] beanshell touch /home/Development/libo/workdir/unxlngi6/ExternalProject/beanshell.done mkdir -p /home/Development/libo/workdir/unxlngi6/Package/prepared/

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Alex Thurgood
Le 08/10/2012 12:58, d.ostrov...@idaia.de a écrit : Hi David, > Could you please check that bsh.jar and js.jar are actually built and > delivered, i. e.: > > make VERBOSE=true beanshell.clean > make VERBOSE=true beanshell > Even without doing that I can see : /home/Development/libo/solver/unx

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread d . ostrovsky
Hi, Quoting Alexander Thurgood : Le 07/10/12 22:59, Alex Thurgood a écrit : I used the --enable-ext switches on both OSX and Linux 32bit - same result, no functional beanshell or javascript extensions loaded, however the build doesn't report any errors, even if I make the modules separately.

Re: Beanshell and Javascript extensions not registered in master build

2012-10-08 Thread Alexander Thurgood
Le 07/10/12 22:59, Alex Thurgood a écrit : Just to clarify : > I tried building master today with the following switches : > > ./autogen.sh --enable-binfilter --enable-extra-template > --enable-extra-sample --enable-ext-scripting-beanshell > --enable-ext-scripting-javascript --enable-ext-mysql-

Beanshell and Javascript extensions not registered in master build

2012-10-07 Thread Alex Thurgood
Hi all, I tried building master today with the following switches : ./autogen.sh --enable-binfilter --enable-extra-template --enable-extra-sample --enable-ext-scripting-beanshell --enable-ext-scripting-javascript --enable-ext-mysql-connector --with-system-mysql --enable-symbols --enable-debug --e