Skip to content

Conversation

@taep96
Copy link

@taep96 taep96 commented Mar 19, 2025

Thank you for your contribution!

We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:

Submission Checklist 📝

  • I have updated existing examples or added new ones (if applicable).
  • I have used cargo fmt command to ensure that all changed code is formatted correctly.
  • I have used cargo clippy command to ensure that all changed code passes latest Clippy nightly lints.
  • My changes were added to the CHANGELOG.md in the proper section.

Pull Request Details 📖

Description

esp-rs/espup#476

Testing

Describe how you tested your changes.

std::env::home_dir().map(|home| home.join(".espup").join("esp-clang"));
let espup_clang_path = std::env::home_dir().map(|home| {
const ESPUP_CLANG_SUFFIX: &str = "espup/esp-clang";
let local_share_path = home.join(".local").join("share").join(ESPUP_CLANG_SUFFIX);
Copy link
Collaborator

Choose a reason for hiding this comment

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

While local share is the "default xdg data home" its not really a "xdg support" per se, For that we would have to respect the respective xdg env var itself.

I would not be opposed to use it if its set by the user. But crucially the change should work not only for linux people, but should not change the default for windows and mac users.

Site note: keep in mind that this particular case where we are "using the espup" provided esp-clang version we are in a separate file path looking. There is a certain risk to merge the espclang path into a directory where users might have other clang versions installed and may then provide wrong versions. E.g the user provided install overrides the espup install. By having the default in a separate folder its less risk.

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