Closed aaronchongth closed 1 year ago
There is https://github.com/open-rmf/rmf_api_msgs too, I can update the readme there too.
for rmf-web
, I think we are installing into the virtual environment and not system so it shouldn't matter right?
There is https://github.com/open-rmf/rmf_api_msgs too, I can update the readme there too.
for
rmf-web
, I think we are installing into the virtual environment and not system so it shouldn't matter right?
It half matters because rmf-web
uses a venv that shares the system packages, the venv packages should have priority but in rare cases there may be problems with the transitive dependencies (actually this also applies to fastapi, uvicorn etc). I don't see any solutions though so this might be the best workaround.
After we merge this, what else do we need to do to make the build farm also use these instructions?
Right now the buildfarm doesn't care, it is actually optional https://github.com/open-rmf/rmf_api_msgs/blob/main/rmf_api_msgs/CMakeLists.txt#L95, to allow folks to use models in python (ok this is rather important still if someone wants to use binaries and python to interact with rmf-web
) But right now, nothing needs to be done.
We'll need to start the conversation again, regarding migrating away from pip for anything rmf related.
Bug fix
Fixed bug
Fixes https://github.com/open-rmf/rmf/issues/372.
Fix applied
datamodel_code_generator
from installation step as it is not released by binaries, and only emits a warning even when buildingrmf_api_msgs
from source, not crashing the build, as per https://github.com/open-rmf/rmf/issues/249datamodel_code_generator
will only be used if a user is trying to create their ownapi-server
via the schemas fromrmf_api_msgs
, otherwise it is not used at alldatamodel_code_generator
will only be inrmf_api_msgs
Verify warning instead of crash
Using
podman
,