Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » buggy C/C++ build options window
buggy C/C++ build options window [message #110923] Thu, 15 July 2004 20:34 Go to next message
Eclipse UserFriend
Hi; i've been happily developing with Eclipse's CDT for some time now, but
yesterday my managed-make project suddenly stopped building.

When I try to build/rebuild my project, nothing happens. No messages in
the C-build window, or in the console from which I launched eclipse. I can
still build it outside of eclipse using the eclipse-generated makefile (by
typing "make" in a console), so it's not that my project isn't compilable
or magically crashes gcc or anything.

I looked at Project-->Properties-->C/C++ build, but in the configuration
settings panel, where there should be a list of things to tweak on the
left and some entry fields to the right (e.g. extra #include & lib paths),
I see only a blank list on the left and a blank gray area on the right.

That was with Eclipse 2.1.3 and cdt 1.2. I tried downloading Eclipse 3.0
and cdt 2.0, but I get the same problem. I'm using sun's jdk1.4.2_01 on
debian linux.

I tried removing my .metadata folder and re-launching eclipse, but that
didn't help.

Any suggestions?

Thanks,
-- Matt
Re: buggy C/C++ build options window [message #110983 is a reply to message #110923] Fri, 16 July 2004 09:15 Go to previous messageGo to next message
Eclipse UserFriend
Matt,
Sounds like something in the .cdtbuild file has become corrupted. It's
too bad you blew away the .metadata directory because there would have
been a log file there which might have contained a call stack with some
error information. Probably the best thing to do is raise a bugzilla
report, copy the contents of the .metadata/log file into it.

What happens when you create a new project and move the contents of the
old project over to it?

Sean

Matt wrote:
> Hi; i've been happily developing with Eclipse's CDT for some time now, but
> yesterday my managed-make project suddenly stopped building.
>
> When I try to build/rebuild my project, nothing happens. No messages in
> the C-build window, or in the console from which I launched eclipse. I can
> still build it outside of eclipse using the eclipse-generated makefile (by
> typing "make" in a console), so it's not that my project isn't compilable
> or magically crashes gcc or anything.
>
> I looked at Project-->Properties-->C/C++ build, but in the configuration
> settings panel, where there should be a list of things to tweak on the
> left and some entry fields to the right (e.g. extra #include & lib paths),
> I see only a blank list on the left and a blank gray area on the right.
>
> That was with Eclipse 2.1.3 and cdt 1.2. I tried downloading Eclipse 3.0
> and cdt 2.0, but I get the same problem. I'm using sun's jdk1.4.2_01 on
> debian linux.
>
> I tried removing my .metadata folder and re-launching eclipse, but that
> didn't help.
>
> Any suggestions?
>
> Thanks,
> -- Matt
>
>
>
Re: buggy C/C++ build options window [message #111112 is a reply to message #110983] Fri, 16 July 2004 12:55 Go to previous messageGo to next message
Eclipse UserFriend
I tried making a new project and copying the source files over, and that
seemed to work. The project-->properties-->c/c++ build window is now fully
functional.
I actually hadn't nuked my .metadata folder, I just renamed it so it
wouldn't get used. I'll try posting a bugzilla report.

Thanks,
-- Matt

Sean Evoy wrote:

> Matt,
> Sounds like something in the .cdtbuild file has become corrupted. It's
> too bad you blew away the .metadata directory because there would have
> been a log file there which might have contained a call stack with some
> error information. Probably the best thing to do is raise a bugzilla
> report, copy the contents of the .metadata/log file into it.

> What happens when you create a new project and move the contents of the
> old project over to it?

> Sean

> Matt wrote:
> > Hi; i've been happily developing with Eclipse's CDT for some time now, but
> > yesterday my managed-make project suddenly stopped building.
> >
> > When I try to build/rebuild my project, nothing happens. No messages in
> > the C-build window, or in the console from which I launched eclipse. I can
> > still build it outside of eclipse using the eclipse-generated makefile (by
> > typing "make" in a console), so it's not that my project isn't compilable
> > or magically crashes gcc or anything.
> >
> > I looked at Project-->Properties-->C/C++ build, but in the configuration
> > settings panel, where there should be a list of things to tweak on the
> > left and some entry fields to the right (e.g. extra #include & lib paths),
> > I see only a blank list on the left and a blank gray area on the right.
> >
> > That was with Eclipse 2.1.3 and cdt 1.2. I tried downloading Eclipse 3.0
> > and cdt 2.0, but I get the same problem. I'm using sun's jdk1.4.2_01 on
> > debian linux.
> >
> > I tried removing my .metadata folder and re-launching eclipse, but that
> > didn't help.
> >
> > Any suggestions?
> >
> > Thanks,
> > -- Matt
> >
> >
> >
Re: buggy C/C++ build options window [message #111328 is a reply to message #111112] Sat, 17 July 2004 14:52 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: genbiz.albaedit.com

Matt wrote:
> I tried making a new project and copying the source files over, and that
> seemed to work. The project-->properties-->c/c++ build window is now fully
> functional.
> I actually hadn't nuked my .metadata folder, I just renamed it so it
> wouldn't get used. I'll try posting a bugzilla report.
>
> Thanks,
> -- Matt
>
> Sean Evoy wrote:
>
>
>>Matt,
>>Sounds like something in the .cdtbuild file has become corrupted. It's
>>too bad you blew away the .metadata directory because there would have
>>been a log file there which might have contained a call stack with some
>>error information. Probably the best thing to do is raise a bugzilla
>>report, copy the contents of the .metadata/log file into it.
>
>
>>What happens when you create a new project and move the contents of the
>>old project over to it?
>
>
>>Sean
>
>
>>Matt wrote:
>>
>>>Hi; i've been happily developing with Eclipse's CDT for some time now, but
>>>yesterday my managed-make project suddenly stopped building.
>>>
>>>When I try to build/rebuild my project, nothing happens. No messages in
>>>the C-build window, or in the console from which I launched eclipse. I can
>>>still build it outside of eclipse using the eclipse-generated makefile (by
>>>typing "make" in a console), so it's not that my project isn't compilable
>>>or magically crashes gcc or anything.
>>>
>>>I looked at Project-->Properties-->C/C++ build, but in the configuration
>>>settings panel, where there should be a list of things to tweak on the
>>>left and some entry fields to the right (e.g. extra #include & lib paths),
>>>I see only a blank list on the left and a blank gray area on the right.
>>>
>>>That was with Eclipse 2.1.3 and cdt 1.2. I tried downloading Eclipse 3.0
>>>and cdt 2.0, but I get the same problem. I'm using sun's jdk1.4.2_01 on
>>>debian linux.
>>>
>>>I tried removing my .metadata folder and re-launching eclipse, but that
>>>didn't help.
>>>
>>>Any suggestions?
>>>
>>>Thanks,
>>>-- Matt
>>>
>>>
>>>
>
>
>

I have this problem constantly, and I'm always having to create a new
project, and then bringing over the source once again from the last
project which ceased to compile.

The last straw was today, when I touched a file. I hit BuildAll and the
app hangs. Sometimes the hard disk works on something for a bit, but
many times there is no drive activity. If I try to cancel, nothing
happens, and if I kill the app, I corrupt the .metadata file. The only
exit is to log off, and then back on. Then, off I go, renaming the
current project to something else, restart Eclipse, create a new C
project, import the old files, re-enter all the build data (defines,
directories, libraries to link) and then I'm back in action, for a build
or two.

No offense to the great folks working on this project, but it is the
most fragile piece of production code I've ever worked with. There is no
way I'm going over to new version. I've finally got a set of workarounds
with this one.

For the record, I'm using Eclipse 2.1.2 and CDT 1.2.1.
Re: buggy C/C++ build options window [message #111513 is a reply to message #111328] Mon, 19 July 2004 15:40 Go to previous message
Eclipse UserFriend
Actually,
Moving over to the new version may involve some potential short-term
pain as your projects are converted, but some improvements have been
made to both the internals of the build system and the dependency
generation. From your description, it sounds like the manged builder is
spinning-up the indexer to help it do dependency calculation. The
builder no longer relies on this feature to work, so these types of long
delays before a build are (typically) reduced or eliminated altogether.
Further, some major strides have been made to improve the way the build
model manages its internal data which may reduce or eliminate the number
of times the project data is corrupted due to other failures.

It is entirely up to you, of course.

Sean

Joseph Rooney wrote:

> Matt wrote:
>
>> I tried making a new project and copying the source files over, and that
>> seemed to work. The project-->properties-->c/c++ build window is now
>> fully
>> functional. I actually hadn't nuked my .metadata folder, I just
>> renamed it so it
>> wouldn't get used. I'll try posting a bugzilla report.
>>
>> Thanks,
>> -- Matt
>>
>> Sean Evoy wrote:
>>
>>
>>> Matt,
>>> Sounds like something in the .cdtbuild file has become corrupted.
>>> It's too bad you blew away the .metadata directory because there
>>> would have been a log file there which might have contained a call
>>> stack with some error information. Probably the best thing to do is
>>> raise a bugzilla report, copy the contents of the .metadata/log file
>>> into it.
>>
>>
>>
>>> What happens when you create a new project and move the contents of
>>> the old project over to it?
>>
>>
>>
>>> Sean
>>
>>
>>
>>> Matt wrote:
>>>
>>>> Hi; i've been happily developing with Eclipse's CDT for some time
>>>> now, but
>>>> yesterday my managed-make project suddenly stopped building.
>>>>
>>>> When I try to build/rebuild my project, nothing happens. No messages in
>>>> the C-build window, or in the console from which I launched eclipse.
>>>> I can
>>>> still build it outside of eclipse using the eclipse-generated
>>>> makefile (by
>>>> typing "make" in a console), so it's not that my project isn't
>>>> compilable
>>>> or magically crashes gcc or anything.
>>>>
>>>> I looked at Project-->Properties-->C/C++ build, but in the
>>>> configuration
>>>> settings panel, where there should be a list of things to tweak on the
>>>> left and some entry fields to the right (e.g. extra #include & lib
>>>> paths),
>>>> I see only a blank list on the left and a blank gray area on the right.
>>>>
>>>> That was with Eclipse 2.1.3 and cdt 1.2. I tried downloading Eclipse
>>>> 3.0
>>>> and cdt 2.0, but I get the same problem. I'm using sun's jdk1.4.2_01 on
>>>> debian linux.
>>>>
>>>> I tried removing my .metadata folder and re-launching eclipse, but that
>>>> didn't help.
>>>>
>>>> Any suggestions?
>>>>
>>>> Thanks,
>>>> -- Matt
>>>>
>>>>
>>>>
>>
>>
>>
>
> I have this problem constantly, and I'm always having to create a new
> project, and then bringing over the source once again from the last
> project which ceased to compile.
>
> The last straw was today, when I touched a file. I hit BuildAll and the
> app hangs. Sometimes the hard disk works on something for a bit, but
> many times there is no drive activity. If I try to cancel, nothing
> happens, and if I kill the app, I corrupt the .metadata file. The only
> exit is to log off, and then back on. Then, off I go, renaming the
> current project to something else, restart Eclipse, create a new C
> project, import the old files, re-enter all the build data (defines,
> directories, libraries to link) and then I'm back in action, for a build
> or two.
>
> No offense to the great folks working on this project, but it is the
> most fragile piece of production code I've ever worked with. There is no
> way I'm going over to new version. I've finally got a set of workarounds
> with this one.
>
> For the record, I'm using Eclipse 2.1.2 and CDT 1.2.1.
>
Previous Topic:converting old cdt projects to cdt 2.0
Next Topic:How to develop VS project in Eclipse?
Goto Forum:
  


Current Time: Sun Nov 09 23:02:01 EST 2025

Powered by FUDForum. Page generated in 0.07913 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top