shared-libraries

问题 I'm currently working on an shared library based on mono, where I want to put as much business logic of my app as possible. I used this helpful tutorial. I managed putting the whole logic for rest-requests in this shared library, but now I'm stuck with soap. I used the wsdl command of mono to generate Client Stubcode from my wsdl (as described here http://www.mono-project.com/Web_Services). When I put the generated class to my C# library, which is the root project of my shared library, there

问题 I have an Android Studio project which depends on a native shared library. I have created a cmake file to compile the library and I have added a soft link to the shared library inside the android project (in src/main/jniLibs/armeabi ). That way when the android project is built, the shared library is included in the package. Here is the relevant part of build.gradle : android { ... externalNativeBuild { cmake { path "../cpp/CMakeLists.txt" } } } The problem is that gradle tries to open the

问题 I have a question which may be somewhat silly because I'm pretty sure I may know the answer already. Suppose you have static library A, and dynamic shared object library B and your program C under linux. Suppose that library A calls functions from library B and your program calls functions from library A. Now suppose that all functions that C calls in A make no use of functions in B. To compile C will it be enough to link just A and omit B and furthermore can your program C be run on a system

问题 I'm facing a weird problem. I'm building a shared library for my Android application. I can't build both armv5 and armv7 at the same time. If I do so, I get a lot of errors on my source files at the second run (when the ndk build the armV7 lib) like: FinderPatternInfo.o: previous definition here multiple definition of ... My Application.mk APP_ABI := armeabi armeabi-v7a APP_PLATFORM := android-8 APP_STL := stlport_static APP_CPPFLAGS += -fexceptions It works perfectly if I only set APP_ABI :=

问题 I have two static libraries which seem to have duplicate symbols(TBXML.o) and won't compile. ld: duplicate symbol _OBJC_METACLASS_$_TBXML in /Users/Hoya/Desktop/SocialSync/include/SMUFLib/deviceLib/libSFCommonLibs.a(TBXML.o) and /Users/Hoya/Desktop/SocialSync/Cauly/libCaulyDevice.a(TBXML.o) for architecture armv6 Command /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/clang failed with exit code 1 The developer of both libraries don't provide the source code so there is nothing I can

问题 I'm trying to learn some libuv and it seems there's a great book that goes through it. However, the book doesn't explain how to actually compile it. I ran make on the code that I pulled from github, and compiled with GYP as described on the github (https://github.com/joyent/libuv). However I'm not sure what kind of libraries I need to include to get the code to compile. I tried to compile this code: /* first.c */ #include <stdio.h> #include <uv.h> int main() { uv_loop_t *loop = uv_loop_new();

问题 I'm trying to figure out how an operating system handles multiple unrelated processes loading the same DLL/shared library. The OSes I'm concerned with are Linux and Windows, but to a lesser extent Mac as well. I presume the answers to my questions will be identical for all operating systems. I'm particularly interested in regards to explicit linking, but I'd also like to know for implicit linking. I presume the answers for both will also be identical. This is the best explanation I've found

问题 My build environment is CentOS 5 . I have a third party library called libcunit. I installed it with autotools and it generates both libcunit.a and libcunit.so . I have my own application that links with a bunch of shared libraries. libcunit.a is in the current directory and libcunit.so and other shared libraries are in /usr/local/lib/ . When I compile like: gcc -o test test.c -L. libcunit.a -L/usr/local/lib -labc -lyz I get a linkage error: libcunit.a(Util.o): In function `CU_trim_left':

问题 An application ( app ) depends on two shared librarys: liba.so and libb.so . liba and libb have the same function of void Hello() but with different implementations. Load the two shared libraries at runtime and try to access the two versions of Hello(). I load liba.so and libb.so by poco C++ shared-library, but eventually it calls dlopen() to load shared libraries. Here's the code: #include "Poco/SharedLibrary.h" using Poco::SharedLibrary; typedef void (*HelloFunc)(); // function pointer type

问题 I am migrating a production app from bamboo stack to cedar, I successfully pushed the app on cedar but resulting in error like LoadError: Could not open library 'lib.so': lib.so: cannot open shared object file: No such file or directory from /app/vendor/bundle/ruby/1.9.1/gems/ffi-1.0.9/lib/ffi/library.rb:75:in `block in ffi_lib' from /app/vendor/bundle/ruby/1.9.1/gems/ffi-1.0.9/lib/ffi/library.rb:54:in `map' from /app/vendor/bundle/ruby/1.9.1/gems/ffi-1.0.9/lib/ffi/library.rb:54:in `ffi_lib'