-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore ways to transfer structured data between the apio process and the scons process #550
Comments
Here is a quick feasibility test with protocol buffer 2 in text mode. Scons params are serialized to a file and are read and parsed back. Zip file with the experiment files at the bottom of this message. Protocol buffer definition
Python test code
Generated serialized data
|
Here is a more complete draft of the Protocol Buffers definitions for for the scons params. Not tested or integrated yet.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The scons doesn't access data such as apio project, profile and resources data and recieves all of its data via a flat Dict[str, str]. This issue is for exploring a more structured way of transferring data from the apio process to the scons process.
Things to look for (not all are absolutely required):
One candidate that comes to mind is Protocol Buffers 2 with text serialization. The apio process can write it to a file in _build and the scons process can read it from there. Since the serialization used internally within a single apio invocation, there are no issues of backward compatibility.
The text was updated successfully, but these errors were encountered: