Fix string comparison to use [[ ]] since bashisms are in use anyway.

[rpavlik]

The == for string equality checking, I believe, is bash syntax - in any case, with the normal sh single-[] syntax, I got:

$ ./xpacks-paths.sh
MINGW64_NT-10.0 not supported

on "git bash" when there's clearly a case intended to handle it. Switching to the bash [[ ]] syntax seemed to fix at least that part.

[ilg-ul]

can you better explain this patch? as far as I know, the [[ ... ]] syntax uses pattern matching.

the xpacks-paths.sh script is not intended to be executed directly, but included with source in the generate.sh script, which uses bash.

[rpavlik]

Ah, good call - I thought that the [[ ]] syntax was required to get "bash-specific" test builtin behavior, but it seems like you're right: https://unix.stackexchange.com/questions/248164/bash-if-syntax-confusion

In any case, you do use the double brackets elsewhere, and switching to double brackets solved the problem - perhaps switching to a single = would have also done so.

You caught me - my quotation wasn't precise, I had sourced it, lacking any apparent "generate" script... (Trying to get started using this stuff since GNU-MCU-Eclipse works so slick, but having some difficulty.)

[rpavlik]

Ah ha - so when I used a generate script from the sample eclipse projects, it did the same thing, but this time I tried echoing the substring - turns out it was off by one. I'll open a new PR fixing the real problem.