-
Notifications
You must be signed in to change notification settings - Fork 180
Cannot easily use Machinetalk in other projects #753
Comments
Btw. I have create a Qt pro und pri file to use in Qt projects some time ago: https://github.com/strahlex/QtQuickVcp/tree/master/3rdparty/machinetalk-protobuf-qt |
Ah! That works very nicely. Proper install rule and everything. Do you suggest other applications to use this same library to link to machinetalk-protobuf or should they build the protobuf files into their own library/code? |
close this issue here since duplicated in machinetalk-protobuf repo |
At the moment using Machinetalk in other projects is not a smooth process. Machinetalk-protobuf needs to be cloned (using git clone or git subtree) and the .proto files need to be compiled into .h, .c, .py, .js files. After that user-projects need to copy those files, reference the machinetalk-protobuf directory or use git subtree and integrate the Makefile into their build process.
This is a general problem that (I think) needs to be solved per language/framework.
For Python projects it's standard to have a package in pypi, so that people can install it using
pip install machinetalk-protobuf
or reference machinetalk-protobuf in their setup.py. This is covered in issue machinekit/machinetalk-protobuf#26For NodeJS projects it's standard to have a package in npmjs, so that people can install it using
npm install machinetalk-protobuf
or reference the machinetalk-protobuf in their setup.py. This is covered in issue machinekit/machinetalk-protobuf#25For C/C++ projects it's standard to have include files and libraries available through pkg-config, installable through
make install
. Additionally it is helpful if the .proto files are installed in a standard location, also using make install. This is covered in issue machinekit/machinetalk-protobuf#24The text was updated successfully, but these errors were encountered: