Hi Juergen and Jochen, Have a look on the project I launched at school: it is not sure that it will continue, however you can have a look on how we integrated the use of URE and SDK in our build:
http://cvs.sourceforge.net/viewcvs.py/stareditor/ this supposes that the URE and SDK are installed on the machine and build from this. I changed the configure script (much smaller) and imported in our CVS only the necessary modules. Hope that helps, Cedric PS: there was no relation between "Star Editor" and staroffice: we just started from Georges Melies film company: Star Films ;) Jürgen Schmidt a écrit : >> This is a great staring point, but when we integrete it in our >> product, we would have to do our own builds from source for our >> compiler/platform combinations. Some of these combinations are >> currently unsupported in OOo. We want to extend UNO to support these, >> but I fear we dont't have the resources to do this for the whole of >> OOo ;-) > You only need a subset > for the URE: > sal > cppu > cppuhelper > cpputools > jurt > jut > javaunohelper > ridljar > stoc > registry > bridges > remotebridges > idlc > codemaker > udkapi > > URE + SDK: > bean > autodoc > offapi (SDK is shared for URE and Office, offapi contains office API's) > odk > sdk_oo > > for Packaging: > scp > instsetoo_native > > > But i must confess that i am not sure if that are all, i haven't tested. > We build the URE and the SDK from the whole tree, so we have always > everything in place. Especially for the packaging step i don't know all > requirements exactly. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
