DR1000 Building Hello World 4.0 - Page 3

rvs · 03-21-2011, 04:30 PM

Trying it out right now on the qemu

rvs · 03-21-2011, 05:28 PM

Can you explain how the logging works (LOGPRINTF and WARNPRINTF)? I can't find the location of these logs.

Thanks

Mackx · 03-22-2011, 03:59 AM

Hi rvs,

Every component has a files called log.h (or something simular) to control the logging of LOGPRINTF, WARNPRINTF and ERRORPRINTF. Default only WARN and ERROR are enabled. The output (default) goes to stderr.
To see the output on the emulator, you can press Ctrl-Alt-3. Pressing Ctrl-Alt-1 brings you back to the UI again.

rvs · 03-22-2011, 12:02 PM

Thanks Marcel, very useful information.

Do you develop using Anjuta? I'm guessing it's probably easier that way to quickly test small changes and turn logging on/off, but I still need to figure out how to import the Hackx source code into a (new) Anjuta project.

Mackx · 03-22-2011, 02:21 PM

Quote:

Originally Posted by rvs

Thanks Marcel, very useful information.

Do you develop using Anjuta? I'm guessing it's probably easier that way to quickly test small changes and turn logging on/off, but I still need to figure out how to import the Hackx source code into a (new) Anjuta project.

I use all different kinds of editors on linux and windows to change the code. But for most of the components of MackxPatch I use Anjuta projects. However I do not build using Anjuta, I am used to embedded software and thus also to compiling from command-line.
I use different Anjuta projects for every firmware component (ctb, popupmenu, sysd, etc). One of them I use to start qemu. For each component I also have a separate shell, to execute the make (with correct parameters) and copy the build executable to the qemu (using scp). I have 3 desktops/workspaces, left for the command shells, middle for the Anjuta projects and right for the qemu and a shell that is logged into the qemu (ssh qemu, just press enter for password).
For the commands to type I have a 'que-card', see attached file.
'Creating' an Anjuta project is very easy, copy the one from helloworld to the 'root' of one of the firmware components, rename it and start it.

Hope this helps.
Marcel.

rvs · 03-22-2011, 02:36 PM

Thanks, it's both helpful and interesting

Iñigo · 03-23-2011, 06:56 PM

Quote:

Originally Posted by Mackx

I use all different kinds of editors on linux and windows to change the code. But for most of the components of MackxPatch I use Anjuta projects. However I do not build using Anjuta, I am used to embedded software and thus also to compiling from command-line.
I use different Anjuta projects for every firmware component (ctb, popupmenu, sysd, etc). One of them I use to start qemu. For each component I also have a separate shell, to execute the make (with correct parameters) and copy the build executable to the qemu (using scp). I have 3 desktops/workspaces, left for the command shells, middle for the Anjuta projects and right for the qemu and a shell that is logged into the qemu (ssh qemu, just press enter for password).
For the commands to type I have a 'que-card', see attached file.
'Creating' an Anjuta project is very easy, copy the one from helloworld to the 'root' of one of the firmware components, rename it and start it.

Hope this helps.
Marcel.

Interesting.

My DR development environment: a VirtualBox linux virtual machine, with 4 virtual desktops:
1. qemu, a gnome-terminal with 3 tabs (mainly for scp and qemu shell), and a second gnome-terminal with many tabs (for compiling, light editing, copying/moving files and a shared directory from my real desktop)
2. emacs
3. firefox, with some help html files. Btw, when hacking DR firnware doxygen generated files are quite useful
4. evince, a pdf reader

EDIT: I didn't mention I don't use anjuta at all... it doesn't give anything emacs + shell couldn't offer

Iñigo

rvs · 03-24-2011, 10:43 AM

Thanks Iñigo,

I haven't heard of doxygen before. What do you use it for?

Mackx · 03-24-2011, 11:11 AM

Quote:

Originally Posted by rvs

I haven't heard of doxygen before. What do you use it for?

See here: http://www.stack.nl/~dimitri/doxygen/

Iñigo · 03-24-2011, 11:16 AM

Quote:

Originally Posted by Mackx

