#39 Build project with linked Debug/Release folders

Version 0.5.5
closed
None
5
2014-08-17
2014-02-20
glory_man
No

Eclipse Kepler
GNU ARM C/C++ Development Support (End of life) 0.5.5.201310221100

When I create simple "Hello World" project with Sourcery Lite support and try to build it - all fine. But after that delete Debug/Release folder, add linked folder Debug/Release and try to build I have error:
cs-make: *** No rule to make target `all'. Stop.
Is this feature or bug? Why I cann't add linked folders to collect object files of project?

Discussion

    • status: open --> accepted
    • assigned_to: Liviu Ionescu (ilg)
     
  • 0.5.5.201310221100

    sorry, 0.5.5 is no longer supported

    linked Debug/Release folders

    please try exactly the same configuration with the native gcc compiler (not the gnu arm compiler), and let me know if you can build in linked folders.

     
  •  glory_man
    glory_man
    2014-02-20

    I reproduced my steps with "GNU ARM C/C++ Cross Compiler Support 1.8.1.201402180751" installed in eclipse and still have this error for Linked folder.
    "Hello world ANSI C project" with MinGW GCC used have another error when linked folders used for obj files.
    gcc: error: ..\src_b.c: No such file or directory
    gcc: fatal error: no input files
    But with Debug/Release folders inside Project directory buikdes normally.

     
  • how did you create the linked folders? please provide a detailed step by step instruction on how to reproduce your configuration.

     
  •  glory_man
    glory_man
    2014-02-20

    I have following folders structure
    d:\prj\wsp - for eclipse workspace
    d:\prj\obj\Debug - to collect object files of debug config
    d:\prj\obj\Relase - to collect object files of release config
    d:\prj\bin - to collect binary files

    First of all I cann't reproduce steps from ttorial - http://gnuarmeclipse.livius.net/blog/test-project/ - for "Hello World ARM Cortex-M3 C Project". So I tried for "ARM C".
    1. Create "Hello World ARM C Project" - with Cross ARM GCC toolchain.
    2. In the Basic Settings window - save default configurations.
    3. I use "Sourcery CodeBench Lite for ARM EABI (arm-none-eabi-gcc)" so - configure toolchain path - and click Finish
    4. Try to build project - have error:
    Error: Program "cs_make" not found in PATH
    5. In Toolchain settings window change cs_make (cs_rm) -> cs-make (cs-rm)
    6. Try to build - error:
    Building target: _c.elf
    Invoking: Cross ARM C Linker
    arm-none-eabi-gcc -mcpu=cortex-m3 -mthumb -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Wall -g3 -T mem.ld -T sections.ld -Xlinker --gc-sections -L../ldscripts -Wl,-Map,"_c.map" --specs=rdimon.specs -Wl,--start-group -lgcc -lc -lc -lm -lrdimon -Wl,--end-group -o "_c.elf" ./src/main.o ./src/startup_ARMCM3.o
    arm-none-eabi-gcc.exe: rdimon.specs: No such file or directory
    cs-make: [_c.elf] Error 1
    7. Remove in linker settings "--specs=rdimon.specs" and "-lrdimon" flags, try to build ok.
    8. Delete Debug folder appered after build. And add new folder in it - Advanced - Link to alternate location - browse for d:\prj\obj\Debug
    9. Build - cs-make:
    No rule to make target `all'. Stop.

     
    • First of all I cann't reproduce steps from ttorial - http://gnuarmeclipse.livius.net/blog/test-project/ - for "Hello World ARM Cortex-M3 C Project".

      why? I just retried all the documented steps on my Mac and they are correct

      So I tried for "ARM C".

      tried this one too on my Mac, and it built correctly with the GNU Tools for ARM Embedded Processors toolchain

      I use "Sourcery CodeBench Lite for ARM EABI (arm-none-eabi-gcc)"

      sorry, if you do not follow the documented steps, you are on your own

      Program "cs_make" not found in PATH

      oops! this is a bug. I fixed it, you can use the new version by installing new software from 'http://gnuarmeclipse.sourceforge.net/updates-test'

      And add new folder in it - Advanced - Link to alternate location - browse for d:\prj\obj\Debug

      ah, you want to use Eclipse links. as far as I know, you cannot change the location of the Debug/Release folders, and I don't think that trying to cheat with Eclipse links will work, not at least with the current Eclipse.

      sorry, this does not seem to be a problem with the plug-in. can we close the ticket?

       
  •  glory_man
    glory_man
    2014-02-20

    I use Eclipse Indigo with earlier version of gnu-arm plugin. And use in projects such linked folders, and all work fine. It seems something changed in eclipse.

    can we close the ticket?

    Yes

     
    Last edit: glory_man 2014-02-20
    • as I suggested earlier, if you have a configuration that works with any other toolchain, supported by the standard CDT plug-ins, and does not work with GNU ARM Eclipse, please let me know to investigate, otherwise I can be of little help for CDT problems.

       
    • status: accepted --> closed