Comment 1 for bug 938417

On Wed, 22 Feb 2012, Daniel van Vugt wrote:

> Public bug reported:
>
> The exact locations of the failures seems to change depending on the
> value of N. Not surprising as they are effectively race conditions.
>
> It would be really nice if we could have parallel builds working because
> it would speed up development, permanently.
>

There's only two that I know of so far.

The first is one when building po files. I think we need to make them
depend on the OUTPUT and not on the TARGET.

The second is core-xml-file . I think that add_custom_command for
core_options.c|h does not use OUTPUT, so that would cause the dependency
failure there.

> Most likely, all the reasons for the build failures will be missing
> dependencies. i.e. Some target requires another target in order to
> build, but fails to declare that dependency formally in CMakeLists.txt
>
> ** Affects: compiz-core
> Importance: Medium
> Status: Triaged
>
> ** Changed in: compiz-core
> Status: New => Incomplete
>
> ** Changed in: compiz-core
> Status: Incomplete => Triaged
>
> ** Changed in: compiz-core
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are a member of Compiz
> Maintainers, which is the registrant for Compiz Core.
> https://bugs.launchpad.net/bugs/938417
>
> Title:
> lp:compiz-core fails parallel builds (make -jN)
>
> Status in Compiz Core:
> Triaged
>
> Bug description:
> The exact locations of the failures seems to change depending on the
> value of N. Not surprising as they are effectively race conditions.
>
> It would be really nice if we could have parallel builds working
> because it would speed up development, permanently.
>
> Most likely, all the reasons for the build failures will be missing
> dependencies. i.e. Some target requires another target in order to
> build, but fails to declare that dependency formally in CMakeLists.txt
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/compiz-core/+bug/938417/+subscriptions
>