关于C_INCLUDES must be under the source or output directories

最新推荐文章于 2023-06-26 16:18:42 发布

cigogo

最新推荐文章于 2023-06-26 16:18:42 发布

阅读量9.4k

点赞数 3

CC 4.0 BY-SA版权

分类专栏： android

本文链接：https://blog.youkuaiyun.com/cigogo/article/details/94546032

android 专栏收录该内容

18 篇文章

订阅专栏

本文详细解析了在从Android N项目迁移到O项目时遇到的编译警告问题，主要原因是配置文件中使用了未定义的变量或绝对路径，导致编译系统错误地解析路径。通过检查Android.mk文件，将LOCAL_C_INCLUDES中的$(VAR)/include更正为相对路径，并确保所有路径都是从源代码树顶部开始的相对路径，最终解决了这一警告。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

之前在Android N上的项目，正常编译，挪到O项目，就报这个异常，很是疑惑。

直接翻译过来，就是被include的目录，必须在源码或者输出的目录内。

Google一翻：

There are a couple of other things that can trigger this check -- I've seen both of these in practice:

1. Using $(VAR)/include in your LOCAL_C_INCLUDES, but when VAR isn't set. The build system then gets "/include", and before this check would attempt to look at the filesystem in that location. If that happened to be present on a machine, it could end up using that inappropriately.

即你配置的变量，在编译时并没定义，为空，所以变成错误的路径了。

2. Using an absolute path to a directory within the source path. This happens when someone overzealously uses $(abspath) or similar. Instead, make sure that all of your paths are relative paths from the top of the source tree. During a build, the working directory is always at the top of the source tree.

你使用了绝对路径，导致这个警告，你应该使用相对路径。

查了自己的Android.mk，发现一个定义正好是2的情况：

 LOCAL_PATH := $(call my-dir)
#TEST_PATH := $(shell pwd)/$(LOCAL_PATH) //原来配置的路径，为绝对路径
 TEST_PATH := $(LOCAL_PATH)/Other

修改之后，编译正常了。这边记录下，防止类似错误。。