-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error occurs when building exported mbed-os programs on e2studio #7155
Comments
ARM Internal Ref: MBOTRIAGE-568 |
Probably, it is related this? |
@toyowata That's a good guess, but I was under the impression that GNU MCU Eclipse could handle the extra long paths without issues. |
Also, you'll notice that the error is different in this issue than in #7129 |
I verified Export by following two patterns.
As the result of it, the following build error was shown.
By Mbed CLI
As the result of it, the following build error was shown("No such file or directory" error is not shown and the same "--wrap" error as above is shown).
To summarize the above, I think that check point is the below.
|
@TomoYamanaka That's not an "unnecessary include path", that's the include paths from the |
I investigated several points. With respect to "No such file or directory" error :
It seems like there is something issue with export from Online, could you let me know your opinion on this ?
As the result of it, the build was successful. |
@theotherjimmy |
@theotherjimmy |
Sorry about that @TomoYamanaka #7410 is not related to this. It may look like it because "exporter" but that's where the relevance stops. Here's some pointers that may help you resolve the problem yourself:
|
Could you help me to resolve the following two points because this is a blocker for Renesas Mbed user's activity?
|
@TomoYamanaka You could extend the jinja template to include the |
Thanks for the reply @theotherjimmy. @TomoYamanaka as for --warp problem since e2 studio template extends gnu arm eclipse template, I'll update the jinja template on GNU ARM exporter to fix both. As for not adding include paths (No such file or directory error) I am not sure why some include paths are added but not others. I can look into it the next week. Thanks |
@phyokyaw The missing include paths are related to features that are disabled. They're supposed to show up in the export (if I recall correctly), and be disabled. It looks to me like the e2studio is missing the second part. |
@phyokyaw The e2studio template does not extend the GNU ARM Eclipse template. It does use the same variables though. |
@phyokyaw @theotherjimmy Thank you for your comments. |
Hi @theotherjimmy, Thank you for your comment. I am looking into the issue regards to excluding source files to see why there are "No such file or directory" errors. When we export using mbed-cli
However in .cproject file exported from online compiler contains
Hence the compiler is not excluding the ignored files/directories. Looks like its referencing paths from online mapped repo rather than local path. Do you have view on how to make the excluded items reflect the correct path? Is there a way we can convert the top path for excluded_folders in
Thanks |
@phyokyaw Thanks for looking into this. I'll take a look at why that's going wrong. |
Just for FYI, I also noticed that in 5.9 mbed-os/features/nanostack/sal-stack-nanostack/source/configs folder is missing for Web exporter. The problem has been reported for other exporters. https://os.mbed.com/questions/81597/Problems-when-exporting-to-uVision5-with/ https://os.mbed.com/forum/bugs-suggestions/topic/32790/?page=1#comment-58923 Once I manually copied the configs/ folder and resolved the excluded path I am able to build and debug from the exported project. Thanks |
👍 This issue was reported here #7615. It shall be fixed for 5.9.5 |
@phyokyaw |
@theotherjimmy Please review the PR if possible. This is to fix the --wrap error. Thank you. |
@theotherjimmy |
@theotherjimmy
Would you please tell us update about the above? |
@theotherjimmy is out of office this week. @cmonr Who else could help? |
@TomoYamanaka The issue with |
And the |
See #8303 for the |
@theotherjimmy Thank you for your update. We'll check #8303. |
Internal Jira reference: https://jira.arm.com/browse/IOTCORE-14 |
I checked whether this issue could be solved by exporting
Also, in the .cproject file exported from Online Compiler, I found that a part of excluding path is still mapped online path, not local path. (expected path is local path and this path by CLI is local path) Although the solution PR #8303 was already merged into Mbed OS 5.10.3, could you make sure whether this contents reflected to Online Exporter environment? |
@TomoYamanaka #8303 is not in the online compiler. |
I'm in trouble with export from online so I'll be very grateful if you could help me. My understanding is that PR #8303 solves to generate unusable project file from online compiler, and this solution should be applied to online environment not only mbed-os/tools. Also I know there is time rag regarding merge into online exporter. Are those correct? |
I'm actually confused as well. @theotherjimmy This is at least in 5.10.3, correct? I'm missing the disconnect as well. |
I don't see what's so confusing. This is in 5.10.3. This is not in the online compiler. |
Could you tell me why this is not in the online compiler? |
Because that requires a tools-release that has not been made. I'll be making a tools release for 5.11.0, and updating the online compiler to use that in the future. |
Thank you for your reply. I understood that PR #8303 will be incorporated into next tools-release (the timing is in synchronization with mbed os 5.11.0). May I ask you something? Is the next tools-release that you mentioned different from tools-release-5.11.0-rc1 ? |
Yes. tools-release-5.11.0-rc1 is based on mbed-os-5.11.0-rc1, and the next tools release will be based on mbed-os-5.11.0. |
Although tools-release-5.11.0 was already released, when I build mbed-os-example-blinky after exporting from Mbed Online Compiler to e2studio, I faced this issue yet. Could you check to whether this tools-release took into Online Expoter? |
@TomoYamanaka The tools release for 5.11 is not yet in the online compiler. |
When will it be ready? We will be grateful if you could let me know the scheduled date that is incorporated to Online Compiler. |
Thank you for continued support, I confirmed this issue was finally solved. |
Description
I faced the several build error when compiled the exported mbed-os programs on Renesas' IDE e2studio.
The build errors are a bit different by programs, but I frequently look messages such as "No such file or directory".
The procedure is as follows:
The error that is shown when building exported
mbed-os-example-blinky(mbed os 5.8.5)
on e2studio is as follows:With respect to file of "No such file or directory", it seems that file was exported but not included headers in the include paths.
Anyway, I think that this should not be the expected behavior, could you confirm the above?
Issue request type
[ ] Question
[ ] Enhancement
[X] Bug
The text was updated successfully, but these errors were encountered: