[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [cdt-dev] Imported source projects and source lookup don't workinCDT 3.1 SDK builds
|
John,
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.
Opinions?
Norbert Ploett
I don't have time to look right now,
but are the feature.xml and build.properties both set properly? I believe the "Source Build" for the build.properties
needs to actually include all of the source directories, and the feature.xml
should "unpack plugin archive after installation", that has worked for me in the
past. --
JohnC
"Sascha Radike"
<sradike@xxxxxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx
04/19/2006 07:48 AM
|
Please respond
to
"CDT General developers
list." |
|
|
To
| "'CDT General developers
list.'" <cdt-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| AW: [cdt-dev] Imported
source projects and source lookup don't work
inCDT 3.1 SDK builds |
|
Yeah, I noticed missing source code, too. Also the extension point
schemas
can't be found.
That's why I imported all plugins from
HEAD.
Sascha
________________________________________
Von:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im
Auftrag
von Ploett, Norbert
Gesendet: Mittwoch, 19. April 2006 12:39
An: CDT
General developers list.
Betreff: [cdt-dev] Imported source projects and
source lookup don't work
inCDT 3.1 SDK builds
Hi
folks,
this is quite a nuisance, I noticed it a few weeks ago and
nobody responded
to my posting. So I'll try again now.
- Install
eclipse 3.2RC1 and a CDT SDK (!) nightly build from the CDT build
machine (I
have the one from April 18 currently, does not matter much
however).
-
Import any CDT plug-in, let's take cdt.core for example AS SOURCE PROJECT.
-
Admire a list of round 70 error messages like so:
Package
'org.eclipse.cdt.core.dom.ast.c' does not exist in
this
plug-in org.eclipse.cdt.core/META-INF MANIFEST.MF line
11 1145442735079 15555
These
errors are there because
a) The imported plug-in project
does NOT contain ANY SOURCES and
b) the jar file which is packaged in
(e.g.
org.eclipse.cdt.core_3.1.0.200604180500.jar) is not on the java
compiler's
build path.
b) can easily be righted manually but the
problem of missing sources
remains: I have no way to look into the code.
Guess it has something to do with the build process on the cdt
build
machine. The sources are not packaged with the SDK in the right way.
Will
anybody take a look at this? Is this behavior reproducable for anybody
else?
Thanks,
Norbert
Ploett
=======================
Dr.-Ing. Norbert Plött
Siemens
A&D ATS 1
Gleiwitzer Str. 555
90475 Nürnberg
Tel.: +49 911 895
3484
Fax: +49 911 895
3715
_______________________________________________
cdt-dev
mailing
list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
