Andre Leiradella

I get it know, thanks for the detailed explanation.

My first thought was that it could have something similar to `ungetc` to backtrack one byte, then you could just `win->dasm.cur_addr--; win->dasm.bin_pos--;` without the disassembler having to store any state.

Ah, it's always possible to get the instruction bytes by using the PC passed to the disassembler and the next PC that it returns, so maybe `ungetc` is not even...

I've added double quotes surrouding the path at [build_android, line 183](https://github.com/cocos2d/cocos2d-console/blob/v3/plugins/plugin_compile/build_android.py#L183): ``` command = "%s update project -t %s -p \"%s\"" % (cocos.CMDRunner.convert_path_to_cmd(sdk_tool_path), target_str, manifest_path) ``` and now it works...

Oops, talked too soon. There are other places where paths with spaces cause problems. I'll update this issue if I can fix them.

I've added double quotes to lines 296, 299 and 301, but: ``` Android NDK: ERROR: You NDK_MODULE_PATH variable contains spaces Android NDK: Please fix the error and start again. ```...

This is in addition to loading/saving states to arbitrary files, right? I think it will only work when we have OSD messages.

I believe they were put there to make everything work out-of-the-box, and that the fetch script exists just to update them. @meleu can you confirm this?

I'll leave @meleu @Jamiras and @GameDragon2k decide what to do about this. My development machine runs Linux. I just don't think removing them from the repo and adding instructions to...

I think they being in the `bin` folder also means that they are the "good" set, that have been tested and are known to work. I'll let the other devs...