Update DevSetup.md for Android

[rh101]

Describe your changes

The instructions in the DevSetup state that r23c is the minimum, which may make developer assume that it would be set as the default, which is not the case, since the default configured NDK is r23d in https://github.com/axmolengine/axmol/blob/dev/1k/build.profiles#L46

To avoid this confusion, instructions have been updated to ensue developers run the setup.ps1 -p android in order to download NDK r23d, just so that they can get up and running with a new project without issues.

Issue ticket number and link

Checklist before requesting a review

For each PR

• Add Copyright if it missed:
  - "Copyright (c) 2019-present Axmol Engine contributors (see AUTHORS.md)."

• I have performed a self-review of my code.

  Optional:

  • I have checked readme and add important infos to this PR.
  • I have added/adapted some tests too.

For core/new feature PR

• I have checked readme and add important infos to this PR.
• I have added thorough tests.

[rh101]

@halx99 There may be an issue on MacOS. If setup.ps1 is run first, then setup.ps1 -p android is run afterwards, it does not download the NDK. It's happened to a few developers so far, and all seem to be using MacOS. Could there be something that is preventing the command from running correctly (such as a cached value etc.)?

[halx99]

@halx99 There may be an issue on MacOS. If setup.ps1 is run first, then setup.ps1 -p android is run afterwards, it does not download the NDK. It's happened to a few developers so far, and all seem to be using MacOS. Could there be something that is preventing the command from running correctly (such as a cached value etc.)?

I will take a look

[rh101]

Sorry, I didn't realise it created the branch in this repo instead mine, so I'll pay more attention to that next time.

[halx99]

@halx99 There may be an issue on MacOS. If setup.ps1 is run first, then setup.ps1 -p android is run afterwards, it does not download the NDK. It's happened to a few developers so far, and all seem to be using MacOS. Could there be something that is preventing the command from running correctly (such as a cached value etc.)?

I will take a look

I can't reproduce it

[rh101]

I can't reproduce it

OK! Then it may just be a configuration issue in their own environment.