[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] releng/ptp vs core/ptp.core
|
Orion,
I think org.eclipse.ptp is only for branding purposes, so you can probably exclude it from the build.
Greg
On Jan 20, 2010, at 2:05 PM, Orion Poplawski wrote:
> I'm trying to do a modular build of PTP for Fedora, so to that end instead of building the ptp.master feature, I'm doing:
>
> features=$(grep -F id= releng/org.eclipse.ptp.master/feature.xml | sed -e 's/^ *id="//' -e 's/"$//' | grep -vF master | grep -vF slurm | grep -vF etfw.tau | grep -vF ptp.rm.pbs)
> for feature in $features
> do
> %{eclipse_arch_base}/buildscripts/pdebuild -d "cdt cdt-parsers rse" \
> -f $feature -a "-DjavacSource=1.5 -DjavacTarget=1.5" -o `pwd`/orbitDeps
> done
>
> Which basically gets me a bunch of individual features/dropins, which seem okay. I also get a org.eclipse.ptp and org.eclipse.ptp.core package, which both contain ptp.core, ptp.debug, ptp.help, ptp.ui, and some others, but org.eclipse.ptp also contains the ptp "feature".
>
> This seems a little odd. Perhaps ptp.core shouldn't be in ptp.master/feature.xml ?
>
> --
> Orion Poplawski
> Technical Manager 303-415-9701 x222
> NWRA/CoRA Division FAX: 303-415-9702
> 3380 Mitchell Lane orion@xxxxxxxxxxxxx
> Boulder, CO 80301 http://www.cora.nwra.com
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
