Thanks for the tip but I have that line already. Here is my /etc/directfbrc:
bash-2.05b# cat /etc/directfbrc debug banner no-vt-switch depth=32 bg-color=00000000 pixelformat=ARGB wm=sawman I don't get how the "testrun" process can locate the sawman manager created by the "testman" process. Could anyone explain that for me? IPC? Best regards, Lars Salomonsson Pedro Aguilar wrote: > Hi, > > You have to add the "wm = sawman" option in the directfbrc file. > See the directfbrc man page. > > Regards, > -- > Pedro Aguilar > > >> Hi. >> >> I hope someone can help a newbie with SaWMan. I'm trying to follow the >> README file to get the tiled windows on my screen (a TV connected to my >> target). The framebuffer/DirectFB stuff is working because I can run the >> example apps like df_andi etc so I guess that I don't need any >> 'gfxdrivers' directory. The problem is that I don't get it how the >> SaWMan should be used. >> >> The README section "Running testman" says: >> >> "Once you have a session running after setting the option "wm = sawman" >> ..." >> >> What is the meaning with "session" here? >> >> I try to run it this way: I have two telnet sessions to my target. In >> session #1 I start "testman": >> >> bash-2.05b# ./testman >> (*) SaWMan/TestMan: Initializing... >> >> =======================| DirectFB 1.0.0 |======================= >> (c) 2001-2007 The DirectFB Organization (directfb.org) >> (c) 2000-2004 Convergence (integrated media) GmbH >> ------------------------------------------------------------ >> >> (*) DirectFB/Core: Single Application Core. (2007-09-07 11:18) >> (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 1686)... >> (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 1687)... >> (*) DirectFB/Input: Keyboard 0.9 (directfb.org) >> (!) Direct/Modules: Could not open module directory >> `/usr/lib/directfb-1.0-0/gfxdrivers'! >> --> No such file or directory >> (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org) >> (*) DirectFB/Core/WM: SaWMan 0.1 (directfb.org) >> >>>>>>> CALL sawman_call >>>>>>> >> <<<<< EXIT sawman_call - ERROR: no manager >> >>>>>>> CALL sawman_call >>>>>>> >> <<<<< EXIT sawman_call - ERROR: no manager >> >>>>>>> CALL sawman_call >>>>>>> >> <<<<< EXIT sawman_call - ERROR: no manager >> >>>>>>> CALL ISaWMan_Construct >>>>>>> >> <<<<< EXIT ISaWMan_Construct >> >>>>>>> CALL ISaWMan_CreateManager >>>>>>> >> >>>>> CALL sawman_register >> <<<<< EXIT sawman_register >> (*) SaWMan/TestMan: Process added (1684) [1]! >> <<<<< EXIT ISaWMan_CreateManager >> >> here the application just waits. Nothing happens on my screen. >> >> >> In session #2 I run "testrun": >> >> bash-2.05b# ./testrun Penguins >> (*) SaWMan/TestRun: Initializing... >> >> =======================| DirectFB 1.0.0 |======================= >> (c) 2001-2007 The DirectFB Organization (directfb.org) >> (c) 2000-2004 Convergence (integrated media) GmbH >> ------------------------------------------------------------ >> >> (*) DirectFB/Core: Single Application Core. (2007-09-07 11:18) >> (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 1690)... >> (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 1691)... >> (*) DirectFB/Input: Keyboard 0.9 (directfb.org) >> (!) Direct/Modules: Could not open module directory >> `/usr/lib/directfb-1.0-0/gfxdrivers'! >> --> No such file or directory >> (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org) >> (*) DirectFB/Core/WM: SaWMan 0.1 (directfb.org) >> >>>>>>> CALL sawman_call >>>>>>> >> <<<<< EXIT sawman_call - ERROR: no manager >> >>>>>>> CALL sawman_call >>>>>>> >> <<<<< EXIT sawman_call - ERROR: no manager >> >>>>>>> CALL sawman_call >>>>>>> >> <<<<< EXIT sawman_call - ERROR: no manager >> >>>>>>> CALL ISaWMan_Construct >>>>>>> >> <<<<< EXIT ISaWMan_Construct >> >>>>>>> CALL ISaWMan_Start >>>>>>> >> >>>>> CALL sawman_call >> <<<<< EXIT sawman_call - ERROR: no manager >> <<<<< EXIT ISaWMan_Start >> (#) DirectFBError [saw->Start( saw, ((argc > 1) && argv[1]) ? argv[1] : >> "Test Application", &pid )]: No (suitable) implementation found! >> (*) SaWMan/TestRun: Shutting down... >> >>>>>>> CALL sawman_call >>>>>>> >> <<<<< EXIT sawman_call - ERROR: no manager >> bash-2.05b# >> >> As you can see I have added some trace printouts to the sawman code and >> what I can see is that the check for presence of the manager fails in >> function sawman_call() in file sawman.c when I run "testrun". The >> "testman" process seems to successfully create a sawman manager though. >> How do the two processes communicate? Or am I totally messing things up >> here? >> >> I should also mention that I am not using the testman and testrun >> scripts in directory samples (because they try to start my compiler ??? >> which I don't have on the target). Instead I install and run the apps in >> directory samples/.libs instead. >> >> Any help would be greatly appreciated! >> >> Best regards, >> Lars Salomonsson >> >> _______________________________________________ >> directfb-users mailing list >> [email protected] >> http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users >> >> > > > > _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
