Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367540 - When referred project changes, this does not trigger a rebuild of the depended project
Summary: When referred project changes, this does not trigger a rebuild of the depende...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: 8.1.0   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-24 10:02 EST by Boian Petkantchin CLA
Modified: 2020-09-04 15:26 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Boian Petkantchin CLA 2011-12-24 10:02:14 EST
Build Identifier: Version: Indigo Service Release 1 | Build id: 20110916-0149

If we have two project, one of them a shared library and the other is an executable. Both of them are using the Internal Builder. The executable project references the shared library project. I achieve this through "Project -> Properties -> Project References" and "Project -> Properties -> C/C++ General -> Paths and Symbols -> References". In the latter case, the active build configuration is referred. When a source file is changed in the shared library and a build of all project is ordered, the library is rebuild, but the executable is not. The expected behavior is that the dependent executable project is also rebuild.
I experience this problem both on Windows XP and Ubuntu with the same version.
This seams to be related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=205113, but here the rebuild does not happen even if the file is changed inside Eclipse.

Reproducible: Always

Steps to Reproduce:
1. Create a C++ shared library project, that uses the Internal Builder.
2. Create a C++ executable project, that uses the Internal Builder.
3. Create a project dependency through "Project -> Properties -> Project References" and "Project -> Properties -> C/C++ General -> Paths and Symbols -> References", by referring the shared library in the executable project.
4. Add some dummy source files in the projects.
5. Order "Project -> Build All".
6. Change some of the source files in the shared library project.
7. Order "Project -> Build All".