shared-libraries

What is the best practice for sharing the assemblies of a bin folder across multiple ASP.net websites in IIS 7? I've got several sites, each with slightly different HTML front ends, but all with the same middle tier logic and DB. I don't want to redploy the same dlls to each of the many site's bin folders everytime I make a change. Thanks. Yes, actually, you do want to deploy them individually. That's how it works. If this truly offends you, then consider whether this common code should be in a WCF service called by all those sites. Another option is to make your .Net code smart enough so that

Is it possible to have a Fortran program load a Fortran library at run time? If so, would it be possible to modify a function and recompile only the library to have the originally-compiled program call the modified function in the library at run time? If anyone can provide a minimal working example of how this could be achieved that would be great. Here are some few links that can be helpfull: This page on rosettacode.org which gives complete example with details and discuss implementation on linux and MACOS This intel forum post where Steve Lionel give some advice on how to do the dynamic

Coming from PHP, this is my first experience with C/C++ (so go easy on me). I'm following this tutorial to write a simple script using the FreeType library. The following compiles just fine: #include <ft2build.h> #include FT_FREETYPE_H main() { FT_Library library; FT_Face face; } This tells me that the FreeType library is readily available to the compiler. However, things break once I try to use any methods. For example, take the following script: #include <ft2build.h> #include FT_FREETYPE_H main() { int error; FT_Library library; error = FT_Init_FreeType(&library); if (error) {} FT_Face face;

This question already has an answer here: Main Program and Shared Library initializes same static variable in __static_initialization_and_destruction_0 1 answer I am working on a project that has a class 'A' that contains a static stl container class. This class is included in both my main program and a .so file. The class uses the default(implicit, not declared) constructor/destructor. The main program loads the .so file using dlopen() and in its destructor, calls dlclose(). The program crashes after main exits when glibc calls the destructor for the static class member variable. The problem

Technically, in terms of file content, what is the difference between the output of gcc -fPIC -shared src.c and gcc -fPIC src.c ? Assume that int main(int, char**) is defined in src.c so that both compilations succeed. But executing the a.out generated by gcc -shared src.c , as expected, gave the following error: -bash: ./a_shared.out: cannot execute binary file Even if there is a main function it it. Also, how can I inspect the difference in the output files using tools like otool or objdump ? Thanks a lot. Shared libraries and executables use the same format: they are both loadable images.

I want to include libgpg-error and libgcrypt in my swift-project and created the following module.modulemaps: libgpgerror: module libgpgerror { header "/Volumes/Xcode/Programme/Swifts/KCAnon/KCAnon_Client/Libs/libgpgerror/gpg-error.h" link "'/Volumes/Xcode/Programme/Swifts/KCAnon/KCAnon_Client/Libs/libgpgerror/libgpgerror-1.21.dylib'" export * } libgcrypt: module libgcrypt { header "/Volumes/Xcode/Programme/Swifts/KCAnon/KCAnon_Client/Libs/libgcrypt/gcrypt.h" link "'/Volumes/Xcode/Programme/Swifts/KCAnon/KCAnon_Client/Libs/libgcrypt/libgcrypt-1.6.5.dylib'" export * } I also added the "Swift

I'm building a shared object file from a group of C++ source files using GCC. All the example tutorials on building .so files show the file created with a version number after the .so suffix. For example: gcc -shared -Wl,-soname,libmean.so.1 -o libmean.so.1.0.1 calc_mean.o This would produce the .so file libmean.so.1.0.1 Additionally, if I browse the /usr/lib directory on my local machine, I see that many of the .so files have version numbers at the end. However, when I compile a shared object file and place it in /usr/lib , the linker is unable to find it if I put a version number at the end.