-
Notifications
You must be signed in to change notification settings - Fork 27
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
add developer documentation about environment setup #51
Conversation
18eddb6
to
687dd40
Compare
687dd40
to
7af88c6
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.
Just a handful of little things
Co-Authored-By: Marya Belanger <[email protected]>
@maryaB-osr Thanks for the improvements! I just removed two extra spaces in 4753935. |
developer/environment.rst
Outdated
|
||
Therefore both parts are implemented in a Python script located in the root of the install prefix: ``_local_setup_util_<ext>.py``. | ||
While the Python script itself can't change the environment it is able to efficiently interpret the operations described by the ``.dsv`` files and generate the shell specific commands necessary to update the environment. | ||
The Python file is templated with information specific to the primary shell it used from hence the ``<ext>`` in the filename. |
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.
Rationale for templating out multiple instances of the script rather than just passing arguments to one?
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.
The templated approach was just easier to implement. The script logic only needs to take one set of formatting strings into account.
Based on questions in colcon/colcon-core#262.