Re: [pde-build-dev] Basebuilder Question

[Andrew Niefer <aniefer@xxxxxxxxxx>]

Mark,
The basebuilder is different from the
baseLocation.  As you said, basebuilder is the build engine so it
really only needs to contain the things that org.eclipse.pde.build depends
on.  The plugins that the things you are building depend on are expected
to be in the baseLocation.  You could probably use one eclipse SDK
install for both, but it would probably be better to keep them separate,
especially since you are trying to be more specific about what is getting
built.

For the second question, the one thing
that comes to mind about compiled plugins one at a time, you need to make
sure you do them in the right order (for dependencies) and when one changes,
all of its dependents are recompiled as well.

-Andrew

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