Re: Undefined symbols for architecture arm64
Walter McCreary
Thanks, Alex.
toggle quoted messageShow quoted text
My architectures build settings do match yours. This is an old project, originating in 2009. There are 7 targets, and this behavior is common to at least 2 of them. At least one of them (the newest, from 2014) is okay. So, I’m assuming that the project build settings aren’t problematic. Since my last email, I tried building the target in question after updating the .LinkFileList by hand, to include the new classes that the linker could not find previously. This worked, and the build for arm64 succeeded (though it did not touch or update the .LinkFileList). I also tried a build without a .LinkFileList, to see if that would force its generation, but this failed, with the linker complaining that it couldn’t find the file. So, I’m guessing that the compiler must be responsible for generating that list for the linker. Do you know if that’s the case? Anyway, I decided to just mv the project’s build directory out of the way, to force rebuilding the whole tree. This has tested ok for one of the targets in question - I have not yet tested any of the others. -Walter
On Jul 19, 2019, at 21:30, Alex Zavatone via Groups.Io <zav=mac.com@groups.io> wrote:
|
|