Hi Maho, *, On Sat, Sep 5, 2009 at 12:27 AM, Maho NAKATA<m...@openoffice.org> wrote: > From: Christian Lohmaier <cl...@openoffice.org> > Subject: Re: [qa-dev] Looking for QA-Rep for cws cloph13 - create backwards > compatible builds for Mac by using the developer-sdk during compilation > Date: Fri, 4 Sep 2009 22:21:15 +0200 > >> http://users2.ooodev.org/~cloph/OOo_cloph13_090904_MacOSXPowerPC_install.dmg >> (has been built without mozilla, so configuring Macro security level >> and other mozilla-dependent parts won't work) > > I'd like to volunteer to test on Leopard PPC.
Ah, great - interesing would also be a version of the workspace built on Leopard/PPC > Could you please tell me how to QA your package? It is just functionality testing of the Office itself > It's not very clear to me... > > 1. download > 2. install Yes, and then check whether everything works. With the build above, there should be no difference compared to a default build of DEV300_m52, since I only have PPC with Mac OSX 10.4, and when building on 10.4, it uses the 10.4 versions anyway (there are no newer versions available to build against), so it is merely a check that the cws doesn't break anything. But the cws makes a difference when you build on Leopard, since then, with DEV300_m52 as comparison, it would build against the system's version (i.e. the 10.5 SDK - well not against the SDK, but the system's default libraries that correspond to the 10.5 SDK), as a result, the installset created on Leopard will not run/function properly when trying to run it on Tiger (10.4). The special area to test is external components (ICU, which is "checked" very early, a "Leopard DEV300_m52" build will crash/not load at all on 10.4 because the symbols are expected in a different library/not found and OOo will not launch. a Leopard-cloph13, as the MacIntel installset however, should work as it had been built on Mac OSX 10.4. So especially hyphenation, spellchecking (both native as well as OOo's version), python/java macros, berkeley database should be checked as those use either third-party tarballs built during an OOo build, or use completely external stuff from the system. Apart from that, only regular functionality testing is needed. If you have already testtool experience, and have DEV300_m52 results to compare the cws against, then it would be appreciated as well, but IMHO it is not really necessary to run them. The cws only modifies compiler flags, nothing in the code itself. The basic change of the cws is: *) export MACOSX_DEPLOYMENT_TARGET=10.4 and *) use -isysroot /Developer/SDKs/MaxOSX10.4u.sdk for compiles and *) use -Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk for linking > 3. sdk... The cws doesn't touch anything related to the SDK, so no SDK testing is necessary. The SDK is exaclty the same as before the cws. ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qa.openoffice.org For additional commands, e-mail: dev-h...@qa.openoffice.org
