shared-libraries

Python's easy_install and custom header/library location

扶醉桌前 提交于 2019-12-06 16:09:26
问题 I am trying to install adns-python using linux and had to recompile adns with some special options, so I can't seem to use easy_install <tarball> as I normally would (py26_default)[mpenning@localhost src]$ easy_install adns-python-1.2.1.tar.gz Processing adns-python-1.2.1.tar.gz Running adns-python-1.2.1/setup.py -q bdist_egg --dist-dir /tmp/easy_install-9cVl4i/adns-python-1.2.1/egg-dist-tmp-vvO8Ms adnsmodule.c:10:18: error: adns.h: No such file or directory adnsmodule.c:31: error: expected

How can I make lazy/delay loading work in Linux?

心不动则不痛 提交于 2019-12-06 15:55:01
I got this working great on Windows -- application loads my plugin (C++, Qt), my plugin does a smart search to find an installed JRE, sets the library search path accordingly, and then calls a function in the JVM which forces the jvm.dll to be loaded at that point. (Previous question: How can I deploy a mixed C++/Java (JNI) application? ) Now I'm trying to get it working on Linux. From what I read, lazy linking/loading was the default, so I thought it would just work.... doesn't seem like it. I'd like to avoid dlopen() and dlsym() , LD_LIBRARY_PATH , ldconfig , etc. The idea is that users of

*.so library from included *.jar involves UnsatisfiedLinkError

╄→尐↘猪︶ㄣ 提交于 2019-12-06 14:29:44
问题 I've wrote android app with native shared library ( libnativeext.so ). Inside java class in app I load libnativeext.so with System.loadLibrary("nativeext"). All works great. Native code compiles, and libnativeext.so places in /libs/armeabi/ folder. So final first.apk file contains /lib/armeabi/libnativeext.so , installs on device and all work ok. Then I export project in javaext.jar . At this point javaext.jar contains libnativeext.so in /libs/armeabi/ . In the new project (second-proj) I

Linux, Mono, shared libs and unresolved symbols

只愿长相守 提交于 2019-12-06 14:25:55
I have a shim library (shared, C++) which calls functions in another shared library (libexif) and presents a simple interface to C# for Platform Invoke calls. (That is, a C# program uses PInvoke to call my custom shared library which in turn calls another shared library.) In Windows, my custom shared library links to the shared library when my custom library links and when the C# application executes, all symbols are resolved. On Linux, linking my shared library does not link the other shared library. With a C++ driver, I specify the other library when the application is linked and at that

Shared Libraries in Same Folder with App in TCSH

耗尽温柔 提交于 2019-12-06 13:41:34
问题 I am deploying a locally-compiled app to a remote Linux server. Since I don't have root account I cannot put needed shared libraries to /usr/lib Is there a way to overcome this? I put libraries in same folder and changed "path" variable but did not work. 回答1: Two simple options. You can set the LD_LIBRARY_PATH variable inside your script (see Section 3.3.1. of the shared libraries HOWTO). There are problems with this approach for production code, but if set in a wrapper script is probably ok.

binary compatibility vs backward compatibilty

我们两清 提交于 2019-12-06 13:37:41
问题 I've been reading some details about Qt d-pointer and came across the binary compatibility term. Is this the same as backward compatibility? 回答1: Backward compatibility of shared libraries includes: Binary compatibility Source compatibility Behavioral compatibility So, the answer is NO. Binary compatibility is only the part of backward compatibility. See the "Kinds of Compatibility: Source, Binary, and Behavioral" for more info. 来源: https://stackoverflow.com/questions/5728838/binary

visual studio 2015 android is missing .mk files for NDK native development

ぐ巨炮叔叔 提交于 2019-12-06 13:29:40
I am using Visual Studio 2015 to compile and test Android native c++ code. I really need to use LOCAL_SHARED_LIBRARIES in android.mk file to use shared native library. But Visual Studio 2015 doesn't even have .mk files. Instead a bunch of XMLs is used. Please help me. 来源: https://stackoverflow.com/questions/36219677/visual-studio-2015-android-is-missing-mk-files-for-ndk-native-development

How are variables in shared libraries referenced by loader?

梦想与她 提交于 2019-12-06 13:21:58
I now understand how dynamic functions are referenced, by procedure linkage table like below: Dump of assembler code for function foo@plt: 0x0000000000400528 <foo@plt+0>: jmpq *0x2004d2(%rip) # 0x600a00 <_GLOBAL_OFFSET_TABLE_+40> 0x000000000040052e <foo@plt+6>: pushq $0x2 0x0000000000400533 <foo@plt+11>: jmpq 0x4004f8 (gdb) disas 0x4004f8 No function contains specified address. But I don't know how dynamic variables are referenced,though I found the values are populated in the GOT once started,but there's no stub like above,how does it work? The dynamic loader relocates all references to

how to investigate python2 segfault on imp.load_module

妖精的绣舞 提交于 2019-12-06 11:55:36
I am trying to install and use dolfin on Arch Linux, with Python 2.7.3. What is the best way to find out what is causing segmentation faults such as these? $ python2 -c "import dolfin; print dolfin.__version__" [3] 6491 segmentation fault (core dumped) python2 -c "import dolfin; print dolfin.__version__" I have tried inspecting the core file through gdb: $ sudo systemd-coredumpctl gdb 6491 but they are always truncated: Reading symbols from /usr/bin/python2.7...(no debugging symbols found)...done. BFD: Warning: /var/tmp/coredump-wSi8DV is truncated: expected core file size >= 39694336, found:

Telegram for Android, confusing NDK error

こ雲淡風輕ζ 提交于 2019-12-06 11:07:25
So I have downloaded Telegram messenger source from GitHub, and I am trying to get it to run on Android Studio for the first time. Now the error is as below: The build failed message is: Error:error: CreateProcess: No such file or directory The detailed log in Gradle Console is: FAILURE: Build failed with an exception. What went wrong: Execution failed for task ':TMessagesProj:externalNativeBuildArmv7Debug'. Build command failed. Error while executing process D:\AndroidStudio\sdk\ndk-bundle\ndk-build.cmd with arguments {NDK_PROJECT_PATH=null APP_BUILD_SCRIPT=C:\TMessagesProj\jni\Android.mk NDK