This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: Problem Making Shared Library
- To: cygwin at cygwin dot com
- Subject: Re: Problem Making Shared Library
- From: "Charles S. Wilson" <cwilson at ece dot gatech dot edu>
- Date: Fri, 09 Feb 2001 13:25:55 -0500
- CC: Hadi Bannazadeh <hadi at itrc dot ac dot ir>
- References: <002201c092ee$7ef79380$02c8c9c8@node2> <20010209114047.H18080@redhat.com>
Take a look at one of the 'dll-ized' libraries' sourcecode. You can
find that on any cygwin mirror in the cygwin/contrib/ directory. Look
at:
zlib, libpng, jbigkit, jpeg, tiff, ncurses, readline, gdbm, or gettext.
jbigkit is probably the most straightforward example of 'dll-izing'.
--Chuck
> >when I made a .so file and used it as shared library
> >by (gcc -ladd) which add is shared Lib name I found
> >that all Functions in add library are exported!
> >of course we have problem if we use some functions with same names in different libraries and the main program.
> >as I know in VC++ or BorlandC I use _declspec(dllexport)
> >or __export in front of exported functions prototype.
> >and all other functions remain private for that DLL.
> >How I can solve this problem
> >Please Help me!!
> >Best Regards
> >Hadi
> >Iran Telecommunication Research Center
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple