| Summary: | XDCtools should support sharing of configuration among application builds | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Amit Mookerjee <amitm> |
| Component: | Core | Assignee: | Dave Russo <d-russo> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | dfriedland, sascha |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | target:3.23.01 | ||
|
Description
Amit Mookerjee
Pkg.addConfiguration() allows one to create a configuration that can be shared (among exes in the same package). - verified using 3.23.01.39
The following code from package.bld demonstrate the test I used to verify that one configuration can be used for multiple executables:
var assembly = Pkg.addConfiguration('hello', targ, targ.platform, {
cfgScript: "hello.cfg", profile: "release", prelink: true
});
var prog = Pkg.addExecutable('hello', targ, targ.platform, {
rtsName: null, profile: "release", sharedCfg: assembly.getBaseName()
});
prog.addObjects(["hello.c"]);
var prog2 = Pkg.addExecutable('hello2', targ, targ.platform, {
rtsName: null, profile: "release", sharedCfg: assembly.getBaseName()
});
prog2.addObjects(["hello2.c"]);
The output verifies that we build the configuration only once and reuse it when building executables:
making package.mak (because of package.bld) ...
generating interfaces for package assembly.test1 (because package/package.xdc.inc is older than package.xdc) ...
configuring hello.pe64P from package/cfg/hello_pe64P.cfg ...
cle64P package/cfg/hello_pe64P.c ...
lnke64P hello.pe64P ...
cle64P hello.c ...
lnke64P hello.xe64P ...
cle64P hello2.c ...
lnke64P hello2.xe64P ...
all files complete.
xdctools 3.23.05 GA is available from here: http://www.sanb.design.ti.com/tisb_releases/XDCtools/3_23_05_61/ |