Bug 175864 - Problems building multiple configs at once
Summary: Problems building multiple configs at once
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-28 12:16 EST by Andrew Niefer CLA
Modified: 2022-11-18 17:16 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Niefer CLA 2007-02-28 12:16:56 EST
PDE/Build resolves its state with all the configurations at once.
Consider bundle A with platform filter os=gtk and exports a package.
Bundle B with platform filter os=win32 exports the same package.

Bundle C imports this package.
At compile time all configs are resolved at once, there is no way to know which of A or B will get wired to C.  If the package contains method signatures that are different in A & B, then C has a problem at runtime if it was compiled against the wrong bundle.

A similar problem exists with platform dependent fragments.  This problem appeared in bug 175500.

If C claims to be platform independent, then it shouldn't be using methods that are different on different platforms.  I'm not sure there is anything we can do about this case.

However, if C does have a platform filter, then we may have to resolve the state multiple times to get this right.
Comment 1 Lars Vogel CLA 2018-12-03 09:13:14 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 2 Lars Vogel CLA 2018-12-03 09:14:07 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 3 Eclipse Genie CLA 2020-11-27 09:08:06 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2022-11-18 17:16:12 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.