>From the XDCtools team: ================================ The linker command file is generated using a template that is provided by the platform, IF the user does not explicitly provide one. You can supply a linker command file template via: 1. The -linkTemplate option to the configuro tool; "xs xdc.tools.configuro -linkTemplate ..." (see http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/tools/configuro/package.html) or, 2. If you are using the xdc build engine, the optional attribute linkTemplate passed to addExecutable (see http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/bld/Executable.html#.Attrs).
Platforms usually reference the template contained in the target's package and in the case of TI targets the template is ti/targets/linkcmd.xdt. So, while not the best answer, it is possible to copy the current template ($(XDC_INSTALL_DIR)/packages/ti/targets/linkcmd.xdt) to some other location, modify it to insert the appropriate UNION statements, and use one of the methods above to override the default ti/targets/linkcmd.xdt template. ================================ Chris > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > ] On Behalf Of Itay Chamiel > Sent: Thursday, October 23, 2008 5:46 AM > To: Vladimir Pantelic > Cc: [email protected] > Subject: RE: Codec Engine Code Overlays with more than one codec? > > > Vladimir Pantelic wrote: > > > what about removing the overlay related stuff from the > codecs link.xdt > and adding them UNIONised in the servers link.cmd file? > > Well, that would work, but it would be rather ugly. As far as I have > seen with XDC so far, third-party packages are basically a closed unit > which the integrator is not supposed to modify. So, I don't like this > because (A) I need to touch files that conceptually should not be > touched by me, (B) the codec package becomes unusable as a self > contained unit - any project using it must manually add the relevant > lines to the link.cmd file, (C) I need to do this manual process every > time the third party releases a new version of the codec, and > (D) I need > to do an extra manual process every time I add or remove a > codec from my > project. > > I understand that this is might be the only way to accomplish > this, but > I'm surprised at TI for going to such great lengths to make everything > self-contained, nice and automatic (see the wiki page I > linked to in my > original post to see the effort done to make the job trivial for the > integrator) but leaving this whole issue kind of half-baked. > > -itay > -- > Itay Chamiel > Software Engineer > Mango DSP > itayc at mangodsp.com > > > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
