> > Actually, this script is not "OOo side" integration.
>
> Wrong. It is. It is a file for loooking where OOos SDK is.
Yes, but it couldn't be called "OOo side" integration now because it needs to
be included into client's project, and it searches for OOo installations in the
system, not be
[ please follow Netiquette and wrote proper lines with proper linebreaks ]
Hi,
On Tue, May 25, 2010 at 05:20:49PM +0400, Konstantin Tokarev wrote:
> > Actually, no, I disagree. As it's just a data file, we can just include
> > it in the SDK.
>
> Actually, this script is not "OOo side" integrat
> Actually, no, I disagree. As it's just a data file, we can just include
> it in the SDK.
Actually, this script is not "OOo side" integration. It's intended to be
included into projects using CMake, it will not work from from SDK location
(as, for example, pkg-config files work). Alternativel
On 5/25/10 2:01 PM, Rene Engelhard wrote:
Hi,
On Tue, May 25, 2010 at 01:46:12PM +0200, Juergen Schmidt wrote:
Once you have created such a page it would make sense to reference it
from http://wiki.services.openoffice.org/wiki/Extensions_development
Actually, no, I disagree. As it's just a da
Hi,
On Tue, May 25, 2010 at 01:46:12PM +0200, Juergen Schmidt wrote:
> Once you have created such a page it would make sense to reference it
> from http://wiki.services.openoffice.org/wiki/Extensions_development
Actually, no, I disagree. As it's just a data file, we can just include
it in the S
Hi Konstantin,
it sounds interesting and i would suggest that you create a wiki page
where you document it in detail. Ideally with an example.
Once you have created such a page it would make sense to reference it
from http://wiki.services.openoffice.org/wiki/Extensions_development
Juergen
On Tue, May 25, 2010 at 01:59:56PM +0400, Konstantin Tokarev wrote:
> File is attached. License is BSD. Any fixes/addition are welcomed.
No. ;)
(And you better file an issue with the patch anyway)
Grüße/Regards,
René
-
To unsu