#53 Provide toolchain settings through headless build

Version 1.x
closed
None
5
2014-07-07
2014-05-05
Roel
No

Hi,

We're invoking builds from a continuous integration server (Jenkins) using the eclipse headless build feature. There're multiple build jobs configured each with their own private workspace. Jobs are running in parallel to each other so multiple eclipse builds can be run at the same time.

We're facing a problem that sometimes during the middle of the build the compiler command could not be resolved anymore; 'arm-none-eabi-gcc: command not found'. Our eclipse projects are configured to resolve the toolchain from the windows path. I've read in the gnu-arm documentation that this is not recommended so I would like to configure the toolchain path through the gnu-arm settings.

Our Jenkins build jobs are configured to clean up all local changes before invoking an eclipse build, effectively removing the eclipse workspace as well. This is to make sure we always have a clean build environment. Is it possible to provide the toolchain path through the eclipse command line invocation?

Discussion

  • Liviu Ionescu (ilg)

    Is it possible to provide the toolchain path through the eclipse command line invocation?

    sure, the plug-in does nothing to prevent this, it just adds the per toolchain or per project path to the global path, if defined.

     
  • Liviu Ionescu (ilg)

    Roel, I read again your message and I think I misunderstood it.

    I guess you asked if I implemented any special feature to pass the toolchain path via a command line option.

    No, I did not, but it is not necessary, you can pass the toolchain path to the CI server via the usual environment path.

    If you have any more questions, please let me know.

     
  • Liviu Ionescu (ilg)

    any new input on this issue?

     
  • Liviu Ionescu (ilg)

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

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

Sign up for the SourceForge newsletter:





No, thanks