-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Changing Build Path Breaks ESP8266 build. #8106
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
Comments
You can try this patch. It builds but I didn't test it on hardware: --- a/ports/esp8266/boards/esp8266_common.ld
+++ b/ports/esp8266/boards/esp8266_common.ld
@@ -144,7 +144,7 @@ SECTIONS
*shared/timeutils/*.o*(.literal*, .text*)
*drivers/bus/*.o(.literal* .text*)
- build-*/main.o(.literal* .text*)
+ *main.o(.literal* .text*)
*fatfs_port.o(.literal* .text*)
*gccollect.o(.literal* .text*)
*gchelper.o(.literal* .text*)
@@ -182,7 +182,7 @@ SECTIONS
*/frozen.o(.rodata.mp_frozen_content) /* frozen modules */
/* for -mforce-l32 */
- build-*/*.o(.rodata*)
+ *.o(.rodata*)
_irom0_text_end = ABSOLUTE(.);
} >irom0_0_seg :irom0_0_phdr |
Thanks Damien, but I am rather embarrassed to tell you that I have never applied and patch and don't know how :-( I tried saving it to a file and running it with:
But that prompts me for a file name and I thought the file name is contained in the file ?? |
You can do it by hand, just remove the |
Thanks, yes but I have a LOT of scripts to build a docker image and really need to automate everything. Build of esp32 also just failed, I switched back to to using the default build path and again, problem went away. Chances are there will be other ports that fail as well, I guess there's no global fix for this ?? |
All ports except esp8266 should build in any directory. This is already all automated by the |
See #8107 for a fix for this issue. |
Hmmm rp2 fails for me when using a custom path, when I use the default path it succeeds:
|
2 Builds from same folder:
|
The RP2 problem appears to be caused by locales, not sure why it's only a problem when using a custom build path, but installing and setting locales solved this problem.
|
Uh oh!
There was an error while loading. Please reload this page.
My apologies for all the recent issue, but I am building a new docker container for building ALL micropython ports with an easy to use interface, and so I need to change some default paths and use different O/S than may have been used when for example the esp8266 open sdk was last updated.
Anyway, I have made good progress and most is working, however I have just changed the BUILD PATH from the standard:
$BUILD-build
relative pathTo an absolute path in my working folders i.e.
\usr\share\pydev\work\boards\$PORT\$BOARD\build
.This new env var $BUILD_PATH then gets set in the make command:
make .....other-args BUILD=$BUILD_PATH
And on building the esp8266 it results in this:
As soon as I restore my custom build path override to the default, everything works again.
Any idea on the cause and a fix ?
The text was updated successfully, but these errors were encountered: