[haiku] Re: Willing to work for your project.(George)
- From: Stephan Aßmus <superstippi@xxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Fri, 25 Mar 2011 07:53:40 +0100
Hi,
Am 25.03.2011 07:00, schrieb George zhao:
The configure problem is solved and get the nightly version built, now
I guess it's good to go.
Struggling in setup the developing, debugging and testing environment
now, I got some help from IRC, hopefully could figure out a good way
to editing code, build image, load it up and do the test and
validation in the coming days.
Do you have any suggestion about it? Thanks!
Depending on what you are doing, different models of development have
better turn around times.
When developing a GUI app, or even a driver that can be dynamically
reloaded for each test run, developing directly in Haiku can give the
quickest turn around times. The development tools in Haiku are the Pe
editor, the command line, GDB, Kernel Debugging Land and printf or
syslog debug output. The PPP module might be such a situation, but
Philippe would know best from working on it recently.
Another possibility is to run Haiku in a VM. The build system supports
the "update" feature. It can be configured quite extensively. Suppose
you have a jam target "ppp", then you can update the Haiku image with
"jam @your_vm_profile update ppp". This will be very quick. "ppp" can be
a pseudo target and update multiple files on the image. Then you just
have to live with the time it takes to reboot Haiku in the VM.
In any case, going back to the first scenario, when you develop a driver
in Haiku, and you exchange the binary of the driver at its install
location, the kernel will know it has updated. When your test
application (re)opens the driver, it will use the new version.
If any of this was confusing, don't hesitate to ask for more details... :-)
Best regards,
-Stephan
Other related posts:
