Open MdB-3 opened 3 years ago
Hi @MdB-3, apologies for the long delay here.
We recently updated the windows installation instructions on the Wiki.
If you could share more details about the issue you were having (i.e. a screenshot of the Max Console when running oopsy in verbose mode) we can help get it sorted out.
The make -n
that is done within oopsy was (and may still be) necessary due to the version of Make not functioning correctly when called from cmd.exe (the shell used when oopsy calls system commands). The output of the each line of the dry-run invocation of Make is piped out to cmd.exe individually, and should function correctly.
Hi Stephen,
The problem I was experiencing had to do with os.EOL being used to split the make -n output into executable commands. Using '\n' instead corrects this (possibly 'cause I had my Cygwin bin in my path)..
When following the new installataion instrcutions for Windows this problem was solved.
But still a glitch remains in the build and flash sequence (see the Max console log below).
Regards, Marcel du Bois newtools.txt
"(see the Max console log below)" -- can't see the log here.
There's a file attached (newtools.txt) to the previous comment
Just to clarify things: building and flashing works fine now. The remaining glitch just causes the flashing to be attempted twice.
On a Windows host the automatic build + download is not working. The soure/oopsy.js script performs a "make -n" i.s.o. a "make" (line 254).