Re: zaurus turns off when picogui running

hi eric,

with the -l option you mean the locatin of the libraries for the linker !?
since i`m not that familiar with makefiles i created a little shell 
script for compiling my app. the command line for the linking is:

arm-linux-gcc meineapp.o comio.o libpgui.a -o handleser 
-L/home/peter/buildroot-neu/buildroot-oz/output/staging/usr/lib

where the path after -L is the location of the arm libs......
another possibility is, to use the LDFLAGS environment variable. e.g.

LDFLAGS="-L/home/peter/buildroot-neu/buildroot-oz_neu/output/build/pg-cli_c/src/.libs"

hope that helps you.

btw:
i tried compiling picogui-0.45 for arm "manually" and then just copy the 
pgserver into the buildroot/output . but that didn`t worked for me, 
since i then got a linker error (something with invalid symbols) when 
linking against freetype.
for me worked: compile the pgserver using the openzaurus buildroot, 
compiling the cli_c by hand and link that against my app (statically, 
since there are no more shared cli_c libs as the makefile of the OZ 
buildroots wants ....)

greets, peter


Eric Heinemann wrote:

> Well I am using the buildroot.  My problem is when it is trying to 
> locate the png and freetype libraries.  This problem is 
> occuring because the arm ld does not allow the -l option.  My 
> environment is Mandrake 9.1 running Gnome with OZ's arm-gcc 2.95.3.  
> Any help would be greatly appreciated.  When you finish your project, 
> if you want to make it public, I have a website you could store it on.
>  
> Eric
>
> */Peter Hermsdorf <[email protected]>/* wrote:
>
>     hi eric,
>
>     sending you a zip file is somehow hard, since i use picogui with
>     OZ and
>     thatswhy it is in the buildroot of openzaurus.
>     i don`t know if you use openzaurus too, if so i could maybe give you
>     some hints which may help you gettig picogui compiled (e.g. i wasn`t
>     able to compile the cli_c stuff using OZ buidlroot completly, but i
>     added the neccessary files so that it works too )
>     another possibility would be to compile picogui yourself for arm
>     (i have
>     a ./compile script for that) and then just install the files at the
>     right positions in the output image...... (but that hasn`t worked out
>     for me 100 % )
>
>     maybe you give me some more information about your environment, so i
>     could give you some hints !?
>
>     greets, peter
>
>     Eric Heinemann wrote:
>
>     >Peter,
>     >
>     >I have been banging my head against a wall for the
>     >! last week trying to get PicoGUI to compile for the
>     >Zaurus. After I fix one error, I get another. I have
>     >a favor to ask, would it be possible to get a gzipped
>     >file of all of the picogui files for arm that you have
>     >gotten compiled? This would be greatly appreciated.
>     >I am currently trying to get a PicoGUI only ROM
>     >compiled and running, and well PicoGUI is an integral
>     >part of that.
>     >
>     >Thanks,
>     >Eric
>     >
>     >
>     >--- Peter Hermsdorf
>     >wrote:
>     >
>     >
>     >>the error seems to be the timer_vidblank part.
>     >>when just commenting out
>     >>
>     >> if (timer_vidblank && timer_eval(timer_vidblank +
>     >>timer_lastactivity))
>     >>
>     >>drivermessage(PGDM_POWER,PG_POWER_VIDBLANK,NULL);
>     >>
>     >>the error does not appear.
>     >>i added some printf statements before these lines
>     >>with
>     >&g! t;
>     >> printf("timer_vidblank: %d\n\r",timer_vidblank);
>     > ;> printf("eval statement:
>     >>%d\n\r",timer_eval(timer_vidblank +
>     >>timer_lastactivity));
>     >>
>     >>the output right after starting pgserver on the
>     >>zaurus is
>     >>
>     >># pgserver
>     >>timer_vidblank: 600
>     >>eval statement: 0
>     >>timer_vidblank: 600
>     >>eval statement: 1
>     >>
>     >>all this in < 3 secs (so oviously not 60 as
>     >>configured). so it seems the
>     >>timer_eval function behaves somehow different.
>     >>i wasn`t able to track this down further. hope that
>     >>helps somehow !?
>     >>
>     >>bye,peter
>     >>
>     >>Peter Hermsdorf wrote:
>     >>
>     >>
>     >>
>     >>>>I haven't looked at it yet, but I don't see how
>     >>>>
>     >>>>
>     >>it could be anything but
>     >>
>     >>
>     >>>>the code in timer.c causing the problem. That
>     >>>> *>>>>
>     >>code doesn't depend on
>     >>
>     >>
>     >>>>much else, so it shouldn't take much 'big
>     >>>>
>     >>>>
>     >>picture' knowledge to find the
>     >>
>     >>
>     >>>>problem.
>     >>>>
>     >>>>
>     >>>>
>     >>>>
>     >>>ok. i`ll see what i can do.....
>     >>>
>     >>>
>     >>>
>     >>>>PicoGUI suspends the zaurus by issuing a command
>     >>>>
>     >>>>
>     >>in /proc, but it
>     >>
>     >>
>     >>>>shouldn't have any effect on poweron.
>     >>>>
>     >>>>
>     >>>>
>     >>>>
>     >>>this behaviour is the same in console only mode,
>     >>>
>     >>>
>     >>so it has nothing
>     >>
>     >>
>     >>>specific to PicoGUI..... maybe i have to ask this
>     >>> >>>
>     >>question on
>     >>
>     >>
>     &g t;>>openzaurus-dev.
>     >>>bye,peter
>     >>>
>     >>>
>     >>>
>     >>>>>Micah Dowty wrote:
>     >>>>>
>     >>>>>
>     >>>>>
>     >>>>>
>     >>>>>
>     >>>>>>I've seen this problem before now that you
>     >>>>>>
>     >>>>>>
>     >>mention it, but I haven't
>     >>
>     >>
>     >>>>>>looked into it and it seems to have escaped
>     >>>>>>
>     >>>>>>
>     >>from the collector :)
>     >>
>     >>
>     >>>>>>The input driver for the zaurus includes a
>     >>>>>>
>     >>>>>>
>     >>driver message handler to
>     >>
>     >>
>     >>>>>>support picogui's suspend timer. You can see
>     >>>>>>
>     >>>>>>
>     >>this in
>     >> !
>     >>
>     >>>>>>server/input/zaurus.c
>     >>>>>>
>     >>>>>>The suspend timer itself is in
>     >>>>>>
>     >>>>>>
>     >>server/gcore/timer.c
>     >>
>     >>
>     >>>>>>In README.configfile, the timers.sleep property
>     >>>>>>
>     >>>>>>
>     >>is shown to have the
>     >>
>     >>
>     >>>>>>default value zero, meaning that the timer is
>     >>>>>>
>     >>>>>>
>     >>disabled. Check whether
>     >>
>     >>
>     >>>>>>your pgserver.conf is overriding this. If so,
>     >>>>>>
>     >>>>>>
>     >>try commenting out that
>     >>
>     >>
>     >>>>>>line. If it looks correct, try adding printf()s
>     >>>>>>
>     >>>>>>
>     >>or breakpoints! to
>     >>
>     >>
>     >>>>>>timer.c
>     > ;>>>>>
>     >>>>>>If you don't feel like fixing this right away
>     >>>>>>
>     >>>>>>
>     >>or at all, add
>     >>
>     >>
>     >>>>>>it to the collector and it will be eventually
>     >>>>>>
>     >>>>>>
>     >>fixed.
>     >>
>     >>
>     >>>>>>--Micah
>     >>>>>>
>     >>>>>>On Fri, May 02, 2003 at 03:40:21PM +0200, Peter
>     >>>>>>
>     >>>>>>
>     >>Hermsdorf wrote:
>     >>
>     >>
>     >>>>>>
>     >>>>>>
>     >>>>>>
>     >>>>>>
>     >>>>>>>hi all,
>     >>>>>>>
>     >>>>>>>i finally got hello.c running, but there is a
>     >>>>>>>
>     >>>>>>>
>     >>funny effect: after
>     >! ;>
>     >>
>     >>>>>>>starting pgserver the display immediately
>     >>>>>>>
>     >>>>>>>
>     >>shuts down. when
>     >>
>     >>
>     >>>>>>>pressing a key, let`s say the OK-Key, the
>     >>>>>>>
>     >>>>>>>
>     >>screen turns on and i
>     >>
>     >>
>     >>>>>>>can see the hello world window,when i release
>     >>>>>>>
>     >>>>>>>
>     >>the key the screen
>     >>
>     >>
>     >>>>>>>immediately turns off. when again pressing a
>     >>>>>>>
>     >>>>>>>
>     >>key, it turns on
>     >>
>     >>
>     >>>>>>>again and i have to keep the key pressed to
>     >>>>>>>
>     >>>>>>>
>     >>see something.
>     >>
>     >&! gt;
>     >>>>>>>anybody knows what`s the problem? . .. is this
>     >>>>>>>
>     >>>>>>>
>     >>maybe some
>     >>
>     >>
>     >>>>>>>misconfigured energy saving feature or
>     >>>>>>>
>     >>>>>>>
>     >>something ?
>     >>
>     >>
>     >>>>>>>thx for any help!
>     >>>>>>>
>     >>>>>>>bye,peter
>     >>>>>>>
>     >>>>>>>
>     >>>>>>>
>     >>>>>>>
>     >>>
>     >>>
>     >>>
>     >>>
>     *
>




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge