This PR mainly remove the references to the used template project, remove some configure and compilation warnings, and setup the packaging of this project.
It currently lacks proper entry points installations. The C++ binary is already in bin/, but the python main_*.pyscripts are currently installed in the sitelib. So they can be run with eg. $ python3 ~/install/lib/python3.6/site-packages/quadruped_reactive_walking/main_solo12_control.py -i test, but this is not really convenient.
I can suggest to either install them also in bin/ with a clear unique name (eg. $ qrw-solo12-control -i test) or let them in the sitelib, and merge them in a module (eg. $ python3 -m quadruped_reactive_walking solo12-control -i test) or put them into submodules (eg. $ python3 -m quadruped_reactive_walking.solo12_control -i test).
Any preference ?
Also, feel free to ask questions or modifications on this PR :)
Hello @thomasfla & @paLeziart,
This PR mainly remove the references to the used template project, remove some configure and compilation warnings, and setup the packaging of this project.
It currently lacks proper entry points installations. The C++ binary is already in
bin/, but the pythonmain_*.pyscripts are currently installed in the sitelib. So they can be run with eg.$ python3 ~/install/lib/python3.6/site-packages/quadruped_reactive_walking/main_solo12_control.py -i test, but this is not really convenient.I can suggest to either install them also in
bin/with a clear unique name (eg.$ qrw-solo12-control -i test) or let them in the sitelib, and merge them in a module (eg.$ python3 -m quadruped_reactive_walking solo12-control -i test) or put them into submodules (eg.$ python3 -m quadruped_reactive_walking.solo12_control -i test).Any preference ?
Also, feel free to ask questions or modifications on this PR :)