Right now, I have installed
gcc-arm-none-eabi on the Bash on Ubuntu on Windows system. In the future, I plan to use it much more, but currently, I use bash mainly for
make all for this project right now (and
echo hi for testing bash).
The big problem is that I cannot even get into the bash environment via Atom. Whenever I try to enter, it seems Atom doesn’t have the permissions to access the
bash.exe executable. Node’s
child_process.spawn (or similar function) will return something along the lines of check if the executable exists your that you have sufficient permissions and even the
cmd /c [command] way returns ‘bash’ is not recognized as an internal or external command, operable program or batch file.
There have currently been 4 ways I have tried to start bash via Atom:
- via the Build package and a custom build command
- via the Script package and a test batch file
- via the
init.coffee script and Node’s
- via the PlatformIO terminal (just because you mentioned it)
all with multiple test commands (
bash 'echo hi',
cmd \c bash 'echo hi',
dir C:\Windows\System32\bash.exe), and yet none of them can access bash.
However Eclipse (with some finagling) was able to enter bash, it just couldn’t handle the output (error 0x8070057) as Eclipse used an old version of the command line (there are sometimes workarounds). Also, just starting Command Prompt from the Start menu lets me access bash. I have a feeling that somehow, Atom’s security principle is not included on the
bash.exe file. I just don’t know how to find Atom’s security principle.
bash.exe allows execution from:
- ALL APPLICATION PACKAGES
- ALL RESTRICTED APPLICATION PACKAGES
Now I suppose I could edit these security settings, making it so that Everyone could access bash, or if I find Atom’s security principle, just Atom instead. However, I am running Windows Insider, and programs like bash get updated frequently, so to my knowledge, these modified permissions wouldn’t stay. I would like to find a more permanent solution instead if possible.
I started using the
dir command to check if the command line had the right permissions to access bash, since I was able to narrow the problem down to permissions, and because it’s harder to mess up syntax with (no weird escaping characters or strings). At this point I can’t even see or access the bash file from Atom at all.
If I need to, I can upload my code to Mega, but I have no problems with it when running commands from the Command Prompt, so it seems irrelevant.
(also, sorry about the lack of information, I’m still getting used to participating in forums)