|AW: [cdt-dev] Imported source projects and source lookup don't workinCDT 3.1 SDK builds|
> I would check with PDE Build to see if it is a bug in their area.
So which mailing list do I post to?
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Doug Schaefer
Gesendet: Donnerstag, 20. April 2006 14:50
An: CDT General developers list.
Betreff: RE: [cdt-dev] Imported source projects and source lookup don't workinCDT 3.1 SDK builds
This could be a bug in PDE. Or they change the rules. Our build.properties files have not changed. The compile part of PDE picks up the source folders for classes to include in the build from the Runtime Information part of the editor. In the past, it also picked up which folders to include in the build. The source directories was only for additional directories to include, such as schemas.
Unpack is the setting that turns off the plugin as a jar feature. These should be left off except for plugins that contain shared libraries since the operating systems cant load them from the jar files.
I would check with PDE Build to see if it is a bug in their area.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC member
Behalf Of Ploett, Norbert
I checked your hints and found the following:
- The Build Configuration / Source Build (e.g. for cdt.core) does not have any of the source directories checked. That would be easy to change but since I have little experience, and do not have testbed, I hesitate do just do it. Maybe if somebody who knows would encourage me ...
- I am not sure about setting the "Unpack ..." property in the feature since we do not really want unpacked plugins, at least not for the runtime builds, maybe for the sdk builds. So even if somebody can confirm that this is actually necessary this change should be discussed in the community.
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von John Camelon
Back to the top