[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [pde-build-dev] Basebuilder Question
|
Thanks for the replies, Andrew and Pascal.
Yes, I assumed baseLocation was pointing
to both the builder and the required plugins at the same time. I
guess if I need two separate items I am wondering if it is worth it in
my case. Perhaps if I make this build system truly dynamic it would
be worth looking at. In particular, to handle the dependency issues
I will need to strategically use the pluginPath argument to the various
Ant tasks (which I haven't been able to get to work yet - but could be
doing something wrong) to satisfy things. I suppose I could use the
basebuilder and supply the rest of my dependencies that way. After
all, I'll need the infrastructure anyway. That just means I'll have
to include some Eclipse JARs in my binary repository.
So, if support for these Ant tasks that
allow me to do plugin-level builds is not going away then I'm going to
take a shot at this. Hopefully it isn't too hard. ;o)
In terms of EclipseCON - this year I'm
sure if I can go, which is a shame. But if I do end up going, I'll
definitely be targeting the PDE build tutorials!
Thanks again,
Mark.
----------------------------------------------------------
pde-build-dev-bounces@xxxxxxxxxxx wrote on 02/08/2007
07:16:36 PM:
>
> From what I see you are confusing the base location and the builder
> / releng.builder.
> The releng builder contains just the few plugins required to make
> pde build runs (ant, pde build, jdt core, etc.). See it as ANT on
steroids...
>
> The base location is the equivalent concept of the PDE UI target
> (window > preferences > pde target). It contains the set of
plugins
> and features that the application you are building depends on but
> that you are not compiling. For example a typical base location for
> developing RCP app is made of RCP binary dl plus the delta pack. To
> re-emphasize, it contains all the plugins that are required from
> your application and that you do not develop.
>
> So in your case what you want to do is: in one folder install releng
> builder, and in another one put all the plugins your app depends on
> (target). Then change the main build.properties (the one sitting
> next to the allElements.xml) to set the baseLocation property to
> point to the "target" folder.
>
>
> As for building one plugin at a time it should be possible and the
> script generator (eclipse.buildScript ant task) will happily
> generate you a build.xml for a plugin. However I'm not sure that you
> will find on this generated build.xml all the targets you will need.
> Your idea of "incremental build" sounds really interesting,
however
> you would have to be careful to recompile the dependent plugins on
> the ones that will have changed (note that the rules for knowing
> whether or not dependent plugins should be changed are pretty
> complex since it depends on the kind of code changes that have been
> done in java).
>
> *** Advertisement ***
> Sonia, Andrew, and I will be at eclipsecon for a tutorial on PDE Build.
>
> PaScaL
>
>
>
> Mark_Melvin@xxxxxxxx
> Sent by: pde-build-dev-bounces@xxxxxxxxxxx
> 02/08/2007 02:20 PM
>
> Please respond to
> "Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
>
> To
>
> pde-build-dev@xxxxxxxxxxx
>
> cc
>
> Subject
>
> [pde-build-dev] Basebuilder Question
>
>
>
>
>
> Hi All,
>
> I have a bit of a silly question. I am looking at streamlining
our
> build process and making it more granular. Currently we use
a
> headless PDE build that is rather monolithic. It currently uses
a
> full Eclipse SDK as the underlying build engine, but I was looking
> at using the basebuilder because it is much smaller. However,
I
> don't understand how this is supposed to work if you require a
> plugin that is part of the Eclipse platform runtime, but not
> included in the basebuilder. For example, one of my simplest
> plugins provides an intro page - and thus depends on org.eclipse.ui.
> intro. Naturally this fails to work with the basebuilder because
it
> is not included in the package. So, does this mean I should
just
> use an SDK like I have always been doing, or am I missing something
> here? What do other plugin projects do that depend on items
outside
> of the basebuilder package?
>
> A second question - I am looking at writing some wrapper scripts so
> that I can build a plugin at a time (outside of my features) using
> the PDE-provided Ant tasks (i.e. eclipse.buildScript). It looks
> like this is possible, but before I spend a huge amount of time on
> it - does anyone want to discourage me for any reason whatsoever?
;
> o) I am looking at doing this because I would like to split
up my
> build process into smaller bits and store the artifacts in an Ivy-
> like repository so I can essentially "assemble" components
as I need
> them. We also have a lot of plugins that don't change much compared
> to others, so it makes sense to not rebuild them all the time.
>
> Thanks in advance,
> Mark.
> AMI Semiconductor - "Silicon Solutions for the Real World"
> NOTICE:
> This electronic message contains information that may be
> confidential or privileged. The information is intended for the use
> of the individual or entity named above. If you are not the intended
> recipient, please be aware that any disclosure, copying,
> distribution or use of the contents of this information is
> prohibited. If you received this electronic message in error, please
> notify the sender and delete the copy you received.
> _______________________________________________
> pde-build-dev mailing list
> pde-build-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pde-build-dev
> _______________________________________________
> pde-build-dev mailing list
> pde-build-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pde-build-dev
AMI Semiconductor - "Silicon Solutions for the Real World"
NOTICE:
This electronic message contains information that may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you received this electronic message in error, please notify the sender and delete the copy you received.
