#52 Plug-in does not work in 3.7.2 (spaces in project name)

Version 0.5.4
closed-fixed
Build (20)
5
2013-10-18
2012-02-27
fubo
No

After a clean an rebuild, I am getting some errors using Indigo 3.7.2:

Errors occurred during the build.
Errors running builder 'CDT Builder' on project 'xxx'.
java.lang.IllegalArgumentException

I use Win7 x64 and Eclipse SR2 x32.

Discussion

  • Liviu Ionescu (ilg)

    what toolchain are you using, and what version of the plug-in you have?

     
  • Liviu Ionescu (ilg)

    • assigned_to: nobody --> ilg-ul
    • labels: --> Build
     
  • fubo

    fubo - 2012-02-27

    Toolchain: Sourcery Codebench Lite.
    Plug-in version: tried 201112030833 (that works with Eclipse 3.7.1) and 201202210114.

     
  • Liviu Ionescu (ilg)

    later in the evening I'll try to replicate it and let you know.

     
  • Liviu Ionescu (ilg)

    • status: open --> open-accepted
     
  • fubo

    fubo - 2012-02-28

    I just tried to update the plugin in Eclipse 3.5.1 (starting version was 0.5.4.201112030833) under winxp 32bit, and downloader installed also some CDT updates. I got same error. Reverting to 2011 version.

     
  • Liviu Ionescu (ilg)

    unfortunately I'm not able to replicate your problem.

    I freshly installed
    - a Win7 32bit virtual machine
    - arm-2011.09-69-arm-none-eabi.exe
    - eclipse-cpp-indigo-SR2-incubation-win32.zip
    - 0.5.4.201202210114

    my simple test project builds as expected, without errors in the workspace log

    **** Build of configuration Debug for project t1 ****

    cs-make all
    'Building file: ../C1.cpp'
    'Invoking: ARM Sourcery Windows GCC C++ Compiler'
    arm-none-eabi-g++ -O0 -Wall -Wa,-adhlns="C1.o.lst" -fno-exceptions -fno-rtti -c -fmessage-length=0 -MMD -MP -MF"C1.d" -MT"C1.d" -mcpu=cortex-m4 -mthumb -g3 -gdwarf-2 -o "C1.o" "../C1.cpp"
    'Finished building: ../C1.cpp'
    ' '
    'Building file: ../dummy.c'
    'Invoking: ARM Sourcery Windows GCC C Compiler'
    arm-none-eabi-gcc -O0 -Wall -Wa,-adhlns="dummy.o.lst" -c -fmessage-length=0 -MMD -MP -MF"dummy.d" -MT"dummy.d" -mcpu=cortex-m4 -mthumb -g3 -gdwarf-2 -o "dummy.o" "../dummy.c"
    'Finished building: ../dummy.c'
    ' '
    'Building file: ../main.cpp'
    'Invoking: ARM Sourcery Windows GCC C++ Compiler'
    arm-none-eabi-g++ -O0 -Wall -Wa,-adhlns="main.o.lst" -fno-exceptions -fno-rtti -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.d" -mcpu=cortex-m4 -mthumb -g3 -gdwarf-2 -o "main.o" "../main.cpp"
    'Finished building: ../main.cpp'
    ' '
    'Building target: t1.elf'
    'Invoking: ARM Sourcery Windows GCC C++ Linker'
    arm-none-eabi-g++ -Wl,-Map,t1.map -mcpu=cortex-m4 -mthumb -g3 -gdwarf-2 -o "t1.elf" ./C1.o ./dummy.o ./main.o
    'Finished building target: t1.elf'
    ' '
    'Invoking: ARM Sourcery Windows GNU Create Flash Image'
    arm-none-eabi-objcopy -O ihex t1.elf "t1.hex"
    'Finished building: t1.hex'
    ' '
    'Invoking: ARM Sourcery Windows GNU Create Listing'
    arm-none-eabi-objdump -h -S t1.elf > "t1.lst"
    'Finished building: t1.lst'
    ' '
    'Invoking: ARM Sourcery Windows GNU Print Size'
    arm-none-eabi-size --format=berkeley t1.elf
    text data bss dec hex filename
    2636 1300 84 4020 fb4 t1.elf
    'Finished building: t1.siz'
    ' '

    **** Build Finished ****

     
  • Liviu Ionescu (ilg)

    > Eclipse 3.5.1 ... 0.5.4.201112030833 ... I got same error.

    0.5.4.x requires CDT 8.x, I doubt this works in 3.5.x

     
  • fubo

    fubo - 2012-02-29

    Sorry! I meant 3.7.1! And I must correct: with 3.7.1 and a fresh installation (from zip file) it works.
    Some more info. I am
    - running win7 64bit or winxp 32bit
    - using java 1.6.0b31 32 bit JVM
    The issue often happen when I do clean and then build.

     
  • Liviu Ionescu (ilg)

    reading again your initial message, I noticed you are using Win7 x64, while my test was on Win7 x32.

    unfortunately I don't have a Win7 x64 instance at hand, but could you retry the test on a Win7 x32, eventually on a fresh configuration?

     
  • fubo

    fubo - 2012-02-29

    I don't have Win7 x32 as well...
    Could you test on XP 32bit? Do you confirm you're using JVM 1.6.0b31?

     
  • Liviu Ionescu (ilg)

    I'm currently using Version 6 Update 30 (build 1.6.0_30-b12)

     
  • Liviu Ionescu (ilg)

    It seems the new Java has a problem, after upgrading to latest (build 1.6.0_31-b05), I see many java.lang.IllegalArgumentException in the logs, but none seem related to the plug-in.

     
  • fubo

    fubo - 2012-02-29

    Hmmm...
    at least you saw the issue. So I will try reverting to b30.

     
  • Liviu Ionescu (ilg)

    I tried to investigate the problem, but, strangely enough, on the same 31-b05, with exactly the same eclipse archive, and the same plu-in fetched from the update site, the problem does not repeat.

    I have 6 Eclipses in total, but only one fails, all other 5 build properly the test project.

    Could you try to install a fresh Eclipse (eclipse-cpp-indigo-SR2-incubation-win32.zip) and try again with the latest Java and the latest plug-in?

     
  • fubo

    fubo - 2012-03-01

    I think I found the issue. It is a combination of different things.
    I was able to let it work if I do not use spaces in project name. If I change the name from "micro target" to "micro_target", and no space is in the path, the SR2+JRE160b31+GNUARM201202210114 works. It also works with JRE170b3.
    Spaces were working in SR1+JRE160b31+GNUARM201112030833.
    I was able to address the issue because JRE170b3 was reporting different error regarding path not valid...

     
  • Liviu Ionescu (ilg)

    I cannot confirm your suggestion, in my environment I have no problems with spaces in the workspace PATH:

    C:\Users\admin\Desktop\GNU ARM Eclipse Test\workspace space

    However, spaces in the project name are a known problem, and should not be used

    So, we have no obvious, repetitive problem.

    My feeling is that, somehow, the Eclipse folder gets corrupted, and after this happens the build crashes with exception.

    If so, the workspace should not be affected, and installing a fresh Eclipse should cure it.

    Could you try this, as already suggested before?

     
  • fubo

    fubo - 2012-03-04

    And in fact now it is working by avoiding spaces in project names. However, another toolchain plugin does not have issues with spaces.

     
  • Liviu Ionescu (ilg)

    • summary: Plug-in does not work in 3.7.2 --> Plug-in does not work in 3.7.2 (spaces in project name)
    • status: open-accepted --> closed
     
  • Liviu Ionescu (ilg)

    Projects with spaces in project names were fixed from 0.5.5.201309281715, but requires a CDT patch that will be available with the next Eclipse.

     
  • Liviu Ionescu (ilg)

    • status: closed --> closed-fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks