scp2 - modules (and fdo#60924)
bjoern.michaelsen at canonical.com
Thu Jun 20 11:26:34 PDT 2013
sorry for the late reply.
On Tue, Jun 11, 2013 at 05:34:38PM +0200, Matúš Kukan wrote:
> Anyone knows what should be the result of processing scp2 files?
> Few $(OUTDIR)/bin/*.ins files but I mean the solenv/bin/modules/ thing.
> We could install (copy) files directly with gbuild, so what would be
> missing after removing scp2 ?
> Especially I don't understand the chaos in various modules (gid_Module_Foos)
> - do we need them also for Windows? e.g. scp2/source/activex/module_activex.scp
> For Linux it's somehow used to create packages I think.
> Bjoern, do you have ideas how to continue with
> https://bugs.freedesktop.org/show_bug.cgi?id=60924 ?
> Marcos is doing great work there.
> I'm not sure I can continue to mentor it - maybe we are doing good -
> but I don't know which modules do we need in gbuild.
Since with fdo#60924 gbuild knows about:
- which layer a lib belongs to (and thus: were in the install it should end up)
- which of the old gid_Module stuff a lib belongs to
we should able to populate instdir/ on a gid_Module by gid_Module basis. In the
long run, this should allow to conveniently build LibreOffice in parts.
Of course, the gid_Modules differ somewhat as distros patched and modified it
to their needs. We should find a decent default, but in the end distro will
patch the package split to their needs anyway. The important advantage with
having the module information in gbuild: one can shift a lib from one module to
another, without having to tweak and patch _both_ the build and the install.
Ideally, in the end IMHO one would be able to build and install parts of
LibreOffice as in "make install_ure" or "make install_writer" ...
More information about the LibreOffice