[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Releng change thoughts
|
Just tried the new install. Works very nicely, and guarantees i have a
local copy of all the pieces(useful for building installs of the different
combos offline).
Plus I automatically have an install site on my local machine as well (also
good for teaching tutorials!)
However, it turned off "Build automatically" for my PDE/java environment.
I remember the discussion about turning it off for CDT. Don't know that
you can separate the two, but...
Not sure most folks will realize this, and lots of compile errors scared me
for a bit there, until i turned it back on....
...Beth
Beth Tibbitts (859) 243-4981 (TL 545-4981)
High Productivity Tools / Parallel Tools http://eclipse.org/ptp
IBM T.J.Watson Research Center
Mailing Address: IBM Corp., 455 Park Place, Lexington, KY 40511
Doug Schaefer
<DSchaefer@xxxxxx
m> To
Sent by: "CDT General developers list."
cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
clipse.org cc
Subject
06/05/2007 07:55 RE: [cdt-dev] Releng change
PM thoughts
Please respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
O.K. I got the first build done. All 4.0.0 builds starting with
I200706052319 are done in the new way. It's a single zip called cdt-master.
Download to your machine and hook it up to the Update Manager using the New
Archived Site button. As a reminder, the build page is:
http://download.eclipse.org/tools/cdt/builds
BTW, the new zip is 32.4 Meg, which is only slightly larger that the SDK
downloads which were 28-29 Meg. The build is also takes 2/3 the time. I'm
pretty happy with it. Please provide your feedback, especially if there are
things that don't work.
Also, builds are now total 36 Meg (with compile log and junit results) down
from 438 Meg from the last build. This should mean that I can run builds
more often, maybe even truly nightly :)
Cheers,
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Doug Schaefer
> Sent: Tuesday, June 05, 2007 2:02 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Releng change thoughts
>
> Cool. That's exactly what I'm working on right now. But it confirms I'm
> going down the right path.
>
> I don't think I'm going to get to the slice and dice part of this
process.
> And part of this is so that we don't have such huge builds and keep
> running
> out of disk quota anyway.
>
> So we'll have one master zip file that contains the update site as I get
> it
> from the signer. I'll unzip it and run the optimizer to create our
> eclipse.org update site.
>
> If anyone comes up with reusable slice and dice scripts, feel free to
> contribute them.
>
> Thanks, Vivian!
> Doug Schaefer, QNX Software Systems
> Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
>
>
> > -----Original Message-----
> > From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On
> > Behalf Of Vivian Kong
> > Sent: Tuesday, June 05, 2007 1:37 PM
> > To: CDT General developers list.
> > Subject: RE: [cdt-dev] Releng change thoughts
> >
> > Hi Doug,
> >
> > I was exchanging emails with Kim Moir from Platform and she has a
> comment
> > on signing below:
> >
> > It's possible to have both the update site and the builds signed. Here
> is
> > the approach we take
> >
> > Construct a build-time master feature which contains all the plugins
and
> > features that are used in the build.
> > Send this master feature to the eclipse.org signing process.
> > When signing is complete, slice and dice the master feature into the
> ziips
> > that you need for your build using pde build's packaging facilities.
> > Create an update site with the same jars from the feature, run the
> update
> > core's site optimizer to create the packed jars.
> > Thus you will be using the same jars that are used for the update site
> as
> > are used for the build and they will both be signed and packed.
> >
> > This approach also saves time during the build process because plugins
> in
> > multiple features are not compiled twice since you are using the
> packager
> > to assemble the build.
> > When we converted our build to use this approach, the time for the
> actual
> > build to complete decreased by 30%.
> >
> > Regards,
> >
> > Vivian Kong
> > IBM Eclipse CDT
> > IBM Canada Toronto Lab
> > Phone: (905) 413-6067
> > Email: vivkong@xxxxxxxxxx
> >
> >
> >
> > From: Doug Schaefer <DSchaefer@xxxxxxx>
> >
> > To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
> >
> > Date: 06/05/2007 09:58 AM
> >
> > Subject RE: [cdt-dev] Releng change thoughts
> > :
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx]
> > On
> > > Behalf Of Adam Finucane
> > > Sent: Monday, June 04, 2007 6:49 PM
> > > To: CDT General developers list.
> > > Subject: Re: [cdt-dev] Releng change thoughts
> > >
> > > Hello Doug,
> > >
> > > Having the zip archive of the update site sounds good. I assume this
> > will
> > > be
> > > the case for releases as well, as releases is just a particularly
good
> > > "nightly" build. It will be easier for us to manage. Instead of
> > > downloading
> > > several zips and tar.gzs for various OSes, we can download a single
> > file.
> >
> > That's a good point and an added bonus. And yes, that would include all
> > builds. Right now I take the zips and create the update site with a
> couple
> > of scripts. This will make that easier as well.
> >
> > > > People who used to use the .zips/tar.gz's for creating product
> > installs
> > > can
> > > > use the archive site to create the same layout with some simple
> > scripts.
> > >
> > > Some example scripts would be nice :o)
> >
> > Yes, we'll see how my time goes, this might have to wait until later
> this
> > month. The idea though is to unjar the cdt.core.* fragments since they
> > have
> > shared libraries that need to be on the file system directly to load.
> >
> > Also, if you're not shipping the SDK or other features we're building
> now,
> > you'd need to remove them. Looking at the feature.xml files gives the
> list
> > of plugins you care about.
> >
> > Thanks,
> > Doug
> >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
