nanogui: Thread: Shared Library

Hi, 

Dose anyone use shared  library for microwindows ?
I used '-rpath' options for linker(ld) and it dose not
work properly.  How can I know if shared library's
path is properly resolved in ?   I know 'ldd' can show 
in Linux desktop.  My target is SH3. 

Kyoung Kim

Exactly what errors are you getting?  When you compile your target,
compile it so that it can find the shared libraries just like you would
do with a static library (-L<path> and -l<library>.  Don't forget the
-shared command too.. :) ).  Then, you should just be able to put the
shared libraries in /usr/lib on your target, and the program will be
able to find it.  You also need to have ld.so on your target, and you
need to make sure that your /etc/ld.so.conf lists all the directories
you should search, and that should take care of it.  The nice thing
about shared libraries is that they are portable as long as you keep
your system properly configured.  What kernel are you running?

Happy hacking!
Jordan

 "KIM,KYOUNG-IL (HP-Cupertino,ex1)" wrote:
> 
> Hi,
> 
> Dose anyone use shared  library for microwindows ?
> I used '-rpath' options for linker(ld) and it dose not
> work properly.  How can I know if shared library's
> path is properly resolved in ?   I know 'ldd' can show
> in Linux desktop.  My target is SH3.
> 
> Kyoung Kim
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

Hi,
	Have anyone tried the Microwindows(nanox api) as shared library?.
As i seen the Greg's mail, he recommended not to use shared library and,
when u use shared library, global data is not initalising properly.

	In my case, i came into the situation that, i must use shared library.

	If anyone has already tried sharedlibrary, please give some hints/ideas
that, where are all it will give the problem.

With regards,
Sadeesh.

Hi Greg,
	Can you give some suggestion for the shared library?.

With regards,
sadeesh.

-----Original Message-----
From: Sadeesh Kumar ####@####.####
Sent: Tuesday, May 29, 2001 7:57 PM
To: ####@####.####
Subject: [nanogui] Shared Library


Hi,
	Have anyone tried the Microwindows(nanox api) as shared library?.
As i seen the Greg's mail, he recommended not to use shared library and,
when u use shared library, global data is not initalising properly.

	In my case, i came into the situation that, i must use shared library.

	If anyone has already tried sharedlibrary, please give some hints/ideas
that, where are all it will give the problem.

With regards,
Sadeesh.





---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####

I am not sure what OS you are using, but I found the following useful on
Linux.

Try using an _init() method so that it is automatically invoked before
dlopen() returns when a shared lib is first opened.

Good luck,

Rob

Sadeesh Kumar wrote:
> 
> Hi Greg,
>         Can you give some suggestion for the shared library?.
> 
> With regards,
> sadeesh.
> 
> -----Original Message-----
> From: Sadeesh Kumar ####@####.####
> Sent: Tuesday, May 29, 2001 7:57 PM
> To: ####@####.####
> Subject: [nanogui] Shared Library
> 
> Hi,
>         Have anyone tried the Microwindows(nanox api) as shared library?.
> As i seen the Greg's mail, he recommended not to use shared library and,
> when u use shared library, global data is not initalising properly.
> 
>         In my case, i came into the situation that, i must use shared library.
> 
>         If anyone has already tried sharedlibrary, please give some hints/ideas
> that, where are all it will give the problem.
> 
> With regards,
> Sadeesh.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

Hi,
	I think u wrongly understood my question.
For me, the problem is only in using of microwindows shared library.

	ok, i will explain my problem in detail.

	Rightnow i am using microwindows 0.89 pre7. I have to build the
microwindows as a shared library.
	When i tested this shared library build in embedded linux on x86(pc)
platform, it is working fine. I didn't find any problem.

	But my target platform is PPC405gp. So i crosscompiled(using ppc_4xx-gcc)
and built the microwindows shared library for ppc. When i tested this, i am
facing the problem in mouse handling. but when i tested the static library,
everything works fine.

	I remember, Greg, one of his email recommended that, not to use shared
library. But i came into the situation that, i have to use shared library.
 Even now, i don't know why it is giving problem in only ppc not in x86. )

	So for that, if anyone of you share your experiences in microwindows shared
library, it will be very helpful to fix the shared library problem.

With regards,
sadeesh.






