Here’s a Minimal, Reproducible Example that exhibits the same problem that you experienced. I created a C library exporting a simple addition function. I also created a Cargo project to use this function. dynlink/ ├── executable │ ├── build.rs │ ├── Cargo.lock │ ├── Cargo.toml │ └── src │ └── main.rs └── library ├── … Read more
Answering my own question because I just earned a Tumbleweed badge for it… and I found out subsequently But I was wondering whether there is perhaps a finer-grained control over this, like overwriting -Bsymbolic for individual function definitions of a library. Yes, there is the option –dynamic-list which does exactly that Should I be aware … Read more
This is the interface to the dynamic loader, which provides a client program with ability to do things such as explicitly load other libraries, lookup symbols within, etc. Most programs do not need to do such things explicitly, since the linker does what is needed to enable ordinary usage of shared libraries while loading the … Read more
This is a warning, not an error. You can still use TensorFlow. The shared libraries libnvinfer and libnvinfer_plugin are optional and required only if you are using nvidia’s TensorRT capabilities. To suppress this and all other warnings, set the environment variable TF_CPP_MIN_LOG_LEVEL=”2″. TensorFlow’s installation instructions list the GPU dependencies (current as of December 13 2022): … Read more
Based on all the responses, the post on raywenderlich.com and the gist created by Chris Conway I came up with this. Executing the following steps I was able to build a Cocoa Touch framework (including Swift and Objective-C files) that contains all architectures for both simulator and device: Create a new (Aggregate) target in your … Read more
I did some investigation and although I could not find a satisfying solution to the problem, I did find a half-solution. The problem of static builds boils down to 3 things: Building and linking the project’s internal libraries. Pretty simple, one just has to flip the BUILD_SHARED_LIBS switch OFF. Finding static versions of external libraries. … Read more
For some time I was thinking that this is my problem as well, but for normal apps (non-iOS-8-extension) you just need to change one build setting in your casual Xcode 6 iOS Universal Framework target (set Mach-O Type to Static Library): There should be no problem with iTunes Connect and iOS 7 after that 🙂
Link binary with libraries Link frameworks and libraries with your project’s object files to produce a binary file. You can link a target’s source files against libraries in the target’s active SDK or against external libraries. Embed Frameworks You can create an embedded framework to share code between your app extension and its containing app. … Read more
As already stated by @przemyslaw-jablonski, this is similar to what was in XCode 10, but in only one screen (which I personally like!). Embedding Do not embed static frameworks and libraries (linking happens at build time), only shared ones (dynamic linking happens at run time, so they need to be in your bundle). file frameworkToLink.framework/frameworkToLink … Read more
Before iOS8, Xcode only allowed the option of creating static libraries for iOS. The common problem with that was we had to ship the binary and headers separately. Later, some developers came with the idea of creating ‘static frameworks’. [the .framework is just a folder with symbolic links to the lib and the headers]. One … Read more