I would like to have posted this in MCU IDE, Tools & Compiler, but the +NEW button is missing today.
I exported a project with Renesas FSP Export and then imported it to a different computer using Import Existing Projects into Workspace.
When I compile it it get this error:
"[ERROR] Toolchain configured for project is not currently available. Please add/enable toolchain through Renesas Toolchain Management or select a different toolchain for this project."
I can't seem to find Renesas Toolchain Management in any of the drop-down menus, when I type it into the Search box of "help" it draws a blank.
There are at least two places where you can manage the toolchain. You first need to right click on the project name and select the "Properties" which is the last line in the pop-up menu.
Then expand the "C/C++ Build" list and see the "Tool Chain Editor" there.
Also you can select the "Settings" point and then switch to the tab "Toolchain"
If this response, or one provided by another user, answers your question, please verify the answer. Thank you!
Renesas Engineering Community Moderatorhttps://community.renesas.com/https://academy.renesas.com/https://en-support.renesas.com/knowledgeBase/
In Sergey's response it will at least tell you what toolchain the project was originally use.
After that you can locate and download the toolchain online and install it on your Pc. I do suggest that you do this with e2 studio not running. By doing this when you start e2 studio again it will detect that you have installed a new toolchain.
Thanks. The "exporting" computer is running last year's E2Studio, the "importing" computer is running the 2023 version with the latest toolchains.
instead of regressing to last year's toolchains, it is possible to tell the "importing" computer just to use the toolchains that is has (which are the most up-to-date)
> "[ERROR] Toolchain configured for project is not currently available. Please add/enable toolchain through Renesas Toolchain Management or select a different toolchain for this project."You should do either install and integrate exact toolchain version or choose toolchain version you already integrated.Anyway, you need any of toolchain first, since e² studio is only IDE.See the following FAQ pages about toolchain integration.FAQ - How can I update my compilers with e² studio update program?https://en-support.renesas.com/knowledgeBase/16979396FAQ - To enable the use of toolchains in e² studiohttps://en-support.renesas.com/knowledgeBase/16979421FAQ - ‘Program "make" not found in PATH’ error when attempting to build an imported projecthttps://en-support.renesas.com/knowledgeBase/18398339
> I can't seem to find Renesas Toolchain Management in any of the drop-down menus, when I type it into the Search box of "help" it draws a blank.Go to Help menu -> "Add Renesas Toolchains",or open workspace property dialog (via Window menu -> Preferences), then search for Renesas -> Renesas Toolchain Management.
pilot answers himself in the following post:
"I fixed it by selecting the "ARM(AArch64)" option and then re-select the "ARM(AArch32)" again. Then the compilation"
Why do I need to add more toolchain? For projects which were started on this computer, it has all the toolchains it needs,
This error occurs because the initial project was created in a different toolchain version than the toolchain version your computer has. Open the configuration.xml file to see the original toolchain version of the project.
E2studio will use the version of the toolchain you have installed, but show the warning about the toolchain version the project was created with not being available.
As long as the build completes with "0 errors" it should not worry you. However, if you want this warning to disappear you need to install in your PC and select from setting the original toolchain version.
Please check Jeremy's answer on community.renesas.com/.../ek-ra6m4-sample-project-error-toolchain-configured-for-project-is-not-currently-available
If so, then, to be consistent with the all the other compiler terminology, should it not say "Warning" and not "Error"?
Yes, I think the term "Warning" would be more appropriate.
I see this message very often when I import projects and never encountered an issue as long as the build completes.