Hi Guys, I'm new to meego and working on the policy framework...
I want to debug *resource-test.c* in *maemo-multimedia-libresource* . I'm using a virtual box. How do I go about doing it? I currently have following questions in mind: 1. I used the netbook ISO and installed it. But after installing I simply get a blank Meego wallpaper and nothing else. So which is the best image that would work with virtual box? 2. After I get into the meego shell , I obviously would not be able to see resource-test.c in the file system. So how do I go about copying it to the virtual box image, creating a makefile ( is there a special format ? ) and debuging it with gdb? Regards, Nimesh ________________________________ From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Tuukka Mäkinen Sent: Thursday, September 22, 2011 6:40 PM To: meego-dev@meego.com Subject: Re: [MeeGo-dev] Audio policy -- Adding one's own resource class On 09/22/11 15:44, nimesh.chanch...@accenture.com<mailto:nimesh.chanch...@accenture.com> wrote: Hi guys, I want to add my own resource class and alter the priorities of the existing ones. Can anyone suggest a starting point or a pointer? Regards, Nimesh Policy settings are in the package policy-settings-basic-{platform} package. That package contains policy rules (in prolog) and some settings files. Looking into settings package for N900 resource classes appear to be defined in resource_classes.pl. It would be interesting to see what could be done with policy framework but unfortunately I haven't quite grasped prolog. Tuukka Mäkinen ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines