Help with Combining Examples on Pitaya-Go Board

[4cplayz]

Help with Combining Examples on Pitaya-Go Board

Project Background
I've recently acquired a Pitaya-Go development board for my end-of-year school project. I'm working on a dynamic NFC emulator that uses a website server API to dynamically change NFC links according to API requests. I selected the Pitaya-Go board because of its integrated features that align perfectly with my project requirements.

The Issue
I've been testing several example codes to better understand the SDK and toolchain used for development. However, I'm experiencing significant difficulty when trying to combine certain examples together.
For instance, when attempting to combine the "button" example with the "nfc/record_url" example, I consistently encounter compilation errors stating "No such file or directory." After researching possible solutions, I discovered that both the Makefile and the sdk_config.h files need to be edited to add the missing file paths.

What I'm Looking For
I'm wondering if there's a more efficient way to handle this issue:

• Is there a way to automatically generate the necessary file paths?
• Are there specific terminal commands I might have missed that would update these files?
• What's the recommended approach for combining examples in this SDK?

The current process is extremely tedious - adding one line of code, building the project, encountering a new missing path error, adding that path, and repeating until eventually nothing works properly.

Any guidance on a better methodology would be greatly appreciated ;)

[caizelin]

@4cplayz
To help diagnose the compilation issues you're facing when combining examples, it would be extremely useful if you could share:

• The exact error logs (full output from the build process).
• Relevant code snippets (or the entire project if possible), especially where the NFC and button functionalities interact.
• Your current Makefile and sdk_config.h, as misconfigurations there are often the culprit.

With these details, we can more efficiently identify the root cause—whether it’s missing paths, conflicting dependencies, or SDK configuration issues. Let us know how we can assist further!