Johannes, I am using a QNX build system. It currently, or at least how I have it setup, does not separate object files into separate folders. Everything goes into one folder. The only separate object folders are for chip architecture, armle-v7, aarch64, x86, and x86-64. I was thinking of renaming the config files in ../src/utils/ to something link util_config.c and util_config.h and the updating the files that include the original ./util/config.h to pickup the renamed one. There are very few files that use the ./src/util version. Duplicate file names in different locations are a problem for our builds. Thanks, Jim -----Original Message----- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx> Sent: July 16, 2021 10:40 AM To: Jim Crites <jcrites@xxxxxxxxxxxxxx>; hostap@xxxxxxxxxxxxxxxxxxx Cc: Hanqi Yang <hanyang@xxxxxxxxxxxxxx> Subject: Re: wpa-2.10 pair of files with same names in 2 different locations causing build problems On Fri, 2021-07-16 at 14:14 +0000, Jim Crites wrote: > Hello, > > I build wpa-2.10 for QNX OS. > I am updating my working version of 2.10 (hostap- > cc6153a8a4555407562a4200f298554e6a27eea1) to hostap- > 311091eb43eb8a5210745b667de7146012abff02. In the newer version there > are 2 sets of config.c and config.h files. One pair in > ../wpa_supplicant/ and one pair in ../src/utils/. The files are not > identical. In the my previous version the files only existed in > ../wpa_supplicant/. This is causing build problems as building both > will cause the last one built object file to overwrite the first one > built. > > Why are there 2 sets of config.x files ? > How does this not affect the builds ? What kind of build system do you have? The current upstream build system separates the object files into separate build directories etc. ... johannes ---------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
