Skip to content

Doc：修正设置环境入门文档中PKG_CONFIG_PATH

Xueyuan Lin请求将 lxy/gitlab:LXY1226-doc-env_setup合并到main-jh

What does this MR do?

修正在按照页面安装开发环境时，PKG_CONFIG_PATH为空时可能导致的出现PKG_CONFIG_PATH=$(brew --prefix)/opt/icu4c/lib/pkgconfig::$(brew --prefix)/opt/libffi/lib/pkgconfig，随后make gitaly时会出现Compilier因选项:-L$(brew --prefix)/opt/libffi/lib/找不到相应文件而不可用的异常。

Related issues

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the ~"docs-technical-debt" label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
由 Xueyuan Lin 编辑于

合并请求报告