openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From janI <>
Subject Re: Is the project dependency chart still valid?
Date Wed, 24 Apr 2013 08:36:12 GMT
On 24 April 2013 09:45, Oliver-Rainer Wittmann <>wrote:

> Hi,
> On 23.04.2013 22:58, Kay Schenk wrote:
>> In my search to find out more about resource files (.src), I came across
>> the old Tools information on the web server, and specifically the project
>> dependency chart:
>> Is this still valid?
> I do not think that it is still 100% valid.
> It contains modules neon and berkeleydb which had been removed during our
> IP clearance work.
> But for a broader view about the module dependencies it can be used.
> Such a dependency graph can only be a snapshot on a certain revision or
> release.
> A dependency graph could be build using the information in the files
> <module>/prj/build.lst. The first text line contains the modules on which
> <module> depends on. The build process uses this information to figure out
> which module needs to build first. But be aware, there might be missing the
> one or the other dependency, because it is not needed for the build process.
> Deeper investigation/evaluation of the makefiles would also reveal
> dependency information.
> But there are also dependencies which are not express in the makefiles or
> the <build.lst> files. For example, certain modules depend on
> default_images - it contains icons and images for the UI -, but this
> dependency is not explicitly mentioned.
I can only agree with the statement that some dependencies is missing.
During the changed of to genLang, I have seen quite a number of
strange things (and written it on my list).

When I get some air, I will start the build project by updating the
dependency chart...we need that to see if we can modularize parts of main.

Jan I.

> Best regards, Oliver.
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**<>
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message