|
From: | Paul Eggert |
Subject: | Re: Merging feature/android |
Date: | Sat, 4 Mar 2023 01:13:47 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 |
On 2023-03-04 00:08, Po Lu wrote:
If gnulib provided a list of its C files, we could arrange for autoconf to symlink the files in lib/ to cross/lib/ during configuration. But I could not find any such list.
m4/gnulib-comp.m4 has gl_FILE_LIST. Although this lists all files not just C files, it should be easy enough to extract the C files.
the C compiler doesn't understand GNU make vpath directives, so the includes in lib/ are: -I$(srcdir) -I. while the includes in cross/src/lib are: -I$(top_srcdir)/lib -I$(srcdir) -I. and as a result, when a file in -I$(top_srcdir)/lib then includes: #include "stdio.h" it gets the stdio.h in lib, and not cross/lib, leading to silent problems later on.
I'm not quite following, since I'm not sure whether we're talking about an in-tree build or an out-of-tree build. That being said, can we address the problem by changing the order of the includes in cross/src/lib/Makefile?
[Prev in Thread] | Current Thread | [Next in Thread] |