Skip to content

[Tools] Add documents for tools script; Add NG for tools #10572

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

BernardXiong
Copy link
Member

拉取/合并请求描述:(PR description)

[

为什么提交这份PR (why to submit this PR)

跟进Tools Scripts的重构

你的解决方案是什么 (what is your solution)

使用AI工具辅助编写,同时兼容原有脚本,原有方式,确保兼容性。

请提供验证的bsp和config (provide the config and bsp)

  • BSP: N/A
  • .config: N/A
  • action:

]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

  • 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
  • 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality:

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

  • 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
  • 代码风格正确,包括缩进空格,命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
  • 没有垃圾代码,代码尽量精简,不包含#if 0代码,不包含已经被注释了的代码 All redundant code is removed and cleaned up
  • 所有变更均有原因及合理的,并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
  • 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
  • 代码是高质量的 Code in this PR is of high quality
  • 已经使用formatting 等源码格式化工具确保格式符合RT-Thread代码规范 This PR complies with RT-Thread code specification
  • 如果是新增bsp, 已经添加ci检查到.github/workflows/bsp_buildings.yml 详细请参考链接BSP自查

@github-actions github-actions bot added the tools label Aug 1, 2025
@Rbb666 Rbb666 requested a review from Copilot August 5, 2025 10:59
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds comprehensive documentation for the RT-Thread tools scripts and introduces a Next Generation (NG) object-oriented architecture for the build system. The changes provide enhanced maintainability and extensibility while preserving backward compatibility.

Key Changes:

  • Adds extensive documentation covering build system usage, technical principles, and SConscript writing guidelines
  • Introduces a new NG module with object-oriented design patterns for better code organization
  • Updates the package.json format and BuildPackage function to support the new rt-thread-component type with enhanced dependency management

Reviewed Changes

Copilot reviewed 21 out of 25 changed files in this pull request and generated 4 comments.

:

File Description
tools/package.py Enhanced BuildPackage function with improved error handling and support for new package.json format
tools/ng/* New object-oriented build system architecture with comprehensive modular design
tools/hello/* Example component with updated package.json format demonstration
tools/docs/* Comprehensive documentation covering usage guides, technical principles, and best practices
Comments suppressed due to low confidence (1)

tools/package.py:115

  • The variable name 'item' is ambiguous in this context where it represents a file path. Consider renaming it to 'file_pattern' or 'file_path' for better clarity.
                    for item in files:

package = json.loads(package_json)

# check package name
if 'name' not in package or 'type' not in package or package['type'] != 'rt-thread-component':
Copy link
Preview

Copilot AI Aug 5, 2025

Choose a reason for hiding this comment

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

Consider using constants for the package type string to avoid magic strings and make the code more maintainable. Define RT_THREAD_COMPONENT_TYPE = 'rt-thread-component' at the module level.

Suggested change
if 'name' not in package or 'type' not in package or package['type'] != 'rt-thread-component':
if 'name' not in package or 'type' not in package or package['type'] != RT_THREAD_COMPONENT_TYPE:

Copilot uses AI. Check for mistakes.

path = os.path.normpath(path)

# Convert to forward slashes for consistency
if platform.system() == 'Windows':
Copy link
Preview

Copilot AI Aug 5, 2025

Choose a reason for hiding this comment

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

The platform.system() call is repeated multiple times in this class. Consider caching the result in init or using the existing PlatformInfo.is_windows() method to avoid redundant system calls.

Suggested change
if platform.system() == 'Windows':
if self._platform_system == 'Windows':

Copilot uses AI. Check for mistakes.

# Try integer
try:
return (int(value, 0), ConfigType.INTEGER) # Support hex/octal
except ValueError:
Copy link
Preview

Copilot AI Aug 5, 2025

Choose a reason for hiding this comment

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

The try-except block catches ValueError but doesn't provide specific error information about malformed integer values. Consider logging the original value that failed to parse for better debugging.

Suggested change
except ValueError:
except ValueError:
logging.warning(f"Failed to parse integer value: '{value}'")

Copilot uses AI. Check for mistakes.

Comment on lines +76 to +77
"""Detect GCC toolchain."""
gcc_path = shutil.which(self.prefix + "gcc")
Copy link
Preview

Copilot AI Aug 5, 2025

Choose a reason for hiding this comment

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

[nitpick] The hardcoded 'gcc' suffix makes this code less flexible. Consider making the compiler executable name configurable or using a constant to make it easier to maintain.

Suggested change
"""Detect GCC toolchain."""
gcc_path = shutil.which(self.prefix + "gcc")
gcc_path = shutil.which(self.prefix + self.GCC_SUFFIX)

Copilot uses AI. Check for mistakes.

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

Successfully merging this pull request may close these issues.

1 participant