In 3.4 we support simple cycles in which
all bundles are binary except for 1 which needs to be compiled.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=208011#c22
In this situation, you could compile
A & B first and then separately compile A' with "allowBinaryCycles=true".
I believe your case is an instance of
https://bugs.eclipse.org/bugs/show_bug.cgi?id=215030 where the cycle is
purely runtime and doesn't exist at compile time.
-Andrew
David Olsen <David.Olsen@xxxxxxxxxx> Sent by: pde-build-dev-bounces@xxxxxxxxxxx
05/28/2008 12:49 PM
Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
Re: [pde-build-dev] cyclic dependencies
in PDE build (but there are no cycles...)
A fragment is an extension of its host plugin and, in some respects, is
not really a separate entity by itself. So the host plugin inherits
all the dependencies that are listed in the fragment. Therefore,
if you have
> Fragment A' with A as a host
> B has a dependency to A
> A' has a dependency to B
then you have a circular dependency. A (via A') depends on B and
B depends on A.
> Is there a solution (maybe build order, something else...) that I
am not aware
> of, or is this something without a solution and we need to change
the
> fragment to a plugin?
The problem can't be fixed by changing the build order. The two solutions
I can think of are:
1. Remove B's dependency on A. (Maybe by moving parts of B to A'.)
2. Change A' from a fragment to a plugin. _______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev