[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] building the Memory Browser and Traditional Renderer
|
I've been working with Randy on the sidelines to get to the bottom of
this. The reason he's getting the error is that he's using Ecipse 3.6M5
and then referencing M7 as the target platform. That approach is usually
fine but there are cases where it isn't--specifically, when a
project
itself (not the code in the project) takes advantage of a new
behavior in the platform. Last week I updated various projects on HEAD to
rely on a new option in JDT that appeared in Eclipse 3.6M6. So, if you're
using a milestone before that, you'll run into the same problems Randy
did.
Ken and I ran into this a while back. I reported an error/warning in an
EDC project. He wasn't seeing it, though, and some serious
head-scratching ensued. Ken finally realized it was because he was using
an older milestone build of the platform as his toolset. So, beware of
this gotchya.
John
At 02:40 PM 5/10/2010, Rohrbach, Randy wrote:
Content-Class:
urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01CAF078.A75F9926"
Folks
I just updated my Open Source Reference CDT
developmemnt space to all M7.
I needed to reset the build options
errors/warnings for the MemoryBrowser and
TraditionalRenderer to the defaults in order to get them to
build. I have not made
any changes to these components. There were certain
specifications which were
forcing errors where they used to just be warnings.
I have seen some emails ( but not followed to
closely ) concerning errors and
warnings changes.
Has anything been changed for these
components.
Thanks for the info.
Randy
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
