您可以将某个依赖项指定为包含某个包的任何本地文件夹或 tarball 文件。此功能对本地脱机开发和测试很有帮助。
注意:如果要将本地文件系统上的包作为 Git 依赖项引用,请改用 file://<url>
格式。Unity 不支持使用文件路径直接引用本地可访问的 Git 代码仓库。有关 file://<url>
格式的更多信息,请参阅 Git 依赖项。
本节介绍如何使用项目清单来设置本地依赖项。如果想改用 Package Manager 窗口,请按照以下页面上的说明进行操作:
路径引用始终以 file:
前缀开头,并且使用正斜杠 (/
) 作为路径分隔符。
注意:在 Windows 上,也可以使用反斜杠 (\
),但前提是将每个反斜杠转义(例如 "file:..\\github\\my_package_folder"
或 "file:C:\\Users\\my_username\\github\\my_package_folder"
)。这些路径不像正斜杠那样容易阅读,很容易出现输入错误,而且除了在 Windows 计算机上之外,不能在其他地方使用它们。由于这些原因,最好使用正斜杠。
您可以使用绝对路径,也可以使用相对于项目的 Packages
文件夹(即项目清单的根文件夹)的路径。换句话说,以两个点 (..
) 开头的路径是指项目路径的根目录,如 ../another_folder
是 Packages
文件夹的同级文件夹。
提示:当追踪同一代码仓库中的项目和包时,带正斜杠的相对路径可跨不同计算机和操作系统提供更好的可移植性。
对于 Windows 绝对路径,file:
前缀后面是驱动器盘符和冒号(通常为 C:
),除此之外,其他部分与 Linux 或 macOS 路径相同。
在 file:
前缀后,路径是标准相对路径:
{
"dependencies": {
"my_package_a": "file:../github/my_package_folder",
"my_package_b": "file:../Downloads/my_package_tarball.tgz"
}
}
在 file:
前缀之后,路径是标准 POSIX 路径,以正斜杠 /
开头:
{
"dependencies": {
"my_package_a": "file:/Users/my_username/github/my_package_folder",
"my_package_b": "file:/Users/my_username/Downloads/my_package_tarball.tgz"
}
}
请注意,驱动器盘符紧跟在 file:
前缀之后:
{
"dependencies": {
"my_package_a": "file:C:/Users/my_username/github/my_package_folder",
"my_package_b": "file:C:/Users/my_username/Downloads/my_package_tarball.tgz"
}
}
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.