| To Rebuild the Package ... or not [message #3282] |
Tue, 19 May 2009 15:44  |
Eclipse User |
|
|
|
This seems like a naive question, but I haven't been able to figure out
the answer on my own.
I want to create a RTSC package for an algorithm I've written. I've used
the RTSC Codec Packaging wizard to create the necessary files (.xdc, .xs,
bld) to describe my package. I then ran the TI XDC tools to create the
package. At a later point in time, I went back and fixed some errata in my
algorithm; then rebuilt the library.
Finally, here's the question: If I haven't changed any interfaces, do I
still need to rerun XDC to recreate the package, or can I simply replace
the library in the package.
Personally, I think recreating the package is a better choice, but I'm
working in CCSv3.3 and my process would be less error prone if I could
skip the XDC step. (BTW, any chance CCSv4 and XDC work better together?)
|
|
|
| Re: To Rebuild the Package ... or not [message #3316 is a reply to message #3282] |
Wed, 20 May 2009 10:34  |
| Eclipse User |
|
|
|
sgspecker wrote:
> This seems like a naive question, but I haven't been able to figure out
> the answer on my own.
>
> I want to create a RTSC package for an algorithm I've written. I've used
> the RTSC Codec Packaging wizard to create the necessary files (.xdc,
> .xs, bld) to describe my package. I then ran the TI XDC tools to create
> the package. At a later point in time, I went back and fixed some errata
> in my algorithm; then rebuilt the library.
>
> Finally, here's the question: If I haven't changed any interfaces, do I
> still need to rerun XDC to recreate the package, or can I simply replace
> the library in the package.
If the changes you made do not cause another file to be referenced
(e.g., you did not change any #include's or reference any new modules in
the implementation of the algorithm) and you did not change and
interfaces, your modified package will probably work.
BUT: timestamps of the files within the package will be wrong and the
RTSC tools will not be able to distinguish between the new fixed package
and the old broken package. This can cause problems for users of your
package who have no way to know if they have a good release or not.
Bottom line: you can modify packages "by hand" within your development
environment, but you should _always_ run "xdc release" prior to letting
the package out "into the wild".
>
> Personally, I think recreating the package is a better choice, but I'm
> working in CCSv3.3 and my process would be less error prone if I could
> skip the XDC step. (BTW, any chance CCSv4 and XDC work better together?)
>
What makes your process error prone when running "xdc release"? Perhaps
there is something that can be changed in the tool to avoid having to
avoid using it.
|
|
|
Powered by
FUDForum. Page generated in 0.03999 seconds
Home