#54 Possibility to set default toolchain path using external properties files.

Time Permitting
closed-fixed
None
3
2014-07-19
2014-06-16
Iulia Vasii
No

In version 2.1.1 the toolchain path mechanism has changed and moved outside .cproject. A new preference page was created - 'Template Default Values' - to view/edit toolchain paths.
The request is to find a way to set the toolchain path externally: using Eclipse preferences support perhaps to allow direct manipulation of the toolchain path.

Discussion

    • status: open --> open-accepted
    • assigned_to: Liviu Ionescu (ilg)
     
  • In version 2.1.1 the toolchain path mechanism has changed and moved outside .cproject.

    not very accurate, the toolchain path was never stored inside .cproject, they were also present there by a mistake, the authoritative setting was in the workspace.

    A new preference page was created - 'Template Default Values' - to view/edit toolchain paths.

    not very accurate either, this page is not part of the GNU ARM Eclipse plug-ins and was never intended to change toolchain paths. you must be missing something.

    The request is to find a way to set the toolchain path externally: using Eclipse preferences support perhaps to allow direct manipulation of the toolchain path.

    that is a valid proposition, I'll investigate for a possible implementation.

     
    Last edit: Liviu Ionescu (ilg) 2014-06-16
  • Iulia Vasii
    Iulia Vasii
    2014-06-16

    Seeing it there, I had the impression the path is stored in the .cproject. My fault.

    Regarding the preference page, which one did you add actually? I read the original request:
    https://sourceforge.net/p/gnuarmeclipse/feature-requests/30/
    "add a page in the preferences windows to view/edit toolchains paths"

     
  • which one did you add actually?

    project Properties -> C/C++ Build -> Settings -> the Toolchains tab, the Global/Per project path settings.

     
  • Iulia Vasii
    Iulia Vasii
    2014-06-16

    The Toolchain tab existed before, you just updated its content accommodating the new new path settings. Ok, it's clear now.

     
    • that's correct.

       
  • Iulia Vasii
    Iulia Vasii
    2014-06-24

    Is there any chance to implement this in next release? Thanks!

     
    • it is on my TODO list, but I did not start work on it yet.

       
  • Iulia Vasii
    Iulia Vasii
    2014-06-25

    Hi, it works as described in the wiki. But I was thinking to be able to set the default paths for every toolchain, e.g:
    toolchain.name=<id name="" or="" something="" of="" toolchain1="">
    toolchain.path=<default path="" of="" toolchain1="">
    toolchain.name=<id name="" or="" something="" of="" toolchain2="">
    toolchain.path=<default path="" of="" toolchain2="">
    ...

    The current solution is not very flexible.

     
  • Iulia Vasii
    Iulia Vasii
    2014-06-25

    My example got lost somehow, re-sent:
    toolchain.name=<id name="" or="" something="" of="" toolchain1="">
    toolchain.path=<default name="" of="" toolchain1="">
    toolchain.name=<id name="" or="" something="" of="" toolchain2="">
    toolchain.path=<default name="" of="" toolchain2="">
    ...

     
  • Iulia Vasii
    Iulia Vasii
    2014-06-25

    Re-sent:
    toolchain.name=(id/name or something of toolchain1)
    toolchain.path=(default name of toolchain1)
    toolchain.name=(id/name or something of toolchain2)
    toolchain.path=(default name of toolchain2)
    ...

     
  • I would consider the syntax

    path.{id}={path}

    the ID is the same as in the Template default values, and, technically, represents the Java hash of the toolchain name.

    could you tell me the use case that requires such definitions? I thought you use only one toolchain, now you need multiple paths? how are your toolchains named?

     
    Last edit: Liviu Ionescu (ilg) 2014-06-25
  • Iulia Vasii
    Iulia Vasii
    2014-06-25

    We use now:
    Linaro AArch64 bare-metal ELF (aarch64-none-elf-gcc)
    and
    Linaro AArch64 Linux GNU (aarch64-linux-gnu-gcc)

     
  • Iulia Vasii
    Iulia Vasii
    2014-06-25

    The use case is we are working with bare-metal projects (aarch64-none-elf-gcc toolchain) and linux application debug projects (aarch64-linux-gnu-gcc toolchain).

     
  • I see.

    I updated the wiki pages and the implementation to reflect setting multiple paths.

     
  • Iulia Vasii
    Iulia Vasii
    2014-06-26

    It works nicely, thank you for the quick fix!

     
    • status: open-accepted --> closed-fixed
     
  • fixed in 2.3.1-201407120554

     
  • file name changed to toolchains.prefs in 2.3.2-201407190854