Skip to content

Conversation

pbergeron-adsk
Copy link
Contributor

@pbergeron-adsk pbergeron-adsk commented Sep 17, 2025

Linked issues

There's no SG-XXXXX ticket for this; I guess I should create one.

Summarize your change.

Because I often need to switch to/from release/debug builds, and I never really knowing which environment I'm in at my command prompt. (multiple shells), and doing "cd" to the correct app folder where the rv binary is located, I decided to update rvcmds.sh to provide more information at the unix prompt and added aliases to "cd" to the appropriate build folder where the rv binary is located.

Later, I'd like to kinda get rid of all of the "d" aliases (eg: rvbuildd -> rvbuild), and depending on the current config / build type (rebug or release) the alias just does the right thing in the right folders. But, that's for a later time.

Describe the reason for the change.

Well, this is a fix for a pet-peeve of mine that has been bothering me since I started working on RV. It was like a little itch too small to do anything about it, but that constantly itches. Well, I fixed the itch.

Describe what you have tested and on which operating system.

macOS. I'd like Cedrik to test this on Windows and Linux.

Add a list of changes, and note any that might need special attention during the review.

  • It's now possible to know which of "rvcfg" or "rvcfgd" we last did, based on an exported env var.
  • The (.venv) prompt was replaced with (.venv|rel) or (.venv|dbg) depending on the current config.
  • added aliases "rvappdir" and "rvappdird" to do a quick "cd" to the appropriate bin dir.

Also added a call to deactivate (exit) the venv if we switch config. Apparently not exiting the venv just stacks venvs on top of each other whenever we change config type.

If possible, provide screenshots.

rvcfgd:
image

rvcfg:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant