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
Take the CMakefile and add that as part of the plugin.
The project name would be something like pyvxl
The volume model prefixes would be replaced with generic
compile would be in the plugin file
There would also need to be an internal plugin added too, for the internal just compile
The docker for compiling vxl in
The plugin would be responsible for the "build" volume
A way to export this for airgap (not fully deployed scenario)
Make sure easy to get compiled pyvxl for fully deployed scenario
Main project (manual?) steps would still include:
Added external/vxl, pyvxl, and pybind11 (can pybind11 be optional?)
Adding PYTHONPATH=${PYVXL_INSTALL_DIR_DOCKER}/lib/python3/site-packages to docker-compose.yml?
It might be possible to embed this in /usr/local/share/just/user_run_patch instead of docker-compose, but then that makes it more automatic and more hidden, trade-off
Unknown
How to pass install volume from plugin to project
I image using the volume:name: in docker-compose, we could come up with a pattern that would include project and user name, and manually add it to the project's docker-compose too.
The text was updated successfully, but these errors were encountered:
I think it should be possible to write a pyvxl plugin
We've added pyvxl to enough projects now, that it's becoming a common pattern that we are copying to get VXL added: https://bitbucket.org/visionsystemsinc/volume_model/branches/compare/main%0D0497eab354ec40f93be30c6100a7087d163e3070#diff
pyvxl
compile
would be in the plugin fileMain project (manual?) steps would still include:
PYTHONPATH=${PYVXL_INSTALL_DIR_DOCKER}/lib/python3/site-packages
todocker-compose.yml
?/usr/local/share/just/user_run_patch
instead of docker-compose, but then that makes it more automatic and more hidden, trade-offUnknown
volume:
name:
in docker-compose, we could come up with a pattern that would include project and user name, and manually add it to the project's docker-compose too.The text was updated successfully, but these errors were encountered: