Thanks Geoffroy and Venkat for sharing the knowledge. It solved the problem for me. Thanks again !!
On Tue, Jan 29, 2013 at 11:17 AM, <[email protected]> wrote: > Hi, > > > > > > unless until you run the respective package on the target board, you can't > see the printf messages or debug message. Here are the steps. > > > > - Add printf in source code > - Compile(Cross on host) > - Generate the RPM > - extract the RPM > - Install it on target rootfs > - then run respective package > > During build time you cant see any printf messages > > > > Thanks, > > Venkat Raju. > > > > -----Original Message----- > From: "embedded linux" <[email protected]> > Sent: Tuesday, January 29, 2013 10:55am > To: [email protected] > Cc: [email protected] > Subject: Re: [Tizen General] Customize and build tizen source packages > > Thanks Venkat for your response. > I am using the following command: > *sudo gbs build -A armv7l -R > http://download.tizen.org/releases/daily/2.0alpha/common/latest/repos/tizen-base/armv7l/packages/-R > http://download.tizen.org/releases/daily/2.0alpha/common/latest/repos/tizen-main/armv7l/packages/--debug > --include-all > * > For now, I have just added a printf statement in the alsa-scenario-0.2 > package and see if I am able to see the printf on the console during the > build which is not happening. I have attached the log with debug messges. > Please let me know if I have to add anything. > > Thanks > > On Tue, Jan 29, 2013 at 10:29 AM, <[email protected]> wrote: > >> Hi, >> >> >> >> Please check the other debug messages in the same source code, use the >> same convention as other debug messages and also enable android logger >> driver form the kernel and use dlogutils(Its the default log tool that >> Tizen uses). >> >> >> >> Thanks, >> >> Venkat Raju. >> >> >> >> >> -----Original Message----- >> From: "embedded linux" <[email protected]> >> Sent: Monday, January 28, 2013 5:20pm >> To: [email protected] >> Cc: [email protected] >> Subject: Re: [Tizen General] Customize and build tizen source packages >> >> Hi Venkat, >> Thanks for your quick response. I tried including --include-all, it says >> the uncommitted packages are included and in >> /GBS-ROOT/local/scratch.armv7l.0/home/abuild/rpmbuild/BUILD/ >> the new package with my printf is added but the printf statement is not >> showing up during compilation on console. >> >> Thanks >> >> On Mon, Jan 28, 2013 at 4:47 PM, <[email protected]> wrote: >> >>> Use --include-all while building it includes all uncommitted chragnes >>> and build it agia, >>> >>> >>> >>> Thanks, >>> >>> Venkat Raju. >>> >>> >>> >>> -----Original Message----- >>> From: "embedded linux" <[email protected]> >>> Sent: Monday, January 28, 2013 4:44pm >>> To: [email protected] >>> Subject: [Tizen General] Customize and build tizen source packages >>> >>> Hi all, >>> I want to customize the source packages from the original packages >>> downloaded from tizen source repo. As far as I understand from the logs, if >>> I want to compile the package such as alsa-scenario-0.2 which is in the >>> directory tizen/framework/multimedia/, when I do gbs build it copies the >>> source to /GBS-ROOT/local/scratch.armv7l.0/home/abuild/rpmbuild/BUILD/ and >>> compiles from there. >>> I made changes in alsa-scenario-0.2 source package just by adding printf >>> statement and see if that prints on the console when the code is compiled, >>> but it is not. Can anybody let me know if I have understood it right? >>> What is procedure to make changes in the source package and build it? >>> Please let me know. >>> >>> Thanks >>> >>
_______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
