Closed woobagooba closed 5 years ago
Windows indicated Mbed CLI is installed. "mbed help" at command line is saying not recognized as internal or external command.
Further update (as we are working to provide a set of correct install instructions ) ...
For some unknown reason, Mbed CLI will not install on a particular Win 10 system. Separate issue has been opened. https://github.com/ARMmbed/mbed-cli/issues/883
We are able to install Mbed CLI on a different Win 10 system. We have worked the install through to the point that the mbed-simulator demo builds fail (all of them). libmbed build fails due to Windows Error 206 ... filename to long. Tried install of mbed simulator and emscriptem as subfolder of C:/ .... no joy.
Please advise next steps.
@woobagooba I've been able to reproduce this issue with a "clean" Windows 10 install (64-bit), after applying all updates. As noted in this issue: https://github.com/ARMmbed/mbed-cli/issues/883 you can manually fix the problem by running "pip install mbed-cli".
@j3hill do you mean "pip install mbed-cli" resolves the mbed cli not installing issue? Or do you mean it also fixes the Mbed OS simulator compilation issue? I assume you mean the former, which means there is still a stopper issue with the compilation failures and the file name too long error.
New week, fresh start, no joy.
Removed the entirety of previous Mbed OS sim install, including Mbed CLI and Emscriptem. Made sure long filenames are enabled on Win10. Restarted. Fresh install of Mbed OS sim (including Mbed CLI and Emscriptem) Install fails at the demo build step. libmbed will not build, windows 206 error thrown by emcc/python. Best we can determine, the only way around this is to use python 3.6 or later. We are therefore left with the conclusion that Mbed OS sim is not compatible with Win 10.
@woobagooba Thanks for reporting. I've used the simulator in Windows in the past, but main development is on macOS and Linux, so haven't used it recently. Based on the error I assume you're overrunning the 259 character limit for file names which exists in Windows. Which folder have you installed the simulator in? Is it possible to move it to a location where the total file name will be lower (e.g. throw it in C:
?). Alternatively, I think Cygwin does not have the file name limit, that would be an option.
Why a local build and install? To operate mbed-simulator with NS other than TTN.
See my comment in https://github.com/janjongboom/mbed-simulator/issues/30#issuecomment-480815636
There are two sets of build instructions with are sparse, differ, overlap, and will not work for us.
Use the version in README in this repository for reference.
Alright, I've found the issues and have pushed a fix here: https://github.com/janjongboom/mbed-simulator/pull/33. The new release is 1.9.5. Thanks for reporting again!
Thanks Jan
Your install instructions need to be consolidated into a single place and verified for correctness.
Please re-open
I'm moving this to a new thread
Dear @woobagooba please, can you say me which version of Emscripten are you using? I'm trying to install mbed simulator offline, but it doens't work. I obtain a fatal error, probably due to the last version of emcc. At present time, the version reccomended by janjongboom is not present anymore.
Sorry, but my team long ago gave up on Emscripten and Mbed Simulator.
Too much time spent fighting with the build issues.
On 4/24/2020 10:00 AM, knish82 wrote:
Dear @woobagooba https://github.com/woobagooba please, can you say which version of Emscripten are you using? I'm trying to install mbed simulator offline, but it doens't work. I obtain a fatal error, probably due to the last version of emcc. At present time, the version reccomended by janjongboom is not present anymore.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/janjongboom/mbed-simulator/issues/32#issuecomment-619028317, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA32UFSS6BCQLUABKBVJSNTROGLRHANCNFSM4HEWHLRA.
I understand your point, thank you for your reply. So, did you find some other alternative to offline mbed simulator? Thank you again @woobagooba
First, thank you for this work. We see value in it ... if we can get past our local build and run troubles.
Why a local build and install? To operate mbed-simulator with NS other than TTN.
There are two sets of build instructions with are sparse, differ, overlap, and will not work for us. Here (https://os.mbed.com/blog/entry/introducing-mbed-simulator/) "Offline" and here (https://github.com/janjongboom/mbed-simulator)
The latter instruction set directs to install "recent" version of node ... ? Mbed CLI pulls in its version of Python. Emscriptem pulls in its own version of Node and Python. We are getting runtime errors that Mbed CLI is not installed ... it is.
Much appreciated and useful to the general community if could Docker-ize mbed-simulator ... a useful Quick Start.