speed up FS upload targets

[Jason2866]

by disabling the not needed LDF in this targets

Checklist:

• The pull request is done against the latest develop branch
• Only relevant files were touched
• Only one feature/fix was added per PR, more changes are allowed when changing boards.json
• I accept the CLA

Summary by CodeRabbit

• New Features

  • Added automatic disabling of Library Dependency Finder (LDF) for filesystem-related build targets to improve build environment handling.

• Refactor

  • Simplified the logic for setting up Python paths by removing fallback attempts for site-packages directories.

[coderabbitai]

Walkthrough

The update modifies the Python path setup logic by removing fallback handling for site-packages discovery, relying solely on subprocess output. Additionally, a new function is introduced to disable the Library Dependency Finder (LDF) in the project configuration when certain filesystem-related build targets are detected.

Changes

File(s)	Change Summary
builder/main.py	Removed fallback logic in setup_python_paths; added switch_off_ldf() to disable LDF for specific targets.

Poem

In the warren, code paths shift and bend,
Old fallbacks gone, on subprocess we depend.
For filesystems now, LDF rests—
The builder bunny knows what’s best!
🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Jason2866]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9d95374 and 3aebc59.

📒 Files selected for processing (1)

• builder/main.py (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: build (macos-15, examples/espidf-peripherals-uart)
• GitHub Check: build (macos-15, examples/espidf-arduino-matter-light)
• GitHub Check: build (macos-15, examples/espidf-arduino-littlefs)
• GitHub Check: build (macos-15, examples/espidf-arduino-blink)
• GitHub Check: build (windows-latest, examples/espidf-blink)
• GitHub Check: build (windows-latest, examples/arduino-wifiscan)
• GitHub Check: build (windows-latest, examples/arduino-blink)

🔇 Additional comments (2)

builder/main.py (2)

648-662: LGTM! Well-implemented optimization for filesystem targets.

The function correctly identifies filesystem-related targets and disables LDF to improve build performance. The implementation properly handles project configuration sections and aligns perfectly with the PR objective of speeding up FS upload targets.

---

807-809: Appropriate placement for LDF optimization.

The function call is correctly positioned after framework-specific configuration loading, ensuring that LDF is disabled unconditionally for the identified targets.