Hi James James Mckenzie schrieb: > I can do that here and I can state that testtool.bin and soffice.bin both die > with the same > error message: > > Could not load the OS X locale discovery library! (libsalsystools.dylib) > no suitable windowing system found, exiting. > > Is there another setting I'm supposed to be working with?
As far as soffice.bin is concerned this is the reason for the existence of soffice script, which just calls soffice.bin after setting some environmental variables and such stuff (perhaps you try a look inside the script - I don't understand most of the things there). testtool.bin seems to work on most systems (e.g. linux) from the scratch - just on intel macs (perhaps on PPC macs too) you need also to set up the environment like soffice-script does. So I used soffice script (not soffice.bin!). And because it has the nice feature to start <whatever my name is>.bin I just did copy it to testtool (not testtool.bin) and start testtool.bin by the so created testtool - script which works fine. Did I get your question right? >> On 28 Feb 2007, at 09:05, Uwe Altmann wrote: >> >>> Hi >>> isn't it not longer necessary to copy the "soffice"-script to >>> "testool" >>> and call that script instead of tettool.bin to get testool started? >>> At least on intel macs it was long time a workaround to get the x11 >>> environment initialized the right way. >> I still do the copy of soffice to testtool. I'll check with the next >> rc that has just been uploaded to see if that can cope without the copy. -- Mit freundlichen Grüßen Uwe Altmann OpenOffice.org auf dem Mac: http://porting.openoffice.org/mac/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
