basher
05/20/2019, 11:24 PMbasher
05/20/2019, 11:25 PMKris Wong
05/21/2019, 12:10 AMKris Wong
05/21/2019, 12:10 AMbasher
05/21/2019, 12:25 AM-framework <lib>
and -F<path>
to the binary linker opts. Problem is that when I inspect the framework with otool -L, there’s no command added to dynamically link the framework. On top of that, I end up with all of the symbols from that framework in my main framework’s symbol table (causes lookup issues when launch the app)Kris Wong
05/21/2019, 12:37 AMbasher
05/21/2019, 1:32 AMolonho
05/21/2019, 5:48 AMsvyatoslav.scherbina
05/21/2019, 6:41 AMribesg
05/21/2019, 8:40 AMbasher
05/21/2019, 12:59 PMbasher
05/21/2019, 1:05 PMKris Wong
05/21/2019, 1:21 PMKris Wong
05/21/2019, 1:22 PMsvyatoslav.scherbina
05/21/2019, 2:07 PMthere’s no command added to dynamically link the framework.
On top of that, I end up with all of the symbols from that framework in my main framework’s symbol table (causes lookup issues when launch the app)Could you clarify? It’s not clear how both can happen at the same time. What do you mean by “lookup issues”?
basher
05/21/2019, 2:38 PMbasher
05/21/2019, 2:39 PMsees it in the K/N framework’s symbol table and errors with a read failure (that symbol isn’t used by the framework, and the framework has no command to load the SQLite framework)This part is a bit speculative, but the error trace strongly suggests this is what’s happening (read error is accurate)
Kris Wong
05/21/2019, 3:55 PMbasher
05/21/2019, 3:58 PMsqlite3_collation_needed
) that the MPP framework does not use (read failure at 0x0)
binaries {
framework {
embedBitcode = 'DISABLE'
linkerOpts = ["-framework sqlite3", "-F$buildDir"]
}
}
Kris Wong
05/21/2019, 4:04 PMbasher
05/21/2019, 4:04 PMKris Wong
05/21/2019, 4:04 PMbasher
05/21/2019, 8:54 PM@executable_path