| RE: [cdt-dev] Build problem - no errors presented! |
|
..sorry, I probably
misinterpreted your last message. The conversion wizard from the latest builds
should work normally for your “non-broken” old-style make projects.
It will not work for your “broken” projects only. Let me know if
that’s not true for you. Mikhail From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail What CDT Build are you
using? As I mentioned, this will be possible starting from the next build or
with the sources from HEAD. Mikhail From:
Fedja Jeleskovic [mailto:mrawd2@xxxxxxxxx] Hmm, I tried
to use the wizard to convert those but when I open up the converter window (by
following the directions of yours) the final one comes empty with Next and Finish
buttons disabled, so I can't continue. Any words on this? On 3/16/07, Sennikovsky, Mikhail <mikhail.sennikovsky@xxxxxxxxx > wrote: Ok, that's really great that we've managed to
find the root of the problem! I'll try to fix it ASAP. >
What should I do know with those projects of mine? Should I delete them all and
recreate everything from the scratch (I rather wouldn't, but if I have to...)?
Or, this might be fixed in the next release of CDT perhaps? For the "non-broken" old-style make
projects (i.e. those that were NOT created on top of the previously existing
old make projects) you can use the "Convert to a C/C++ Make Project"
wizard to convert them to the new-style make projects. The wizard is accessed
by "File"->"New"->"Other.." ->
"C++" or "C" -> "Convert to a C/C++ Make
Project". The wizard will allow you to convert any non-CDT and old-style
make projects presented in the workspace to the new style make project format. NOTE: the general way of importing existing
project into the workspace is importing them rather than creating a new project
on top of the already existing one. To import the project go to
"File" -> "Import" -> "General" -> "Existing
Projects into the Workspace" -> point to your project's location
-> select projects to be imported -> press "Finish" As for the "broken" old-style make
projects (i.e. those that were created on top of the previously existing old
make projects) You can do the following: I. In case the existing project settings are not
valuable for you (e.g. make target settings, etc.), you can just remove the
CDT/Eclipse system files from your project directory (i.e. the .project,
.cdtproject and .cproject files) and create a new project on top of that directory II. In case you are willing to keep the project
settings, you could do the following hack: NOTE: this will be possible starting from the
next CDT build only or using sources from HEAD. 1. remove the
.cproject file from the broken project drectory (don't mix it up with the
.project and .cdtproject files that should be kept) NOTE: the
workspace containing the project should be closed. 2. import the
project into the workspace or just open the workspace containing the broken
project and convert it using the wizard NOTE: The
project with removed .cproject file will be broken and will not function until
it is converted, so you should convert that project as soon as you remove the
.cproject file. Thanks, Mikhail From: Fedja
Jeleskovic [mailto:mrawd2@xxxxxxxxx]
Great! On
3/16/07, Sennikovsky, Mikhail <mikhail.sennikovsky@xxxxxxxxx > wrote: Hi Fedja, Never mind, having your sample project I seem to
find the problem. Your project contains both old-style make natures and
builders as well as new ones. I was able to create the similar project in case
the new-style project is created in the directory containing the old-style make
project (isn't it your case by the way? J ). It seems that you bugs https://bugs.eclipse.org/bugs/show_bug.cgi?id=177458
and https://bugs.eclipse.org/bugs/show_bug.cgi?id=177454 have
the same source. I'll fix this issue and we'll see how things will
go. I'll also investigate the problem with error
messages. Thanks, Mikhail From: Fedja
Jeleskovic [mailto:mrawd2@xxxxxxxxx]
Hi Mikhail, On
3/16/07, Sennikovsky, Mikhail <mikhail.sennikovsky@xxxxxxxxx
> wrote: Fedja, I guess I understand the root of the problem now.
Could you check whether the Autobuild is enabled in your workspace
("Project"->"Build Automatically" menu selected)? I
guess the "make all" build is an autobuild that somehow gets
initiated as a result of the make target build. I'll investigate why this is
happening and will fix the problem. I guess that the https://bugs.eclipse.org/bugs/show_bug.cgi?id=177454
(Make Target build fails to build subcomponents) has the same nature as the
problem you report here. Please try disabling the autobuild an let me know
if this fixes the top level "make all" being invoked when invoking
the custom target. Thanks, Mikhail From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:
cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of
Fedja Jeleskovic Hi there,
|