Skip to content
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 mentioning k4_local_repo #87

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

m-fila
Copy link
Contributor

@m-fila m-fila commented Jan 15, 2025

BEGINRELEASENOTES

  • Update single package development docs to include k4_local_repo

ENDRELEASENOTES

Updating the single package development docs to recommend the usage of k4_local_repo

Copy link
Contributor

@tmadlener tmadlener left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea. Thanks. The limitations sound rather horrifying at the moment ;) We could think about adding a sentence, that mentions that all the manual steps can also be put into a script, but I don't know if that doesn't encourage the proliferation of some truly horrible scripts...

`k4_local_repo` is a helper command to simplify setting up the environment for single package development. This command becomes available immediately after sourcing the environment. To use it, navigate to the root directory of the package you want to develop and execute the command:

```bash
k4_local_repo <install_location>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
k4_local_repo <install_location>
k4_local_repo [<install_location>]

To indicate it's optional and defaults to install?

export PYTHONPATH=<install_location>/python:$PYTHONPATH
```

where `<install_location>` should match the install location specified during cmake configuration with `-DCMAKE_INSTALL_PREFIX=<install_location>`. It's possible some packages may required specifying some extra environmental variables beside these.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
where `<install_location>` should match the install location specified during cmake configuration with `-DCMAKE_INSTALL_PREFIX=<install_location>`. It's possible some packages may required specifying some extra environmental variables beside these.
where `<install_location>` should match the install location specified during cmake configuration with `-DCMAKE_INSTALL_PREFIX=<install_location>`. It's possible some packages may require specifying some extra environmental variables beside these.

Should we also mention MARLIN_DLL here? It's also done automatically in some cases by k4_local_repo.

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.

2 participants