See here: http://www.stack.nl/~dimitri/doxygen/

and for an example of its use: https://inigo.katxi.org/ereader/dr800-sources/ and click on "Directories" link.

Iñigo

rvs · 03-24-2011, 11:24 AM

Very interesting, thanks! It seems quite extensive. I'll try it out (in due time).

Iñigo · 03-24-2011, 12:14 PM

Quote:

Originally Posted by rvs

Very interesting, thanks! It seems quite extensive. I'll try it out (in due time).

It's very useful to study third party code.
Doxygen is a package which parses specially formated sources and generates this kind of documentation.

If you want it I can attach here my doxygen configuration in order to help you generate your own docs, as they are big enough to forbid publishing them.

Iñigo

rvs · 03-24-2011, 02:17 PM

Quote:

Originally Posted by Iñigo

If you want it I can attach here my doxygen configuration in order to help you generate your own docs, as they are big enough to forbid publishing them.

I would very much appreciate that!

Iñigo · 03-24-2011, 02:58 PM

Quote:

Originally Posted by rvs

I would very much appreciate that!

$ gzip -d attached_file.gz

There is also a graphical UI tool for doxygen named doxywizard , you can run it and load the provided config file to modify the output.

Iñigo

rvs · 03-24-2011, 03:07 PM

Thanks again.

I'll try out Doxywizard, too.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
DR800 Building ctb	dima_tr	iRex Developer's Corner	6	06-30-2010 04:47 AM
OOOFBTools for book building	BobC	Workshop	0	01-24-2010 01:53 PM
Having problems building calibre 0.15.4	angevin	Calibre	11	06-12-2009 07:54 PM
iLiad Building FLTK for the iLiad	hudson	iRex Developer's Corner	3	04-01-2007 12:33 PM

03-21-2011, 04:30 PM	#31
rvs Groupie Posts: 181 Karma: 364 Join Date: Oct 2009 Device: DR1000s, Hanlin V5	Trying it out right now on the qemu

03-21-2011, 05:28 PM	#32
rvs Groupie Posts: 181 Karma: 364 Join Date: Oct 2009 Device: DR1000s, Hanlin V5	Can you explain how the logging works (LOGPRINTF and WARNPRINTF)? I can't find the location of these logs. Thanks

03-22-2011, 03:59 AM	#33
Mackx Guru Posts: 999 Karma: 19985 Join Date: Dec 2008 Location: Netherlands Device: iRex DR1000S	Hi rvs, Every component has a files called log.h (or something simular) to control the logging of LOGPRINTF, WARNPRINTF and ERRORPRINTF. Default only WARN and ERROR are enabled. The output (default) goes to stderr. To see the output on the emulator, you can press Ctrl-Alt-3. Pressing Ctrl-Alt-1 brings you back to the UI again.

03-22-2011, 12:02 PM	#34
rvs Groupie Posts: 181 Karma: 364 Join Date: Oct 2009 Device: DR1000s, Hanlin V5	Thanks Marcel, very useful information. Do you develop using Anjuta? I'm guessing it's probably easier that way to quickly test small changes and turn logging on/off, but I still need to figure out how to import the Hackx source code into a (new) Anjuta project.

03-22-2011, 02:36 PM	#36
rvs Groupie Posts: 181 Karma: 364 Join Date: Oct 2009 Device: DR1000s, Hanlin V5	Thanks, it's both helpful and interesting

03-24-2011, 10:43 AM	#38
rvs Groupie Posts: 181 Karma: 364 Join Date: Oct 2009 Device: DR1000s, Hanlin V5	Thanks Iñigo, I haven't heard of doxygen before. What do you use it for?

03-24-2011, 11:24 AM	#41
rvs Groupie Posts: 181 Karma: 364 Join Date: Oct 2009 Device: DR1000s, Hanlin V5	Very interesting, thanks! It seems quite extensive. I'll try it out (in due time).

03-24-2011, 03:07 PM	#45
rvs Groupie Posts: 181 Karma: 364 Join Date: Oct 2009 Device: DR1000s, Hanlin V5	Thanks again. I'll try out Doxywizard, too.

Advert

Advert