03-21-2005
'statically linked' means that the image file (the exe file) has every module it could ever need compiled into the file. Therefore it doesn't ever need to open a dynamic library when it runs. So it doesn't know how to load a lib.
Sounds like you are trying to port compiled code. What are you trying to do, exactly? If you expalin your whole problem there are probably lots of folks who know an answer.
10 More Discussions You Might Find Interesting
1. Programming
hi, every body. i have in trouble that how to load a dynamic library by hand.
for example, i know how to generate a dynamic library and how to link a dynamic library in makefile.
generate a dynamic library:
add -dy -G behind cc
link a dynamic library in makefile:
add -dy -Bdynamic behind cc... (0 Replies)
Discussion started by: subrain
0 Replies
2. Programming
how can i do static compilation in cc and -lldap
i have system defined and user defined header file.
Can any one suggest any site where from i can get some information about static and dynamic compilation.
Thankx (1 Reply)
Discussion started by: bhakti
1 Replies
3. Programming
I have a dynamically linked library, providing some functions needed in my project. I have successfully imported it into my VC ++ 6.0 project. Now, i am translating the project into pure C++ (such as avoiding using MFC classess) in Linux box.
Does anyone know if it makes sense to try to use... (2 Replies)
Discussion started by: cy163
2 Replies
4. Programming
Hi,
I have two dynamically loaded libraries (shared objects), both of which include functions of the same name - foo. When I call 'foo' from libA, it takes it from libB, although it is implemented in libA as well. Since we need the function to be called from libA, we tried linking it with the... (1 Reply)
Discussion started by: rimon
1 Replies
5. AIX
I think the default extension on AIX is .a
so for dynamic lib "libabc.a", we can simply link against it by specifying "-labc"
but here I have a dylib which been built by some one else called "libxyz.so" on AIX. once I say "-lxyz" the linker is only looking for libxzy.a but not .so after that.... (2 Replies)
Discussion started by: acerlinux
2 Replies
6. Programming
Hi,
I created two library libsum.so and libproduct.so. In the libproduct.so is defined function "product" that use function "sum" defined in libsum.so. So libproduct depends on libsum.
In main function I called product function by a dlopen request. Unfortunaly, when I execute program I have an... (5 Replies)
Discussion started by: shade82
5 Replies
7. Programming
I am attempting to port a program from OS X to Linux. It's C++ & Qt Creator and I did the original Windows to OS X port, so I tried to make it as POSIX-compliant as possible; the OS X port works well, and the Linux port builds and starts (it's on Ubuntu 9.10) but has some issues running.
The... (2 Replies)
Discussion started by: Hodapp87
2 Replies
8. Homework & Coursework Questions
I need help program in C... :create a program that runs two processes linked oven (1 Reply)
Discussion started by: gizmo16
1 Replies
9. Shell Programming and Scripting
Greetings to every one,
I have to access different clusters for computing.
But the problem is their lib paths are different. :eek:
How can i export some particular library paths for a particular machine ?
For example
Like cluster_1 (ip : 10.169.85.47)
export LD_libPATH="/opt/CUDA"
Like... (2 Replies)
Discussion started by: admax
2 Replies
10. AIX
I want to create a shared lib with certain libs statically linked to it. I can generate a fully shared lib as follows:
gcc -maix64 -DHAVE_CONFIG_H -I. -I./src -DHAVE_OPENSSL -I/usr/include/openssl -I/usr/include -I/usr/include/apr-1 -D_LARGEFILE64_SOURCE -I/usr/java8_64/include -shared -o... (0 Replies)
Discussion started by: amandeepgautam
0 Replies
LEARN ABOUT PHP
tcl_staticpackage
Tcl_StaticPackage(3) Tcl Library Procedures Tcl_StaticPackage(3)
__________________________________________________________________________________________________________________________________________________
NAME
Tcl_StaticPackage - make a statically linked package available via the 'load' command
SYNOPSIS
#include <tcl.h>
Tcl_StaticPackage(interp, pkgName, initProc, safeInitProc)
ARGUMENTS
Tcl_Interp *interp (in) If not NULL, points to an interpreter into which the package has already been loaded (i.e.,
the caller has already invoked the appropriate initialization procedure). NULL means the
package has not yet been incorporated into any interpreter.
const char *pkgName (in) Name of the package; should be properly capitalized (first letter upper-case, all others
lower-case).
Tcl_PackageInitProc *initProc (in) Procedure to invoke to incorporate this package into a trusted interpreter.
Tcl_PackageInitProc *safeInitProc (in) Procedure to call to incorporate this package into a safe interpreter (one that will exe-
cute untrusted scripts). NULL means the package cannot be used in safe interpreters.
_________________________________________________________________
DESCRIPTION
This procedure may be invoked to announce that a package has been linked statically with a Tcl application and, optionally, that it has
already been loaded into an interpreter. Once Tcl_StaticPackage has been invoked for a package, it may be loaded into interpreters using
the load command. Tcl_StaticPackage is normally invoked only by the Tcl_AppInit procedure for the application, not by packages for them-
selves (Tcl_StaticPackage should only be invoked for statically loaded packages, and code in the package itself should not need to know
whether the package is dynamically or statically loaded).
When the load command is used later to load the package into an interpreter, one of initProc and safeInitProc will be invoked, depending on
whether the target interpreter is safe or not. initProc and safeInitProc must both match the following prototype:
typedef int Tcl_PackageInitProc(Tcl_Interp *interp);
The interp argument identifies the interpreter in which the package is to be loaded. The initialization procedure must return TCL_OK or
TCL_ERROR to indicate whether or not it completed successfully; in the event of an error it should set the interpreter's result to point to
an error message. The result or error from the initialization procedure will be returned as the result of the load command that caused the
initialization procedure to be invoked.
KEYWORDS
initialization procedure, package, static linking
Tcl 7.5 Tcl_StaticPackage(3)