On 11.04.2011 16:16, Joachim Lingner wrote: > On 11.04.11 15:35, Stephan Bergmann wrote: >> On 04/11/11 14:42, rony wrote: >>> >>> On 11.04.2011 13:16, Stephan Bergmann wrote: >>>> On 04/11/11 12:24, rony wrote: >>>>> What I would be after would be to get this information at >>>>> installation >>>>> time without any user-interaction (most won't know what would be >>>>> asked) >>>>> in a platform independent manner. >>>>> >>>>> Something equivalent to a hyptohetic "uninfo bitness" returning >>>>> either >>>>> "32", "64" or "32 64" (if a universal binary). >>>> >>>> I don't think there is something better than inspecting the binaries >>>> with platform specific tools right now. Internally, of course, OOo >>>> knows what "platform" (x86 Linux, x64 Linux, x86 Mac OS X, etc.) it >>>> is---this is at least needed when filtering out extension material >>>> that is not appropriate for the given platform. (Also, the standard >>>> ways to interact with an OOo installation is either via UNO, which >>>> abstracts over those platform details, or through extensions, which >>>> already support platform differences.) >>> It seems that this is some sort of a chicken and egg problem. >>> >>> E.g. on MacOSX: if one uses Java to query the configuration via UNO, it >>> may be the case that 64-bit Java is used instead of a 32-bit Java when >>> getting in touch with OOo/UNO, which may be a 32-bit (and sometimes in >>> the future) a 64-bit implementation or both (universal binary). >> >> Right, when you want to use the OOo's URE to set up a UNO connection to >> OOo, you easily run into this chicken/egg problem. >> >>> If no crash is to be expected, what configuration service/path should I >>> use to figure out the architecture/memory model? (Didn't find anything >>> in the schema "Setup.xcs" nor in "Setup-brand.cxu".) Or with other >>> words, is there an XML-file that carries this information, and if so >>> what is its name and element (this would be even easier to analyze >>> without the need to directyl interact with UNO). >> >> Jochen (now on CC) should know how OOo's extension manager determines >> the current platform. > > The platform is determined ad build time. At runtime one can use then > the bootstrap variables $_OS and $_ARCH to get the information. Thank you! How could one access these attributes via Java?
Should I open an RFE then for making this information available via configuration files that could be processed without a need to have office running? ---rony -- ----------------------------------------------------------------- To unsubscribe send email to [email protected] For additional commands send email to [email protected] with Subject: help