-----Original Message-----
From: ####@####.#### ####@####.#### Behalf Of Robert E.
Hartley
Sent: Thursday, May 31, 2001 8:33 PM
To: ####@####.####
Subject: Re: [nanogui] Shared Library


I am not sure what OS you are using, but I found the following useful on
Linux.

Try using an _init() method so that it is automatically invoked before
dlopen() returns when a shared lib is first opened.

Good luck,

Rob

Sadeesh Kumar wrote:
>
> Hi Greg,
>         Can you give some suggestion for the shared library?.
>
> With regards,
> sadeesh.
>
> -----Original Message-----
> From: Sadeesh Kumar ####@####.####
> Sent: Tuesday, May 29, 2001 7:57 PM
> To: ####@####.####
> Subject: [nanogui] Shared Library
>
> Hi,
>         Have anyone tried the Microwindows(nanox api) as shared library?.
> As i seen the Greg's mail, he recommended not to use shared library and,
> when u use shared library, global data is not initalising properly.
>
>         In my case, i came into the situation that, i must use shared
library.
>
>         If anyone has already tried sharedlibrary, please give some
hints/ideas
> that, where are all it will give the problem.
>
> With regards,
> Sadeesh.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

There are many global variables that will reach up and bite you when you try 
to use shared libraries.  This is especially true when you start using 
multiple clients.  Plus, to make things even more fun, the bugs are very hard 
to find (true to the nature of the shared library).  

The best solution is to start taking the global variables that differ from 
client to client and put them into an array or linked list of structures, and 
requiring that each client register before using the database (something that 
can be easily done in GrOpen).  

This is definately something that should be done at some point, but as long 
as statically compiled Nano-X programs continue to weigh in at about 20 - 30K 
a piece, I won't be *too* worried.    

Jordan

On Thursday 31 May 2001 04:52, Sadeesh Kumar mentioned:
> Hi,
> 	I think u wrongly understood my question.
> For me, the problem is only in using of microwindows shared library.
>
> 	ok, i will explain my problem in detail.
>
> 	Rightnow i am using microwindows 0.89 pre7. I have to build the
> microwindows as a shared library.
> 	When i tested this shared library build in embedded linux on x86(pc)
> platform, it is working fine. I didn't find any problem.
>
> 	But my target platform is PPC405gp. So i crosscompiled(using ppc_4xx-gcc)
> and built the microwindows shared library for ppc. When i tested this, i am
> facing the problem in mouse handling. but when i tested the static library,
> everything works fine.
>
> 	I remember, Greg, one of his email recommended that, not to use shared
> library. But i came into the situation that, i have to use shared library.
>  Even now, i don't know why it is giving problem in only ppc not in x86. )
>
> 	So for that, if anyone of you share your experiences in microwindows
> shared library, it will be very helpful to fix the shared library problem.
>
> With regards,
> sadeesh.
>
>
>
>
>
>
> -----Original Message-----
> From: ####@####.#### ####@####.#### Behalf Of Robert E.
> Hartley
> Sent: Thursday, May 31, 2001 8:33 PM
> To: ####@####.####
> Subject: Re: [nanogui] Shared Library
>
>
> I am not sure what OS you are using, but I found the following useful on
> Linux.
>
> Try using an _init() method so that it is automatically invoked before
> dlopen() returns when a shared lib is first opened.
>
> Good luck,
>
> Rob
>
> Sadeesh Kumar wrote:
> > Hi Greg,
> >         Can you give some suggestion for the shared library?.
> >
> > With regards,
> > sadeesh.
> >
> > -----Original Message-----
> > From: Sadeesh Kumar ####@####.####
> > Sent: Tuesday, May 29, 2001 7:57 PM
> > To: ####@####.####
> > Subject: [nanogui] Shared Library
> >
> > Hi,
> >         Have anyone tried the Microwindows(nanox api) as shared library?.
> > As i seen the Greg's mail, he recommended not to use shared library and,
> > when u use shared library, global data is not initalising properly.
> >
> >         In my case, i came into the situation that, i must use shared
>
> library.
>
> >         If anyone has already tried sharedlibrary, please give some
>
> hints/ideas
>
> > that, where are all it will give the problem.
> >
> > With regards,
> > Sadeesh.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####