static-libraries

问题 We are going to use Omniture-Tracking for iOS, which is part of AdobeMobileLibrary. AdobeAdobeMobileLibrary is not available via cocoapods-repo (only an older version of Omniture), but as a static-library, that you can download from the Adobe Website. I wonder if it is possible to maintain this static-library with cocoapods? I've created a podspec-file: Pod::Spec.new do |s| s.name = 'AdobeMobileLibrary' s.version = '4.0.2' s.license = 'Commercial' s.summary = 'Adobe Omniture SiteCatalyst

问题 I never put much thought into the size difference between a static library and a dynamic library until I downloaded pre-built libraries of boost today. I found that the static libraries of boost are much much bigger than the dynamic libraries. For example, the debug multi-threaded boost wave static library is 97.7 mb in size while the same library, but dynamic, is only 1.4 mb in size (including import library and dll)! That is a huge difference. Why is that? Second question, if I statically

问题 I have my project currently compiling under gcc. It uses Boost, ZeroMQ as static .a libraries and some .so libraries like SDL. I want to go clang all the way but not right now. I wonder if it is possible to compile code that uses .a and .so libraries that were compiled under gcc with clang? 回答1: Yes, you usually can use clang with GCC compiled libraries (and vice versa, use gcc with CLANG compiled libraries), because in fact it is not compilation but linking which is relevant. You might be

问题 A is a module project. There are some test targets and the relevant reusable code is compiled in a separate (static library) target. A uses the third party Lumberjack logging library. The Lumberjack code was simply dropped into the project. B is a different module project, but otherwise it has the same properties as A . C is the main project. It depends on A and B . It links the libraries of A and B . Compiling C will result in duplicate Lumberjack symbols. How can I have multiple separate

问题 I have compiled libclang.a for i386 and armv7. I'm able to build my ios app with i386 libclang.so but it can't be started because of ".dylib not found" error. Then i decided to create fat lib using lipo: lipo -create ../i386/libclang.a ../armv7/libclang.a -output ../fat/libclang.a and added fat library instead of i386. Now i'm getting multiple build errors: Undefined symbols for architecture i386: "llvm::TimeRecord::getCurrentTime(bool)", referenced from: clang::cxindex::Logger::~Logger() in

问题 I'm trying to share code between multiple Xcode projects. I've followed Apple's notes on creating a static library subproject within a project: http://developer.apple.com/library/ios/technotes/iOSStaticLibraries/iOSStaticLibraries.pdf This works great! However, when I follow the same instructions using my own project, I find that the header files I make public in the static library can not be found by code within my app. This is because my project uses custom build configurations. I have one

问题 I have a .a file for a library I'm linking to an iOS application. How do I know the version number of the library? I don't need to do this programmatically, I just need to get it manually once. 回答1: There is no common theme on how to encode a version number into a static library. Sometimes there is none present at all. Sometimes that is done using a header that belongs to that library. Sometimes it is done using a function that returns such information. In some cases that static library is

问题 I am working on a static library that handles sensitive data. It is imperative that the developer using the library can not use reflection on the library. On Android, we solve the problem by developing an aar file with service s and run the service into separate process;(When the service is running into another process then the developer can not use reflection) but I am wondering if something similar exists in iOS ? Can we execute a static library into a separate process? if not, how we can

问题 I have compiled some static and shared libraries for Android. Specifically, I have the libraries libcoinblas.a libcoinlapack.a libcoinmetis.a libcoinmumps.a libipopt.a libcoinblas.so libcoinlapack.so libcoinmetis.so libcoinmumps.so libipopt.so Furthermore, these libraries are inter-dependent, that is, Lapack requires Blas Mumps requires Blas and Metis Ipopt requires Mumps, Metis, and Lapack The Android project correctly links and runs when using the shared libraries, but fails to build with

问题 Sorry about the vague question title, I just want to ascertain some things. Static libraries don't link with other static libraries, right? So when I write a slib: A, that uses functionality of another: B, all I have to provide are the headers of B to A, and only those, even if A actually uses functionality from B? Yes? As long as exe: X, which uses A,has B.lib specified as linker input? So that at link time, the linker takes A.lib, which basically only knows that a function of B was called