SDK • Pico Extension and Debug compilation

The Pico Extension seems pretty well thought out to me. Although the documentation had some serious gaps, I was able to get it up and running and with the use of a Pi Debug Probe able to compile and debug a simple app.

The problem is that the code generated seems to be optimized rather than a debug compilation. The CMakeCache.txt file seems to indicate it is a Release build.

After looking at the available documentation, it seems there are a couple of ways to generate a Debug build, but I wasn't exactly sure.

Should I just change the CMakeCache.txt file to indicate a Debug build? I am not sure this is the proper way to do this.

It seemed that the application should have a simple switch, toggle, or something in the UI that would let you flip between a Release and Debug build. (Like Visual Studio, for example...) So, did I miss something or is this something that is intended to be manually edited?

It seems that if the application has enough sense to know to create an .elf file for the probe to deliver to the target device, it would have enough sense to (by default at least) create a debug version of the code.
Pls give me a clue.

Statistics: Posted by tcroswell — Fri Nov 08, 2024 10:00 pm — Replies 0 — Views 11

---