Stephan Bergmann wrote:
IMO a package X-devel only makes sense if the base package X contains something that has an API for clients, and those clients typically need some additional files to interact with X through that API (C headers, link libraries, etc.). The only parts of OOo that would qualify here are the URE and the OOo UNO API. For the latter, there is already the SDK---which also covers support for the former.

Indeed.

There might be another use case. That is to instantly build desired shared
library files without waiting for finishing with full build process or,
at least, building the desired module on the way of full build.

A set of 'devel' packages would help software engineers slightly modify
source code of OpenOffice.org and build desired shared library files.

Scenario
 A customer wants to have Calc with a single sheet at its startup.
 There might be several solutions. E.g delivering and installing template
 files to every PCs over their organization, remotely replacing one of or
 some of shared library files such as scmi.dll as a patch, and so on.

 It seems the initial number of empty sheets is defined here:
 http://svn.services.openoffice.org/ooo/trunk/sc/source/ui/view/tabvwsh4.cxx

    SCTAB nInitTabCount = 3;  //! konfigurierbar !!!
    for (SCTAB i=1; i<nInitTabCount; i++)
        pDoc->MakeTable(i);

 Substituting 3 with 1 and building scmi.dll might bring desired results.
    SCTAB nInitTabCount = 1;  //! Try it !!!


To build the module 'sc' to get locally modified scmi.dll, several header
files 'deliver-ed' into $SOLARVER/$INPATH/inc/ by other depending modules
would be required. If they are available as a 'devel' package, steps would
be surprisingly easier than ever.

 ./configure ...
 ./bootstrap
 source xxxEnv.Set.sh
 cd sc
 export SOLARINC=" $SOLARINC -I/opt/openoffice.org/basis3.1/include"
 export SOLARLIB=" $SOLARLIB -L/opt/openoffice.org/basis3.1/program"
 build

The same concept could be applied to looking into problems with
'dmake debug=1,' fixing bugs, confirming the fix, etc.

Tora

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Reply via email to