Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 5044

SDK • Re: Elegant ways of documenting changes in SDK for publishing project

$
0
0
The way I have done it is to pull the SDK into a local sub-directory and hack that. You don't necessarily need everything but the SDK isn't set-up to easily allow 'most of the default but use files I have provided', or I missed a trick.

But that's a PITA and I have sometimes patched actual SDK files to include '#ifdef' to remove original code and insert or '#include' my own using definition names the Pico SDK nor users are ever going to use. That makes it 'as was' for everyone and everything but my code. I can live with that as light-touch vandalism.

There's no easy solution. I have long been an advocate of SDK having entirely weak functions so it's easy to replace any function with your own.

Statistics: Posted by hippy — Mon Apr 01, 2024 8:14 pm



Viewing all articles
Browse latest Browse all 5044

Trending Articles