Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#31 Build fails after switching tool chain

Next release
closed
None
9
2014-02-14
2010-07-09
Peter Horn
No

The target no longer builds after the tool chain has been switched forth and back in the tool chain editor. The build fails with message

"No tool found that can build the extension specified with the build artifact name all"

The only way to get out is to add an new build configuration.

Steps to reproduce:

Create a project, add some files, build it.
Open Project Properties->C/C++ Build->Tool Chain Editor
Change the current tool chain to a different one, press apply
Then set the tool chain back to the original setting
Build the project -> Fails

Environment:

GNU ARM C/C++ Development Support 0.5.3.201007072245 org.eclipse.cdt.cross.arm.gnu.feature.group
Eclipse IDE for C/C++ Developers 1.3.0.20100617-0520 epp.package.cpp

Discussion

    • assigned_to: nobody --> ilg-ul
    • status: open --> open-accepted
     
  • I confirm it. it looks like a CDT bug.

     
    • priority: 5 --> 9
     
  • I marked this as a major bug, since I did not find a way to repair broken projects (you have to create a new project and copy content).

    I'll investigate if it is a plug-in or a CDT bug.

    Liviu

     
  • alexp
    alexp
    2011-10-16

    does a fix exist for this bug & svn?
    i import a project via svn, if i create a new procet this is a temporery solution to work, thank you ilg-ul for this solution.
    but in my case i'm not able to commit or update again the new project via svn.

     
  • I don't know of a fix for this bug :-(

    I'll check again when the Indigo will be fixed, currently the plug-in does not run properly on Indigo due to another CDT problem.

    Liviu

     
  • alexp
    alexp
    2011-10-16

    do you know a other way to do a workaround for my problem?
    if i create a new project i'm not able to syncronice with the team in eclipse (svn) & if i synchronice (checkout) i get the wrong settings and must switch the toolchain.
    in this case it's not easy to work...
    perhapse has somebody a idea?!

    thanks

     
  • ok i found a solution for my problem.
    its similar like the workaround from ilg-ul.

    create a new project and config it you need.
    after, copy the content from the .cproject into the .cproject from the broken svn project.
    (the svn project hast now the right configuration)
    now you are able to work with a svn project and can update and commit :-)

     
  • alexp
    alexp
    2011-12-02

    hello,
    today i tried indigo with GNU ARM 0.5.4.201111262136,
    and it it has the sam problem (with the switching of the toolchain).

    and i have a problem with the version 0.5.4, i must uncheck the "group items by category" by installing it via help-->install new software --> (location http://gnuarmeclipse.sourceforge.net/updates/\). its the first time i must do this with the gnu arm plug-in.

    and it possible that the 0.5.4 does not work with the eclipse helios?

     
  • > "group items by category"

    fixed, please check again with 0.5.4.201112030833

    > 0.5.4 does not work with the eclipse helios

    nope, it requires CDT 8.0

    Liviu

     
  • and, Alex, please do not mix multiple bug reports under the same ticket

    Liviu

     
  • alexp
    alexp
    2011-12-06

    thanks,

    only the toolchain-switch bug is open. do you think it can be fixes?

     
  • > only the toolchain-switch bug is open. do you think it can be fixes?

    I don't know yet, but now I have the full CDT source tree in my development environment and I can try to debug the toolchain-switch bug.

    the goal is to find a way to patch my plug-in to avoid the bug, otherwise I see the CDT team reaction is not very fast.

    Liviu

     
  • Manveru
    Manveru
    2012-07-31

    Was this bug reported to the CDT team? I am under Eclipse Juno with GNU ARM 0.5.4.201202210114 and the same problem hits me. Now I have broken project with very complex configuration, that cannot be build due to "No tool found that can build the extension specified with the build artifact name" in makefile.

    I was looking for solution to the other problem with GCC Build output parser (which took wrong command for compilation - not these from my setting, but pure "gcc") and that is why I was switching toolchains.

    I does not sound funny to me to recreate the project.

     
  • lkrzak
    lkrzak
    2013-09-12

    Are there any chances for a fix to this problem? I'm using Eclipse Keppler and the bug still exists. I'm using version 0.5.4.201202210114.

     
  • It is hard to say, being a CDT bug, it can be fixed only by the CDT developers. All I can do, is try (again) to find an workaround, but I do not guarantee any positive results.

    Regards,

    Liviu

     
  • lkrzak
    lkrzak
    2013-09-13

    Ok, let me just point out the exact steps to reproduce the problem and the problem itself, because it may be in fact something else than discussed previously.

    1. Create new C project -> ARM Cross Target Application -> Empty project and select any toolchain - the project is named "test"
    2. Add some source files -> build successful
    3. Change toolchain in C/C++ Build -> Toolchain editor -> build failed with error
    4. Change back the toolchain and the error still remains

    Now the error is:
    make: *** No rule to make target test.elf', needed byall'. Stop.

    Now what is seems to me is that in fact in the generated makefiles there is no rule to build test.elf

    Can I help in any way with this ?

     
  • I think it is the same problem, changing toolchains confuses CDT, and the generated makefile is incomplete, which leeds to failed builds.

    Liviu

     
  • Sprut
    Sprut
    2013-10-09

    Hello.

    This is the difference between the files .cproject.

    I did not click OK after changing the toolchain. I just chose to list the other, and then handed it back and then clicked OK.

    http://diffchecker.com/opuni1ih

    makefile changes too, but it does not affect the build. Returning old .cproject, and makefile to leave new - then everything is OK.

     
    Last edit: Sprut 2013-10-09
  • Thank you Sprut for your detailed report. The bug is known, but nobody from CDT fixed it yet. I recently got involved in CDT development, and I'll try to investigate.

     
    • status: open-accepted --> closed
    • Group: --> Next release