-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document interactive development of mavproxy #6371
base: master
Are you sure you want to change the base?
Conversation
70afbea
to
b94bc77
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't a user ordinarily be in the ArduPilot venv here? It seems you're creating a new venv as part of these instructions...
b94bc77
to
7667f70
Compare
* Use a venv and develop mode from setup.py Signed-off-by: Ryan Friedman <[email protected]>
7667f70
to
589f38a
Compare
These instructions are for an isolated env. If the instructions are making an assumption you use the ardupilot rep's venv, then maybe it's worth adding that as a prerequisite. I've found it's not required to share the same environment for both repos. Also, I saw that MAVProxy would be installed twice. |
How are we supposed to install the wsproto dependency of pymavlink?
|
@peterbarker Can you explain why the ardupilot virtual environment is necessary? The docs don't seem to agree. Here's why: The ardupilot setup is explained as the setup for building the Ardupilot code with waf: Which prompts you on adding the venv to your bashrc: If you just start with MAVProxy, which does not even reference the Ardupilot environment install Then, why would a developer know that the have to install MAVProxy INSIDE of the ardupilot repo's virtual environment? If this is actually true, then shouldn't it be documented that this is the only supported workflow ? |
Purpose
Use a venv and develop mode from setup.py
Relates to BUG: Mavproxy from Pip is missing dependencies causing Import Errors. MAVProxy#1215 (comment)
Depends on Use pip to install mavproxy #6372
Existing Workflow
New Workflow
Now, when you change code, it updates when you just kill mavproxy and run it again.