My point was more like "it works just fine with cargo for me, so deviating too much from that likely causes more problems"
-
-
Define 'It works just fine with cargo for me' - what are you build commands with cargo? what does your basic cargo file look like?
1 reply 0 retweets 0 likes -
just "cargo new --bin hello-world" and then "cargo build" in there (with msvc toolchain). And then just the config here in the launch.json and that's it.
1 reply 0 retweets 0 likes -
So, interesting. hand-crafting the project fails to allow for debugging. Using Cargo to generate the project ... works. Why?pic.twitter.com/V8rwY9uAGA
1 reply 0 retweets 1 like -
If you use rustc manually, how do you call it? Cause there's flags you need to pass.
1 reply 0 retweets 1 like -
pretty straightforward: `rustc .\hello_world.rs`
1 reply 0 retweets 1 like -
Yeah I think you may need to pass -C debuginfo=1 then
1 reply 0 retweets 2 likes -
That appears to be it. Still a bit confused as to why cargo, by default, would build a debug version of the executable ...
1 reply 0 retweets 0 likes -
Because cargo is catered towards actual users, so it has preconfigured debug, release, bench and test profiles while rustc itself is like gcc and requires you to specify all the different options yourself.
1 reply 0 retweets 2 likes -
So, not done by a long-shot, but that's better. Now to see if Visual Studio Community fares any better. I do see a new tutorial set coming up soon.
1 reply 0 retweets 1 like
Glad we got it sorted!
-
-
Now I'm on to the next hill, visual studio community
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.