Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community Forumsreleasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/525688/#msg_525688
package are built. Is this the normal behavior?
To be more explicit, I have a package that generates a dozen of library
variants but I would like to my release to include only 2 variants.
When making the release, all libraries are generated even though I need
only 2 for the release.
--
Patrick Geremia
Texas Instruments (http://www.ti.com)
Phone: +33 4 93 22 26 33
Email: p-geremia@ti.com
Availability: http://meetwith.me/patrickgeremia]]>Patrick Geremia2010-04-07T13:11:07-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/525722/#msg_525722
as being a .zip file containing a unique subset of files from the built
package.
Every package has a "default" release and this release contains all
libraries added. But, you can define a second release that contains
just the two libraries that you want.
Alternatively, if you don't want to create two releases, it's also
possible to eliminate the unnecessary libraries using a "release
script". A release script is a script that can arbitrarily add, remove,
or change any file that is added to a release (before the .zip is
actually created). In effect, release scripts are passed a list of all
the files to be added to the .zip and the release script can filter it
before it's used to create the .zip.
The following example release script removes files whose names end with
"foo":
var files = [];
for (var i = 0; i < Manifest.files.length; i++) {
var fname = Manifest.files[i];
if (fname.match(/foo$/) != null) {
continue;
}
files.push(fname);
}
/* include ONLY those files named in the files array */
Manifest.files = files;
On 4/7/2010 6:11 AM, Patrick Geremia wrote:
> I tried to release a package but I noticed that all the variants of my
> package are built. Is this the normal behavior?
>
> To be more explicit, I have a package that generates a dozen of library
> variants but I would like to my release to include only 2 variants.
> When making the release, all libraries are generated even though I need
> only 2 for the release.
>]]>Dave Russo2010-04-07T15:02:01-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/525723/#msg_525723
Subject: Re: releasing a package
From: dave russo <d-russo@ti.com>
To:
Date: Wed Apr 07 2010 17:02:01 GMT+0200 (CEST)
> Packages can produce more than one release. You can think of a release
> as being a .zip file containing a unique subset of files from the built
> package.
>
> Every package has a "default" release and this release contains all
> libraries added. But, you can define a second release that contains
> just the two libraries that you want.
>
> When you add a library to a package you can specify what releases should
> contain it; see the releases attribute of
> http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/bld/Library. html#.Attrs
>
> Alternatively, if you don't want to create two releases, it's also
> possible to eliminate the unnecessary libraries using a "release
> script". A release script is a script that can arbitrarily add, remove,
> or change any file that is added to a release (before the .zip is
> actually created). In effect, release scripts are passed a list of all
> the files to be added to the .zip and the release script can filter it
> before it's used to create the .zip.
>
> The following example release script removes files whose names end with
> "foo":
> var files = [];
> for (var i = 0; i < Manifest.files.length; i++) {
> var fname = Manifest.files[i];
>
> if (fname.match(/foo$/) != null) {
> continue;
> }
> files.push(fname);
> }
>
> /* include ONLY those files named in the files array */
> Manifest.files = files;
>
> So, you can:
> 1. create a release script that simply deletes the unnecessary
> libraries; see
> http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/bld/Manifest .html
> 2. specify a release script when you create a release; see
> http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/bld/Release. html#.Attrs
> 3. re-define the default release to be this newly created release;
> see
> http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/bld/PackageC ontents.html#default.Release
>
>
>
> On 4/7/2010 6:11 AM, Patrick Geremia wrote:
>> I tried to release a package but I noticed that all the variants of my
>> package are built. Is this the normal behavior?
>>
>> To be more explicit, I have a package that generates a dozen of library
>> variants but I would like to my release to include only 2 variants.
>> When making the release, all libraries are generated even though I need
>> only 2 for the release.
>>
Dave,
ok thanks.
So if I understand correctly, all libraries of the package will be
created regardless of whether a release needs a subset of these libraries?
--
Patrick Geremia
Texas Instruments (http://www.ti.com)
Phone: +33 4 93 22 26 33
Email: p-geremia@ti.com
Availability: http://meetwith.me/patrickgeremia]]>Patrick Geremia2010-04-07T15:06:39-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/525729/#msg_525729
On 4/7/2010 8:06 AM, Patrick Geremia wrote:
> -------- Original Message --------
> Subject: Re: releasing a package
> From: dave russo <d-russo@ti.com>
> To:
> Date: Wed Apr 07 2010 17:02:01 GMT+0200 (CEST)
>
>> Packages can produce more than one release. You can think of a release
>> as being a .zip file containing a unique subset of files from the
>> built package.
[snip]
>
> ok thanks.
> So if I understand correctly, all libraries of the package will be
> created regardless of whether a release needs a subset of these libraries?
>
If you create a single release and remove the files via a reelase
script, yes.
If you create two releases, you can the simply build the "two library"
rlease. Recall that xdc is just make, so any file built can be
explicitly specified in the command line and _only_ the libraries needed
for the specified release will be built.
You can also create your own goals, say ".lite-release", which only has
the two library release as a prerequisite. By adding this goal to all
packages you can then build multiple packages with the goal
".lite-release" and only build what you need.]]>Dave Russo2010-04-07T15:18:24-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/525919/#msg_525919
Subject: Re: releasing a package
From: dave russo <d-russo@ti.com>
To:
Date: Wed Apr 07 2010 17:18:24 GMT+0200 (CEST)
> Actually
>
> On 4/7/2010 8:06 AM, Patrick Geremia wrote:
>> -------- Original Message --------
>> Subject: Re: releasing a package
>> From: dave russo <d-russo@ti.com>
>> To:
>> Date: Wed Apr 07 2010 17:02:01 GMT+0200 (CEST)
>>
>>> Packages can produce more than one release. You can think of a release
>>> as being a .zip file containing a unique subset of files from the
>>> built package.
> [snip]
>>
>> ok thanks.
>> So if I understand correctly, all libraries of the package will be
>> created regardless of whether a release needs a subset of these
>> libraries?
>>
> If you create a single release and remove the files via a reelase
> script, yes.
>
> If you create two releases, you can the simply build the "two library"
> rlease. Recall that xdc is just make, so any file built can be
> explicitly specified in the command line and _only_ the libraries needed
> for the specified release will be built.
>
> You can also create your own goals, say ".lite-release", which only has
> the two library release as a prerequisite. By adding this goal to all
> packages you can then build multiple packages with the goal
> ".lite-release" and only build what you need.
I still do not get it.
My package has a maximum of 12 libraries (8 for C6x target and 4 for gnu
target).
I wanted to create
- a release containing sources only.
- a release containing c6x debug libs
- a release containing c6x release libs
- a release containing gnu libs
see code below:
pkg.attrs.compress = true;
var files = listFiles("h");
for (var i=0; i < files.length; i++)
{
pkg.otherFiles[pkg.otherFiles.length++] = files[i];
}
var relName = pkgName + "_c6x_release";
var c6xRelease = pkg.addRelease(relName);
c6xRelease.attrs.label = "c6x release";
print("ReleaseGoal: " + relName + ".tar.gz")
var relName = pkgName + "_c6x_debug";
var c6xDebug = pkg.addRelease(relName);
c6xDebug.attrs.label = "c6x debug";
print("ReleaseGoal: " + relName + ".tar.gz")
var relName = pkgName + "_host";
var host = pkg.addRelease(relName);
host.attrs.label = "host";
print("ReleaseGoal: " + relName + ".tar.gz")
var relName = pkgName + "_src";
var src = pkg.addRelease(relName);
src.attrs.label = "src";
src.attrs.exportSrc = true;
src.otherFiles[src.otherFiles.length++] = "config.bld";
src.otherFiles[src.otherFiles.length++] = "package.bld";
var files = listFiles("c",srcDir);
for (var i=0; i < files.length; i++)
{
src.otherFiles[src.otherFiles.length++] = files[i];
}
print("ReleaseGoal: " + relName + ".tar.gz")
Here is how I specify which lib goes into which release
From what I understand, any library I add to my package will be added
to the default release in addition to what I specify with the lines
libAttrs.releases
So regardless of which release I want to create a default release will
be created containing my 12 libraries.
so when I run
xdc ti_wbi_umts_rac_raccm_host
all 12 libraries are generated even though this release contains only 4.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"=
>
<title></title>
</head>
<body bgcolor=3D"#ffffff" text=3D"#000000">
<blockquote cite=3D"mid:4BBD9E83.5090605@ti.com" type=3D"cite"><span
style=3D"color: rgb(0, 0, 0);" class=3D"headerSpan">-------- Original
Message --------<br>
Subject: Re: releasing a package<br>
From: Patrick Geremia <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:p= -geremia@ti.com"><p-geremia@ti.com></a><br>
To: <br>
Date: Thu Apr 08 2010 11:14:43 GMT+0200 (CEST)<br>
<br>
</span>-------- Original Message --------
<br>
Subject: Re: releasing a package
<br>
From: dave russo <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:d-russ= o@ti.com"><d-russo@ti.com></a>
<br>
To:
<br>
Date: Wed Apr 07 2010 17:18:24 GMT+0200 (CEST)
<br>
<br>
<blockquote type=3D"cite">Actually
<br>
<br>
On 4/7/2010 8:06 AM, Patrick Geremia wrote:
<br>
<blockquote type=3D"cite">-------- Original Message --------
<br>
Subject: Re: releasing a package
<br>
From: dave russo <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:d-russ= o@ti.com"><d-russo@ti.com></a>
<br>
To:
<br>
Date: Wed Apr 07 2010 17:02:01 GMT+0200 (CEST)
<br>
<br>
<blockquote type=3D"cite">Packages can produce more than one
release. You can think of a release
<br>
as being a .zip file containing a unique subset of files from the
<br>
built package.
<br>
</blockquote>
</blockquote>
[snip]
<br>
<blockquote type=3D"cite"><br>
ok thanks.
<br>
So if I understand correctly, all libraries of the package will be
<br>
created regardless of whether a release needs a subset of these
libraries?
<br>
<br>
</blockquote>
If you create a single release and remove the files via a reelase
script, yes.
<br>
<br>
If you create two releases, you can the simply build the "two library"
rlease.=C2=A0 Recall that xdc is just make, so any file built can be
explicitly specified in the command line and _only_ the libraries
needed for the specified release will be built.
<br>
<br>
You can also create your own goals, say ".lite-release", which only has
the two library release as a prerequisite.=C2=A0 By adding this goal to a=
ll
packages you can then build multiple packages with the goal
".lite-release" and only build what you need.
<br>
</blockquote>
<br>
I still do not get it.
<br>
My package has a maximum of 12 libraries (8 for C6x target and 4 for
gnu target).
<br>
I wanted to create
<br>
- a release containing sources only.
<br>
- a release containing c6x debug libs
<br>
- a release containing c6x release libs
<br>
- a release containing gnu libs
<br>
<br>
see code below:
<br>
<br>
=C2=A0=C2=A0 pkg.attrs.compress =3D true;
<br>
=C2=A0=C2=A0 var files =3D listFiles("h");
<br>
=C2=A0=C2=A0 for (var i=3D0; i < files.length; i++)
<br>
=C2=A0=C2=A0 {
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 pkg.otherFiles[pkg.otherFiles.length=
++] =3D files[i];
<br>
=C2=A0=C2=A0 }
<br>
<br>
=C2=A0=C2=A0 var relName =3D pkgName + "_c6x_release";
<br>
=C2=A0=C2=A0 var c6xRelease =3D pkg.addRelease(relName);
<br>
=C2=A0=C2=A0 c6xRelease.attrs.label =3D "c6x release";
<br>
=C2=A0=C2=A0 print("ReleaseGoal: " + relName + ".tar.gz")
<br>
=C2=A0=C2=A0 =C2=A0=C2=A0 var relName =3D pkgName + "_c6x_debug";
<br>
=C2=A0=C2=A0 var c6xDebug =3D pkg.addRelease(relName);
<br>
=C2=A0=C2=A0 c6xDebug.attrs.label =3D "c6x debug";
<br>
=C2=A0=C2=A0 print("ReleaseGoal: " + relName + ".tar.gz")
<br>
=C2=A0=C2=A0 =C2=A0=C2=A0 var relName =3D pkgName + "_host";
<br>
=C2=A0=C2=A0 var host =3D pkg.addRelease(relName);
<br>
=C2=A0=C2=A0 host.attrs.label =3D "host";
<br>
=C2=A0=C2=A0 print("ReleaseGoal: " + relName + ".tar.gz")
<br>
=C2=A0=C2=A0 =C2=A0=C2=A0 var relName =3D pkgName + "_src";
<br>
=C2=A0=C2=A0 var src =3D pkg.addRelease(relName);
<br>
=C2=A0=C2=A0 src.attrs.label =3D "src";
<br>
=C2=A0=C2=A0 src.attrs.exportSrc =3D true;
<br>
=C2=A0=C2=A0 src.otherFiles[src.otherFiles.length++] =3D "config.bld";
<br>
=C2=A0=C2=A0 src.otherFiles[src.otherFiles.length++] =3D "package.bld";
<br>
=C2=A0=C2=A0 var files =3D listFiles("c",srcDir);
<br>
=C2=A0=C2=A0 for (var i=3D0; i < files.length; i++)
<br>
=C2=A0=C2=A0 {
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 src.otherFiles[src.otherFiles.length=
++] =3D files[i];
<br>
=C2=A0=C2=A0 }
<br>
=C2=A0=C2=A0 print("ReleaseGoal: " + relName + ".tar.gz")
<br>
<br>
Here is how I specify which lib goes into which release
<br>
<br>
=C2=A0=C2=A0=C2=A0=C2=A0if ((build.targets[target].name =3D=3D "C64P_big_=
endian") ||
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (build.targets[target].n=
ame =3D=3D "C64P"))
<br>
=C2=A0=C2=A0=C2=A0=C2=A0{
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 libAttrs.copts +=3D "-fb=3D./"=
+ pkg.libDir + name + "/" + srcDir +
" ";
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 libAttrs.copts +=3D "-ft=3D./"=
+ pkg.libDir + name + "/" + srcDir +
" ";
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 libAttrs.copts +=3D "-ff=3D./"=
+ pkg.libDir + name + "/" + srcDir +
" ";
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 if (profile.search("release")!=
=3D-1)
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 {
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0 libAtt=
rs.releases=3D[c6xRelease];
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 else
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 {
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0 libAtt=
rs.releases=3D[c6xDebug];
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }
<br>
=C2=A0=C2=A0=C2=A0=C2=A0}
<br>
=C2=A0=C2=A0=C2=A0=C2=A0else
<br>
=C2=A0=C2=A0=C2=A0=C2=A0{
<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 libAttrs.releases=3D[host];
<br>
=C2=A0=C2=A0=C2=A0=C2=A0}
<br>
<br>
=46rom what I understand, any library I add to my package will be added
to the default release in addition to what I specify with the lines
libAttrs.releases
<br>
<br>
So regardless of which release I want to create a default release will
be created containing my 12 libraries.
<br>
so when I run
<br>
xdc ti_wbi_umts_rac_raccm_host
<br>
all 12 libraries are generated even though this release contains only
4.
<br>
<br>
<br>
</blockquote>
Dave,<br>
<br>
the code I pasted in my previous post did not show up very nicely.<br>
I am trying again in html. (I am also attaching my package.bld file).<br>=
> So regardless of which release I want to create a default release will
> be created containing my 12 libraries.
Unfortunately, yes. This is something I'd like to change but it
potentially breaks compatibility with existing build scripts.
I suppose we can add a property to packages that indicates that the
default release should not "be greedy" and only implicitly add libraries
that are not already assigned to a release; we want to avoid adding a
library that does not find it's way into _some_ release.
> so when I run
> xdc ti_wbi_umts_rac_raccm_host
> all 12 libraries are generated even though this release contains only 4.
>
It shouldn't. If ti_wbi_umts_rac_raccm_host only includes 4 libraries,
only those four libraries should be built by make before building the
ti_wbi_umts_rac_raccm_host goal.
>]]>Dave Russo2010-04-08T15:28:30-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/526684/#msg_526684
>
>
> On 4/8/2010 2:14 AM, Patrick Geremia wrote:
>>
>> From what I understand, any library I add to my package will be added
>> to the default release in addition to what I specify with the lines
>> libAttrs.releases
>>
> Right.
>
>> So regardless of which release I want to create a default release will
>> be created containing my 12 libraries.
> Unfortunately, yes. This is something I'd like to change but it
> potentially breaks compatibility with existing build scripts.
>
> I suppose we can add a property to packages that indicates that the
> default release should not "be greedy" and only implicitly add libraries
> that are not already assigned to a release; we want to avoid adding a
> library that does not find it's way into _some_ release.
>
>> so when I run
>> xdc ti_wbi_umts_rac_raccm_host
>> all 12 libraries are generated even though this release contains only 4.
>>
> It shouldn't. If ti_wbi_umts_rac_raccm_host only includes 4 libraries,
> only those four libraries should be built by make before building the
> ti_wbi_umts_rac_raccm_host goal.
>
>
>>
sorry I meant the following: when I want to make the release
ti_wbi_umts_rac_raccm_host by running the command xdc
release,ti_wbi_umts_rac_raccm_host , all 12 libraries will be build (as
they part of the default release) even though the
ti_wbi_umts_rac_raccm_host release contains only 4 libraries.
--
Patrick Geremia
Texas Instruments (http://www.ti.com)
Phone: +33 4 93 22 26 33
Email: p-geremia@ti.com
Availability: http://meetwith.me/patrickgeremia]]>Patrick Geremia2010-04-12T15:23:55-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/526689/#msg_526689
> dave russo wrote:
>>
>>
>> On 4/8/2010 2:14 AM, Patrick Geremia wrote:
>>>
>>> From what I understand, any library I add to my package will be added
>>> to the default release in addition to what I specify with the lines
>>> libAttrs.releases
>>>
>> Right.
>>
>>> So regardless of which release I want to create a default release will
>>> be created containing my 12 libraries.
>> Unfortunately, yes. This is something I'd like to change but it
>> potentially breaks compatibility with existing build scripts.
>>
>> I suppose we can add a property to packages that indicates that the
>> default release should not "be greedy" and only implicitly add
>> libraries that are not already assigned to a release; we want to avoid
>> adding a library that does not find it's way into _some_ release.
>>
>>> so when I run
>>> xdc ti_wbi_umts_rac_raccm_host
>>> all 12 libraries are generated even though this release contains only 4.
>>>
>> It shouldn't. If ti_wbi_umts_rac_raccm_host only includes 4
>> libraries, only those four libraries should be built by make before
>> building the ti_wbi_umts_rac_raccm_host goal.
>>
>>
>>>
>
> sorry I meant the following: when I want to make the release
> ti_wbi_umts_rac_raccm_host by running the command xdc
> release,ti_wbi_umts_rac_raccm_host , all 12 libraries will be build (as
> they part of the default release) even though the
> ti_wbi_umts_rac_raccm_host release contains only 4 libraries.
>
this is quite annoying. The only possibilities I see today are
1. not use the RTSC release capabilities. Implement it using external
scripts to generate the zips.
2. or pass the release goal to XDC as XDCARGS and only generate what I
need to generate for that release. (this is what I have done to generate
a release that contains only sources and the build system).
Any other ideas?
Will this problem be addressed in a subsequent release?
--
Patrick Geremia
Texas Instruments (http://www.ti.com)
Phone: +33 4 93 22 26 33
Email: p-geremia@ti.com
Availability: http://meetwith.me/patrickgeremia]]>Patrick Geremia2010-04-12T15:31:57-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/526720/#msg_526720
>>>>
>>> It shouldn't. If ti_wbi_umts_rac_raccm_host only includes 4
>>> libraries, only those four libraries should be built by make before
>>> building the ti_wbi_umts_rac_raccm_host goal.
>>>
>>>
>>>>
>>
>> sorry I meant the following: when I want to make the release
>> ti_wbi_umts_rac_raccm_host by running the command xdc
>> release,ti_wbi_umts_rac_raccm_host , all 12 libraries will be build
>> (as they part of the default release) even though the
>> ti_wbi_umts_rac_raccm_host release contains only 4 libraries.
>>
>
> this is quite annoying. The only possibilities I see today are
> 1. not use the RTSC release capabilities. Implement it using external
> scripts to generate the zips.
> 2. or pass the release goal to XDC as XDCARGS and only generate what I
> need to generate for that release. (this is what I have done to generate
> a release that contains only sources and the build system).
>
> Any other ideas?
If your package only builds libraries, the following should work:
1. first build the .interfaces goal (this ensure that the package's
meta data exists)
2. build _just_ the release archive that you are interested in
In your case:
xdc .interfaces
xdc ti_wbi_umts_rac_raccm_host.zip
This should build only the files that are required for this .zip file.
> Will this problem be addressed in a subsequent release?
>
I've filed "Bug 308900 - can't create individual release without
building a bunch of unnecessary libraries" to track this issue; see https://bugs.eclipse.org/bugs/show_bug.cgi?id=308900
I added you to the CC list so you will get updates whenever this bug's
status changes.]]>Dave Russo2010-04-12T17:42:39-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/527148/#msg_527148
Subject: Re: releasing a package
From: dave russo <d-russo@ti.com>
To:
Date: Mon Apr 12 2010 19:42:39 GMT+0200 (CEST)
>
>
> On 4/12/2010 8:31 AM, Patrick Geremia wrote:
>>>>>
>>>> It shouldn't. If ti_wbi_umts_rac_raccm_host only includes 4
>>>> libraries, only those four libraries should be built by make before
>>>> building the ti_wbi_umts_rac_raccm_host goal.
>>>>
>>>>
>>>>>
>>>
>>> sorry I meant the following: when I want to make the release
>>> ti_wbi_umts_rac_raccm_host by running the command xdc
>>> release,ti_wbi_umts_rac_raccm_host , all 12 libraries will be build
>>> (as they part of the default release) even though the
>>> ti_wbi_umts_rac_raccm_host release contains only 4 libraries.
>>>
>>
>> this is quite annoying. The only possibilities I see today are
>> 1. not use the RTSC release capabilities. Implement it using external
>> scripts to generate the zips.
>> 2. or pass the release goal to XDC as XDCARGS and only generate what I
>> need to generate for that release. (this is what I have done to generate
>> a release that contains only sources and the build system).
>>
>> Any other ideas?
> If your package only builds libraries, the following should work:
> 1. first build the .interfaces goal (this ensure that the package's
> meta data exists)
> 2. build _just_ the release archive that you are interested in
>
> In your case:
> xdc .interfaces
> xdc ti_wbi_umts_rac_raccm_host.zip
>
> This should build only the files that are required for this .zip file.
>
>> Will this problem be addressed in a subsequent release?
>>
> I've filed "Bug 308900 - can't create individual release without
> building a bunch of unnecessary libraries" to track this issue; see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=308900
>
> I added you to the CC list so you will get updates whenever this bug's
> status changes.
>
>
>
>
>
>
Dave,
are you sure you need the .zip?
In my case, I build a compressed tarball (.tar.gz), the release name is
not ti_wbi_umts_rac_raccm_host.tar.gz but ti_wbi_umts_rac_raccm_host
I checked again and when I run the command below, ALL libraries are
build prior to building the release ti_wbi_umts_rac_raccm_host.tar.gz
xdc .interfaces
xdc ti_wbi_umts_rac_raccm_host
--
Patrick Geremia
Texas Instruments (http://www.ti.com)
Phone: +33 4 93 22 26 33
Email: p-geremia@ti.com
Availability: http://meetwith.me/patrickgeremia]]>Patrick Geremia2010-04-14T09:04:23-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/527245/#msg_527245
> Dave,
>
> are you sure you need the .zip?
> In my case, I build a compressed tarball (.tar.gz), the release name is
> not ti_wbi_umts_rac_raccm_host.tar.gz but ti_wbi_umts_rac_raccm_host
>
> I checked again and when I run the command below, ALL libraries are
> build prior to building the release ti_wbi_umts_rac_raccm_host.tar.gz
> xdc .interfaces
> xdc ti_wbi_umts_rac_raccm_host
>
Yes. By using the actual file name, rather than a generated
intermediate goal that has dependencies on .libraries, make will only
build the files necessary to create this particular file.
In your case, the file is ti_wbi_umts_rac_raccm_host.tar.gz (not .zip as
I originally assumed).
Recall that the xdc command just invokes GNU make with the arguments
supplied on the command line (plus a few extras). You can see exactly
what it invokes by passing the -n option.]]>Dave Russo2010-04-14T14:30:01-00:00Re: releasing a package
https://www.eclipse.org/forums/index.php/mv/msg/165901/527266/#msg_527266
Subject: Re: releasing a package
From: dave russo <d-russo@ti.com>
To:
Date: Wed Apr 14 2010 16:30:01 GMT+0200 (CEST)
>
>
> On 4/14/2010 2:04 AM, Patrick Geremia wrote:
>
>> Dave,
>>
>> are you sure you need the .zip?
>> In my case, I build a compressed tarball (.tar.gz), the release name is
>> not ti_wbi_umts_rac_raccm_host.tar.gz but ti_wbi_umts_rac_raccm_host
>>
>> I checked again and when I run the command below, ALL libraries are
>> build prior to building the release ti_wbi_umts_rac_raccm_host.tar.gz
>> xdc .interfaces
>> xdc ti_wbi_umts_rac_raccm_host
>>
> Yes. By using the actual file name, rather than a generated
> intermediate goal that has dependencies on .libraries, make will only
> build the files necessary to create this particular file.
>
> In your case, the file is ti_wbi_umts_rac_raccm_host.tar.gz (not .zip as
> I originally assumed).
>
> Recall that the xdc command just invokes GNU make with the arguments
> supplied on the command line (plus a few extras). You can see exactly
> what it invokes by passing the -n option.
>
>
Dave,