You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2018. It is now read-only.
We need to include "model" mc.proto and other template files inside created PROIO files.
Therefore, I would suggested to copy the directory "model" to the installation location. Then one can link such files using the path $PROIO/model/mc.proto (as an example) during file creation of files.
There should be also a mechanism to store such files (and log files) inside PROIO
best, Sergei
The text was updated successfully, but these errors were encountered:
decibelcooper
changed the title
suggestions
Suggestions for including proto files in installation
Jun 27, 2018
Hi Sergei (@chekanov), thanks! My thought is that File Descriptor protos are included in generated code, so in a sense these files are already being installed. There is also significant overlap here with #20. If we satisfy #20 and add the ability to dynamically deserialize unknown messages using the stored File Descriptor protos, does this satisfy your requirements?
We need to include "model" mc.proto and other template files inside created PROIO files.
Therefore, I would suggested to copy the directory "model" to the installation location. Then one can link such files using the path $PROIO/model/mc.proto (as an example) during file creation of files.
There should be also a mechanism to store such files (and log files) inside PROIO
best, Sergei
The text was updated successfully, but these errors were encountered: