Posted by AntoineP
Feb 21, 2025/18:10 UTC
The email delves into the complexities of managing shared code and configuration in a project setup that involves integrating a wallet as a subtree to a node, and similarly, integrating a GUI with the wallet. It highlights the challenge of deciding how to handle common code sections. Specifically, it points out that while some parts of the code, such as src/crypto
, could be relatively easily split between the projects, other areas like src/util
and src/common
present a more significant challenge. These might either need to be duplicated across projects or require the establishment of another interface to facilitate their integration.
Furthermore, the message touches upon the concerns related to copying configurations, particularly for Continuous Integration (CI) processes, but suggests that these are less worrisome compared to the broader issue of organizing the build system. This latter point is identified as a critical area needing attention, indicating the sender's uncertainty about how best to approach the structuring of the build environment to support this integrated project setup. A call for input is made to @fanquake, seeking expertise or advice on organizing the build system effectively, underscoring the importance of collaborative problem-solving in addressing complex technical challenges within the project.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback