-
Notifications
You must be signed in to change notification settings - Fork 238
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
Does not build esp32 samples #104
Comments
Hello - Thank you for the issue report. Based on the console output provided, I am wondering if the ESP-IDF, toolchain and MSYS2 archive has been installed and required environment variables configured. Our Getting Started instructions include an ESP32 setup section that details the steps required. Please let us know if installing the ESP-IDF resolves your issue. Also, it looks like you are trying to build for the moddable_zero platform? If that is the case, then the mcconfig command line needs to include the platform: mcconfig -d -m -p esp32/moddable_zero Regards, |
Yes, I have the idf installed an am building with eclipse for other projects. To clarify the guide because things seem to be mixed. We install MSYS2 then later use the Developer Command Prompt for VS 2017. Are nmake and esp32-gcc supposed to cross build for the esp32 target? I use forward slashes for MSYS2, but nmake is called by mcconfig.bat C:\Users\Documents\Moddable\examples\helloworld>echo %IDF_PATH% C:\Users\Documents\Moddable\examples\helloworld>dir c:\Sloeber\arduinoPlugin\packages\esp32\esp-idf Directory of c:\Sloeber\arduinoPlugin\packages\esp32\esp-idf 11/25/2018 12:34 AM .11/25/2018 12:34 AM .. 11/25/2018 12:24 AM 721 .editorconfig 11/25/2018 12:34 AM 1,044 .gitignore 11/25/2018 12:34 AM 33,246 .gitlab-ci.yml 11/25/2018 12:34 AM 1,455 .gitmodules 11/25/2018 12:34 AM 577 add_path.sh 11/25/2018 12:34 AM components 11/25/2018 12:34 AM 2,313 CONTRIBUTING.rst 11/25/2018 12:34 AM docs 11/25/2018 12:34 AM examples 11/25/2018 12:34 AM 6,454 Kconfig 11/25/2018 12:24 AM 11,560 LICENSE 11/25/2018 12:34 AM make 11/25/2018 12:34 AM 6,610 README.md 11/25/2018 12:34 AM 413 requirements.txt 11/25/2018 12:34 AM tools 10 File(s) 64,393 bytes 7 Dir(s) 170,619,838,464 bytes free C:\Users\Documents\Moddable\examples\helloworld>mcconfig -d -m -p esp32
The system cannot find the path specified. C:\Users\Documents\Moddable\examples\helloworld>dir C:\USERS\DOCUMENTS\MODDABLE\BUILD\DEVICES\ESP32\XSPROJ\SDKCONFIG.DEFAULTS.PRIOR Directory of C:\USERS\DOCUMENTS\MODDABLE\BUILD\DEVICES\ESP32\XSPROJ 11/26/2018 05:34 PM 14,691 sdkconfig.defaults.prior |
Hello - Thank you for the follow-up and additional notes. It is helpful to know that you have the ESP-IDF installed in a different place. The Moddable ESP32 build requires a number of environment variables to be set. The ESP32 setup for Windows documented in our Getting Started instructions covers what is required. My hunch is that one or more of the environment variables might not be properly set. In particular, the IDF_PATH environment variable needs to be set in the MSYS2 environment using forward slashes. See step 7 in the setup instructions. If you additionally set %IDF_PATH% in the Windows environment, that %IDF_PATH% should specify a Windows-style directory path, e.g. c:\Sloeber\arduinoPlugin\packages\esp32\esp-idf. The Windows all-in-one toolchain (see step 3) you downloaded contains the GCC toolchain used to cross-compile the code. This GCC toolchain is used to build both the Moddable runtime and the ESP32 firmware. The mcconfig tool calls NMAKE on Windows to execute the nmake.esp32.mk make file. The make file builds the the Moddable runtime and launches a MSYS2 window to build the ESP32 firmware. Everything is built using command line tools. It is important to follow the prompts in both the Developer Command Prompt and MSYS2 windows. My suggestion is to first try and get the ESP32 build working by following the Getting Started instructions. Steps 1 through 10 are one-time setup. Once that works, you can revisit the build failure issue after seeing how a successful build works. As for the "fatal error", based on the console output provided, I am wondering if the problem is here at line 282 in nmake.esp32.mk: if exist $(TMP_DIR)_s.tmp ($(MSYS32_BASE)\msys2_shell.cmd -mingw32 -c "echo Running GENCONFIG...; BATCH_BUILD=1 DEBUG=$(DEBUG) IDF_BUILD_DIR=$(IDF_BUILD_DIR_MINGW) SDKCONFIG_DEFAULTS=$(SDKCONFIG_FILE_MINGW) make defconfig") If the MSYS32_BASE environment variable is not correct, the make file won't be able to find the msys2_shell.cmd executable. At the top of the nmake.esp32.mk file, you can follow how the various environment variables are used by the make file. Regards, |
I gave up on windows and went back to my ubuntu vm. Had to move the esp32 compiler and idf to $HOME/esp32/... idf examples can find the toolchain through the PATH variable, but moddable does not. Got the idf 3.1 hello-world example building. Built xsbug and the emulator. cd ${MODDABLE}/examples/helloworld box:~/Downloads/moddable/examples/helloworld$ mcconfig -d -m -p esp32 Does not seem to find the lwip idf component by itself. netdb.h is in ~/esp32/esp-idf/components/lwip/lwip/src/include/lwip/ (IDF 3.1). |
Hello - Please make sure your local Moddable repository is up-to-date and double check that you are building against v3.1 of the ESP-IDF. We recently updated our ESP32 build to be compatible with the v3.1 ESP-IDF. The 3.1 ESP-IDF includes multiple lwip directories. Our ESP32 build make.esp32.mk make file looks for lwip include files in these ESP-IDF base directories (lines 65-66):
Regards, |
Brian, Cloned the 3.1 branch specifically. First time build threw error at uecc and bootloader. Ran mcconfig again. It flashed my esp32 and opened xsbug. Hello world example is now running! Thank you very much. |
Windows 10 builds for the simulator, but not for the esp32 target.
"C:\USERS\DOCUMENTS\MODDABLE\BUILD\DEVICES\ESP32\XSPROJ\SDKCONFIG.DEFAULTS.PRIOR" actually exists! But in lowcase.
C:\Users\Documents\Moddable\examples\helloworld>cd %MODDABLE%\examples\piu\balls
C:\Users\Documents\Moddable\examples\piu\balls>mcconfig -d -m -p esp32
Does C:\Users\Documents\Moddable\build\tmp\esp32\moddable_zero\debug\xsProj specify a file name
or directory name on the target
(F = file, D = directory)? d
C:\Users\Documents\Moddable\build\devices\esp32\xsProj\Makefile
C:\Users\Documents\Moddable\build\devices\esp32\xsProj\partitions.csv
C:\Users\Documents\Moddable\build\devices\esp32\xsProj\sdkconfig.defaults
C:\Users\Documents\Moddable\build\devices\esp32\xsProj\sdkconfig.defaults.prior
C:\Users\Documents\Moddable\build\devices\esp32\xsProj\sdkconfig.defaults.release
C:\Users\Documents\Moddable\build\devices\esp32\xsProj\main\component.mk
C:\Users\Documents\Moddable\build\devices\esp32\xsProj\main\main.c
7 File(s) copied
1 file(s) copied.
FC: cannot open C:\USERS\DOCUMENTS\MODDABLE\BUILD\DEVICES\ESP32\XSPROJ\SDKCONFIG.DEFAULTS.PRIOR - No such file or folder
1 file(s) copied.
The system cannot find the path specified.
NMAKE : fatal error U1077: 'if' : código de retorno '0x1'
Stop.
The text was updated successfully, but these errors were encountered: