Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Real-Time Software Components (RTSC) » Package Compatibility Keys
Package Compatibility Keys [message #641311] Wed, 24 November 2010 16:01 Go to next message
Patrick Geremia is currently offline Patrick Geremia
Messages: 79
Registered: July 2009
Member
I am using RTSC as a build system and I have a package that contains
various functions which constitutes my the public API of that package.

Assuming the first release of the package is 1.0.0.0, am I correct in
stating that if my public API changes (which imply a person consuming my
package has to rewrite his code), then the I need to increase M which
would lead to version 2.0.0.0?

Also, when I create a RTSC release, how can I retrieve the compatibility
key so as to create a release named myrelease_1.0.0.0.tar.gz assuming my
package has the compatibility key is 1.0.0.0.


Regards
Patrick Geremia
Re: Package Compatibility Keys [message #641331 is a reply to message #641311] Wed, 24 November 2010 22:30 Go to previous messageGo to next message
Sasha Slijepcevic is currently offline Sasha Slijepcevic
Messages: 86
Registered: July 2009
Member
Patrick,
you are correct, when a package consumer must rewrite his source code, M must be incremented. Here is more:
http://rtsc.eclipse.org/docs-tip/Compatibility_Keys

When building releases in package.bld, you are using 'Pkg' object, which is an alias for xdc.bld.PackageContent. That object has a parameter version, which is what you are looking for.
Re: Package Compatibility Keys [message #641707 is a reply to message #641311] Fri, 26 November 2010 17:42 Go to previous message
Dave Russo is currently offline Dave Russo
Messages: 172
Registered: July 2009
Senior Member
On 11/24/2010 1:01 PM, Patrick Geremia wrote:
> I am using RTSC as a build system and I have a package that contains
> various functions which constitutes my the public API of that package.
>
> Assuming the first release of the package is 1.0.0.0, am I correct in
> stating that if my public API changes (which imply a person consuming my
> package has to rewrite his code), then the I need to increase M which
> would lead to version 2.0.0.0?
Yes.

During configuration, all packages contributing content are scanned to
determine if there are any that were built using your package. If the
config tool detects that some package, say P, was built with 1.x.y of
your package and 2.a.b is contributing to the configuration, then the
configuration step will fail with an error indicating the package P must
be rebuilt with version 2.a.b.

>
> Also, when I create a RTSC release, how can I retrieve the compatibility
> key so as to create a release named myrelease_1.0.0.0.tar.gz assuming my
> package has the compatibility key is 1.0.0.0.
>
A package's compatibility key can be obtained either as part of a build
script
( http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/bld/PackageC ontents.html#version)
or a program's configuration script
(http://rtsc.eclipse.org/docs-tip/XDCscript_-_Package-Object .%24vers).

During the execution of a build script the only compatibility key
available is that of the package being built (the one contained in the
package.xdc file). During configuration, the compatibility key of any
loaded package is available (this allows a package to check the versions
of any prerequisite packages and handle incompatibilities as necessary).

>
> Regards
> Patrick Geremia
Previous Topic:Release notification for XDCtools 3.20.05
Next Topic:linking with DSP/BIOS 5
Goto Forum:
  


Current Time: Thu Aug 21 18:12:27 EDT 2014

Powered by FUDForum. Page generated in 0.02536 seconds