Revise Windows docs, prefer CMake #691
Conversation
docs/Windows-VisualStudio.md
Outdated
| @@ -100,7 +103,8 @@ There is also a skeleton game project created for you at https://github.com/32bl | |||
| "inheritEnvironments": [ "gcc-arm" ], | |||
| "variables": [], | |||
| "intelliSenseMode": "linux-gcc-arm", | |||
| "cmakeToolchain": "[path...]/32blit-sdk/32blit.toolchain" | |||
| "cmakeToolchain": "[path...]/32blit-sdk/32blit.toolchain", | |||
| "environments": [ { "PATH": "${env.PATH}" } ] | |||
There was a problem hiding this comment.
While that does fix the build, it usually breaks configuring as it resets the PATH set by the "gcc-arm" environment containing the cross tools... (Works after configuring as all the paths are cached)
There was a problem hiding this comment.
I wonder if it can do something like append to the path rather than completely trounce it. I assume you've probably bashed your head against this quite a bit! 😬
There was a problem hiding this comment.
That said, I can't seem to get it to break configuration. Even after deleting the cache.
There was a problem hiding this comment.
Yeah I kept trying to workaround it in 32blit setup... and eventually got annoyed enough to remember my MS account and report it.
There was a problem hiding this comment.
That said, I can't seem to get it to break configuration. Even after deleting the cache.
Possibly finding some other installed toolchain instead of the VS supplied one? It definitely doesn't find the one shipped with VS with that override.
There was a problem hiding this comment.
Oooh that's something to check. Might be prudent to remove the ARM GCC toolchain since that's in my path.
I strongly suspect there wont be a fix for this imminently and we'd have to bless the command-line procedure for actual on-device builds. Which isn't so bad.
Or, I guess, if it's gonna detect ARM GCC and work... that's also fine?
There was a problem hiding this comment.
Hah, maybe it'll work in VS 2022, who knows... There's always VS Code (and probably most other editors) to make the "command-line" builds less... command-line.
Guess the problem with an "external" toolchain is it might stop working, as finding that instead of the VS one probably isn't supposed to work. Might mess up intellisense or something 🤷
There was a problem hiding this comment.
You're right- it finds the ARM GCC toolchain I installed. Makes sense!
This... sort-of... fix does the trick in both cases:
"environments": [ { "PATH": "${env.ProgramFiles(x86)}/Microsoft Visual Studio/2019/Community/Linux/gcc_arm/bin/;${env.PATH}" } ]It's ugly, and I'd feel a lot happier if I could find a way to get the full path to the currently running Visual Studio but there doesn't seem to be a way. Also not sure if I'm subtly breaking something by supplying the wrong executable, my install isn't exactly clean!
There was a problem hiding this comment.
In VS2022 it seems that the "IoT" configs are gone, so the only way to get this to work is to install the Arm toolchain and manually add a config similar to the one above. (Including the PATH hack...)
Anyway, I was in the area so I've rebased this.
docs/Windows-VisualStudio.md
Outdated
|
|
||
| Place these in the `vs\sdl\` folder. You will need to merge the include/lib directories. If you are using CMake/Open Folder, these are downloaded automatically. | ||
|
|
||
| Make sure you install "Desktop development with C++". If you plan to build for 33blit, you'll also need "Linux development with C++", making sure "C++ CMake tools for Linux" and "Embedded and IoT development tools" are selected in the "Optional" section. |
There was a problem hiding this comment.
Ah, the new improved 33blit 😄
There was a problem hiding this comment.
One more bit is nothing to sniff at! Though memory alignment of smaller types is quite complicated so you're encouraged to use uint33_t everywhere.
|
Guess this should mention somewhere that |
|
I never got as far as to get |
|
I think the changes other than the PATH thing still make sense. (I don't know if the bug got fixed, but it got closed as "lower priority" so I'm assuming it hasn't). I did just delete the entire "option 1" section though. Guess I have to make that "33blit" myself now. 😆 |
Daft-Freak
force-pushed
the
patch-windows-vs-docs
branch
from
d86af3b to
47154e5
Compare
No description provided.