Re: [pde-build-dev] Avoiding Multiple Builds of Nested Features

[Andrew Niefer <aniefer@xxxxxxxxxx>]

Mark,
Generally this list is for developing
PDE Build itself, so the platform or rcp newsgroup would be better,  

The eclipse.buildScript task will take
a "recursiveGeneration" property, so yes you should be able to
add it to genericTargets.xml.  Note that the main build script finds
the genericTargets.xml by using the ${genericTargets} propery which defaults
to ${eclipse.pdebuild.scripts}/genericTargets.xml.  So you could have
your own copy by setting this property manually.
The effect of setting "recursiveGeneration"
 will be to not generate scripts for nested features.

A different solution would be to consider
rearranging your features:
-MasterFeature  (without bin.includes
omits it from final results)
        -
includes Common Feature 
        -
includes Feature X
         
      -requires Common Feature
        -
includes Feature Y
         
      -requires Common Feature

-Andrew

Mark_Melvin@xxxxxxxx
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

06/15/2006 10:12 AM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
cc
Subject	[pde-build-dev] Avoiding Multiple Builds of Nested Features

Hmm...I figured I could work around this problem (if it even exists - my
build is so broken now I have yet to find out) by perhaps specifying recursiveGeneration=false
as a property because this is at the top of genericTargets.xml:

<!-- Properties that must be passed to this script:
        buildDirectory 
        id 
        type 
        ignoreTagInfo 
        recursiveGeneration
        workingDirectory 
        configInfo 
--> 

However, I see no use of recursiveGeneration anywhere
in that script.  I assume it was meant to be passed as an attribute
to eclipse.buildScript
in the generateScript target
and was just never implemented?  It seems to me I could simply write
my own version of genericTargets.xml that
does exactly this, however I assume this has never been tested so I wonder
what might break downstream.  This is a big build process and I have
a few years under my belt dealing with it.  ;o)  I'm leery to
check in massive changes to my feature structure and dive into this without
knowing how this is going to work. 
Has anyone tried building multiple features that nest the same common features
before?  Has anyone tried avoiding this using recursiveGeneration=false?

Thanks (again), 
Mark.
----------------------------------------------------------


__________________ 

I have a couple more questions about PDE build.  By the way - is the
mailing list a good place to be asking these, or is the platform newsgroup
a better forum? 

Anyway - let's say for simplicity that I have the following structure where
two features nest the same shared feature: 

Feature X 
  +- Common Feature A 

Feature Y 
  +- Common Feature A 

Now, if I write my customTargets.xml to build Feature
X and Feature
Y, PDE build automatically builds
the nested feature - but will PDE build Common
Feature A twice?  I think
it will. 

Also, is it the same for the assemble stage?  I assume I only have
to specify the assembly of Feature X
and Feature Y,
and the assembly of Common Feature A
will happen automatically - but will it happen twice here as well?

If the above is behaviour is correct, now that I have gone through and
reorganized all of my features to be nested my build time is going to skyrocket.
 It will basically be building the majority of my common features
5 or 6 times!  Nooooooo! 

Thanks 
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