[haiku] Re: Compiling Haiku
- From: Stephan Aßmus <superstippi@xxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Thu, 17 Sep 2009 17:20:27 +0200
Ricardo Maraschini schrieb:
Hello people,
I'm having a great fun here looking for haiku source code and I have a
lot of questions regarding the compile process.
Let's assume that I change a device driver(for instance
intel_extreme/driver.cpp), so I got into intel_extreme directory and
run the "jam" command. As far as I see the compiled files stay under
an directory called "generated" in haiku source.
There's a command(or a parameter to jam) to apply all changed/compiled
binaries to haiku under /boot/system ?
I need to rebuild all system every time I change something?
Anybody can point me to a documentation where I can solve this doubts?
Is this the right list for these questions?
The way to test a binary when you compile it depends a bit on what it
is. For a graphics driver, you need to reboot the system, unfortunately.
The best turn around times for that is probably when you have two
computers, the one with the graphics card being booted over the network
with the other computer supplying the Haiku image and acting as
development machine. I don't know if that's an option for you. To learn
more about network (PXE) booting, I would recommend to google this,
since there have been mails and perhaps even articles describing the
process in detail.
If I had only one machine available, I would probably make links to the
driver binary in generated in the /boot/home/config/add-ons/... folder
(replicating the setup from /system, ie with the link to the driver
binary in drivers/dev/graphics). Then simply reboot to test. I know that
some Haiku components work as expected when you "overlay" or "shadow"
(or whatever you want to call it) an add-on of the same name in the user
hierarchy. Like if you have an add-on named "ffmpeg" in your
home/config/add-ons/media/plugins folder, it will take precedence over
the add-on with the same name in the system/add-ons/media/plugins
folder. But I don't know if that's the case for graphics or kernel
drivers in general at the moment. So you may have to remove the system
driver while you are testing and if something goes wrong, disable
user-add-ons from the boot menu, and use VESA mode to boot.
Hope this helps and best regards! Thanks for digging into Haiku and
don't hesitate to ask more questions! :-)
-Stephan
Other related posts:
