03-02-2011
Quote:
I really don't think you can make one member of a class be exported from the code into the library, and the rest exported from the library to the code.
Yep, that's why I want to take the base class cpp file (which has the static menber) out of the library since it's also in the main app.
Here's how it's set up: In the project I have a base class header and cpp. In the library I have a subclass header and cpp. The library also includes the base class header. It doesn't have the base class definition, which I want to be resolved when the library is loaded in.
Earlier, I was adding in the base class cpp to the library (plus whatever else it needed). But I did some research and it seems I don't need to include all those definitions in both. As one site puts it:
(Sorry, I have to mangle this url because I'm not allowed to post links yet)
www
.informit.
com/articles
/article.aspx?p=22435&rll=1:
Quote:
A shared library may also contain references to functions and variables that aren't themselves defined in the shared library
...
If your main executable exports any dynamic symbols (as if it were a shared library), these symbols may be used.
Since I took unnecessary definitions outside of the library the library hasn't even been loading. If I can get it to load, I am hoping that static member won't be duplicated.
Edit: Just to make sure we're using the same terms: by definition I mean cpp and by declaration I mean header.
Last edited by dorik; 03-02-2011 at 12:31 PM..
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I have been trying to create a sharef object on my HP UX 11 machine
(HP-UX <myhostname> B.11.00 A 9000/879 ...... two-user license)
to create the shared object first I am creating the object file using
cc -Aa -c +z dyn.c
(I use -Aa and +z as per HP's manual on linkers ) to create the... (0 Replies)
Discussion started by: linuxpenguin
0 Replies
2. Linux
Hi All,
I created the share object file using
gcc -shared -fpic mypp.cpp -o myp.so
but, pls tell me how to link this .so file to my client program.
Thanks (0 Replies)
Discussion started by: sarwan
0 Replies
3. AIX
Hi,
When using shared objects on AIX 4.3 i am getting runtime problems.
I have a small sample program which links to a shared object libray, oracle and system related libraries.
At runtime it fails (gives segmentation fault and coredump ) in one proc file when executing login statement.
But... (0 Replies)
Discussion started by: suman_jakkula
0 Replies
4. Programming
Hi
I have a multithreaded daemon(server) which will accept connections from various clients and sends back results to them.
In order to serve my daemon clients, it has to establish a TCP connection to another server(vendor supplied which is listening on a specific TCP port) and gets the... (11 Replies)
Discussion started by: axes
11 Replies
5. UNIX for Advanced & Expert Users
Hi All,
I have a problem with the shared objects setup in AIX. We have a customized shell written by the developers over here. When i issue a MQ Series command (mqsilist) it is giving the error as . All the commands making use of this libImbCmdLib.a.so is failing. But when executed in normal... (1 Reply)
Discussion started by: dhanamurthy
1 Replies
6. Shell Programming and Scripting
Hi,
I have created a shared object (abc.so) which has a function sum(int a, int b).
Is there any way to load the "abc.so" and use the sum function using shell script..
thanks in advance (2 Replies)
Discussion started by: yhacks
2 Replies
7. AIX
Hi all,
I am developing an application with two components. One "c" binary and one "C++" shared object.
While execution, the shared object crashes out and core dump is created whenever "new" is executed. But if i use malloc this will work perfectly.
I tried to use dbx. Below given was... (1 Reply)
Discussion started by: itssujith
1 Replies
8. Programming
Hello,
While running a c++ shared object on AIX I am facing below error -
rtld: 0712-001 Symbol __ct__3ETDFv was referenced
from module /bancs/aml/lib/libmonitor.so(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol etd_insert__3ETDFv was... (3 Replies)
Discussion started by: yatrik007
3 Replies
9. Red Hat
Hi,
I would like to create a shared object ( .so).
This shared object
1. uses the functions from a library.
2. Also it should be able to use the global variable in an app
To achieve this what should I do ? 1) To use the functions in the library should I give the -ld option while... (1 Reply)
Discussion started by: rvan
1 Replies
10. Programming
Hello,
I am not that experienced with Linux, and I am currently facing some issues.
The application I'm working on uses hundreds of threads. To optimize the memory usage, I am putting all my data inside a shared object (so).
The steps for this are as follows:
1. a C file (generated... (17 Replies)
Discussion started by: Maelstrom
17 Replies
LEARN ABOUT DEBIAN
shtool-scpp
SHTOOL-SCPP.TMP(1) GNU Portable Shell Tool SHTOOL-SCPP.TMP(1)
NAME
shtool-scpp - GNU shtool C source file pre-processor
SYNOPSIS
shtool scpp [-v|--verbose] [-p|--preserve] [-f|--filter filter] [-o|--output ofile] [-t|--template tfile] [-M|--mark mark] [-D|--define
dname] [-C|--class cname] file [file ...]
DESCRIPTION
This command is an additional ANSI C source file pre-processor for sharing cpp(1) code segments, internal variables and internal functions.
The intention for this comes from writing libraries in ANSI C. Here a common shared internal header file is usually used for sharing
information between the library source files.
The operation is to parse special constructs in files, generate a few things out of these constructs and insert them at position mark in
tfile by writing the output to ofile. Additionally the files are never touched or modified. Instead the constructs are removed later by the
cpp(1) phase of the build process. The only prerequisite is that every file has a ``"#include ""ofile"""'' at the top.
This command provides the following features: First it avoids namespace pollution and reduces prototyping efforts for internal symbols by
recognizing functions and variables which are defined with the storage class identifier ``cname''. For instance if cname is ``intern'', a
function ``"intern void *foobar(int quux)"'' in one of the files is translated into both a ``"#define foobar __foobar"'' and a ``"extern
void *foobar(int quux);"'' in ofile. Additionally a global ``"#define" cname "/**/"'' is also created in ofile to let the compiler silently
ignore this additional storage class identifier.
Second, the library source files usually want to share "typedef"s, "#define"s, etc. over the source file boundaries. To achieve this one
can either place this stuff manually into tfile or use the second feature of scpp: All code in files encapsulated with ``"#if "dname ...
"#endif"'' is automatically copied to ofile. Additionally a global ``"#define" dname 0'' is also created in ofile to let the compiler
silently skip this parts (because it was already found in the header).
OPTIONS
The following command line options are available.
-v, --verbose
Display some processing information.
-p, --preserve
Preserves ofile independent of the generated ``#line'' lines. This is useful for Makefiles if the real contents of ofile will not
change, just line numbers. Default is to overwrite.
-f, --filter filter
Apply one or more pre-processing sed(1) filter commands (usually of type ``"s/.../.../"'') to each input file before their input is
parsed. This option can occur multiple times.
-o, --output ofile
Output file name. Default is "lib.h".
-t, --template tfile
Template file name. Default is "lib.h.in".
-M, --mark mark
Mark to be replaced by generated constructs. Default is "%%MARK%%".
-D, --define dname
FIXME. Default is "cpp".
-C, --class cname
FIXME. Default is "intern".
EXAMPLE
# Makefile
SRCS=foo_bar.c foo_quux.c
foo_p.h: foo_p.h.in
shtool scpp -o foo_p.h -t foo_p.h.in
-M %%MARK%% -D cpp -C intern $(SRCS)
/* foo_p.h.in */
#ifndef FOO_P_H
#define FOO_P_H
%%MARK%%
#endif /* FOO_P_H */
/* foo_bar.c */
#include "foo_p.h"
#if cpp
#define OURS_INIT 4711
#endif
intern int ours;
static int myone = 0815;
intern int bar(void)
{
ours += myone;
}
/* foo_quux.c */
#include "foo_p.h"
int main(int argc, char *argv[])
{
int i;
ours = OURS_INIT
for (i = 0; i < 10; i++) {
bar();
printf("ours now %d
", ours);
}
return 0;
}
HISTORY
The GNU shtool scpp command was originally written by Ralf S. Engelschall <rse@engelschall.com> in 1999 for GNU shtool. Its was prompted
by the need to have a pre-processing facility in the GNU pth project.
SEE ALSO
shtool(1), cpp(1).
18-Jul-2008 shtool 2.0.8 SHTOOL-SCPP.TMP(1)