[dev] Built and now what ?
I think I got project sal rebuilt cleanly with debug=true. Then I wanted to check that I can run soffice from solver directly (before delivering the new libs into the output tree so that any problems could not be attributable to anything to do with the new libs). Entering $SRC_ROOT solver/680/unxlngi6/bin/soffice gave a neat little window with the text The application cannot be started. An internal error has ocurred. The message is clear but the solution less so. I didn't find some 'setup' or whatever script. Anyway, I don't want to install over my ordinary 'operational' OO nor delete/overwrite its settings etc. How can I run the solver version completely separate from the operational one? Regards, Enno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Specifications - summary suggestions ...
On 11/3/06, Mathias Bauer [EMAIL PROTECTED] wrote: Let's put it that way: it should be possible to integrate something even if the original goal laid out in the spec wasn't reached but the result is good enough. Good enough means that we could live with it even if nothing was changed until the release date. This is something you always must take into account, especially in case of community development. ... We never should accept unfinished UI work in a way that parts of the necessary functionality *willingly* don't work to a degree that users will expect in a professional application. This can't be described by a fixed percentage but I assume that it can be judged with common sense. If developer, QA and other participants agree that it's good enough, then let's take it. I like the way you put it. This is essentially what I was trying to say in my post. Looks like we're on the same page here. Kohei - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Built and now what ?
On 06/11/2006, at 4:03 AM, Enno Fennema wrote: I didn't find some 'setup' or whatever script. Anyway, I don't want to install over my ordinary 'operational' OO nor delete/overwrite its settings etc. How can I run the solver version completely separate from the operational one? I usually build with rpm and install it into my home directory, as different versions live side-by-side, although they share one ~/.openoffice.org2 (and sometimes one .config ). You might save this somewhere, or you could consider working as a different user. The output tree does not contain a running installation, but it contains an installation package. This could be rpm, deb or something, it depends what you configured for example --with- package=rpm else it takes the default for the build platform distribution. You can re-package for rpm or whatever you like this way, there is no need to re-build. export PKGFORMAT=rpm cd instsetoo_native build The installation sets are in instsetoo_native/unxlngs.pro/ (product) / install/ (lang) There are three products OpenOffice.org, OpenOffice.org_SDK and URE You can move these somewhere to keep them safe in case you make a new one. I usually build with rpm and install it into my home directory, as different versions live side-by-side, although they share one ~/.openoffice.org2 (and sometimes one .config ). You might save this somewhere, or you could consider working as a different user. The install script is on mirrors in openoffice.org/developer/ install_scripts To create a new OOo installation in ~/m192 I run it like this with absolute paths $ ./install_linux.sh /path/to/rpm /home/jim/m192 There are other ways and some probably better, but this will get you started quickly. Look in instsetoo_native/util/makefile.mk for more options. You can build the different targets in there, using dmake. There are some improvements on the way, that will create a ready to run installation. jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] test frameworks (was: [dev] Specifications - summary suggestions ...)
Frank Schönheit - Sun Microsystems Germany [EMAIL PROTECTED] writes: What are testshl2 and cppunit? (No, I don't want to google. I want the pointer to the Wiki page where you document their usage inside OOo :) Hi Frank, glad to tell _you_ something new. ;-) cppunit is a port of JUnit to c++ - and dude, seems that testshl2 is indeed totally undocumented (I vaguely remember some stuff on the old wiki, appears lost). We should nudge lla to provide an overview - apart from that, cppunit/TestAssert.h together with the boilerplate in o3tl or basegfx should get you started... Cheers, -- Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
