Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 349251

Summary:	The build rules for applications using custom libs should kick off a build of the src/makefile.libs if any of the librarys' source files change
Product:	[Technology] RTSC	Reporter:	Alan DeMars <ademars>
Component:	Core	Assignee:	Dave Russo <d-russo>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	dfriedland
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Alan DeMars

2011-06-13 19:22:13 EDT

Build Identifier: 3.22.01

Currently, if an application is built against a custom library, and one of the BIOS/IPC module C files is changed, a build of the application does NOT cause a rebuild of the custom library.

Perhaps an API to SourceDir that allows the component library makefile generator to add a list of dependent source files to the 'all' goal...

Reproducible: Always

Steps to Reproduce:
1. Build any example using BIOS.libType = BIOS.LibType_Custom.
2. 'touch' one of the component module C files (ie Task.c)
3. Start application 'Build'. 
4. Notice nothing happens.

Comment 1 Alan DeMars

2011-06-24 17:35:40 EDT

One possibility is to simply have generated makefile include a generated makefile.deps file if it exists.

Comment 2 Alan DeMars

2011-08-19 18:04:46 EDT

Another possibility:

-always call underlying makefile (make it an option to SourceDir).

Comment 3 Alan DeMars

2011-09-09 18:00:20 EDT

Must work with package.bld so that developers testcases depend on the module sources.

We can't have config only trigger the make. Must be in generated package.mak.

Comment 4 Dave Russo

2011-12-05 17:30:18 EST

fixed in xdc-y13

Comment 5 Dave Russo

2016-01-12 00:49:24 EST

closing bugs that have been in resolved state for more than a year

Comment 6 Dave Russo

2016-02-17 18:43:14 EST

in fixed state for more than one year