To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70256 Issue #|70256 Summary|Using Solver: obtaining / maintaining logfiles of refe |rence build Component|tools Version|OOo 2.0.3 Platform|All URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|ENHANCEMENT Priority|P3 Subcomponent|configure Assigned to|rene Reported by|terrye
------- Additional comments from [EMAIL PROTECTED] Tue Oct 10 01:32:58 -0700 2006 ------- I want to use the OOC680_m7 reference source and solver to rebuild OOo after minor tweaks to one of the modules (basic). I want to minimise my start-up time in doing so and have so far failed. One of the key issues here is that lack of documentation on what the basis for creating the OOC680 (or any future solver tarball) is -- that is what was the reference Linux installation, what was that actual configration (gcc version...), etc. Whilst http://tools.openoffice.org/dev_docs/build_linux.html does provide a general discription, it doesn't provide this firm configuration data making it difficult for developers to replicate the solver environment simply. It would REALLY make life so much easier if as standard practice the solver tarballs were created from a script capable of being run as a *single* batch command, and the output (1&2) sent to a logfile (or better logfile per individual step). These logfiles should be maintained in the solver tree and hence also downloadable. This script should start with the clean-out of all the unxlngi4.pro directories, followed by the configure, bootstrap and build --all. This simple process would enable developers to compare their component versions, options, etc against the solver baseline and trace variations in the build against a solver baseline, and also determine where deviations against the reference solver build were occuring. Also it would be useful if you specfied what your actual Linux for the build was as this information is not listed by the configure script. For developers with limited time, it is easier to replicate your rig than to debug their own. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
