mirror of
https://review.haiku-os.org/haiku
synced 2025-01-20 21:41:28 +01:00
afbd081a6f
* The global BPathMonitor looper is now always used, no more optional looper and no more BApplication looper usage. This way we know how the looper behaves and PathHandler::Quit() can be synchronous. In the end, the bug I was observing was not caused by the previous asynchronous node monitor stopping, but this should be safer anyways. When BPathMonitor::StopWatching() returns, you have really stopped watching and not some time later. * Introduced "FileEntry" which is an entry_ref plus node id. This is now used instead of the node_ref for the "watched files set". The whole point is to really be able to add the "path" field to the B_PATH_MONITOR message. Previously, the initial path that was passed to StartWatching() was added, regardless if the message was for an entry somewhere down the hierarchy when watching recursively. The downside of the new method is that it uses a lot more RAM per entry. Another option would be to store the node id of the parent directory and iterate the directory always when in need to construct the path. * Watching a folder recursively now really adds all the existing subfolders as well as all the files if not watching for folders only. The tests for the old implementation only tested what happens when the watched folder was newly created and then subfolders were created. Those where already added by the code. Now it also adds the subfolders of folder that appear in a watched folder. TODO: Remove folders and files recursively when they dissappear. More testing for B_ENTRY_MOVED. Optimizations are possible when some information is retrieved twice. I am also planning to add a way for the BPathMonitor user to filter the automatically watched files/folders in B_WATCH_RECURSIVELY mode. I grepped the entire Haiku tree for usage of BPathMonitor. Only net_server and Mail were using it, but both in a way that is not affected by these changes. Anyways, TextSearch works more reliable now, even for entries in subfolders. Feedback very welcome! :-) git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@26936 a95241bf-73f2-0310-859d-f6bbb57e9c96
Building on BeOS ================ For building on BeOS you need the development tools from: http://haiku-os.org/downloads Please always use the most recent versions. They are required to build Haiku. Building on a non-BeOS platform =============================== Please read the file 'ReadMe.cross-compile' before continuing. It describes how to build the cross-compilation tools and configure the build system for building Haiku. After following the instructions you can directly continue with the section Building. Configuring on BeOS =================== Open a Terminal and change to your Haiku trunk folder. To configure the build you can run configure like this: ./configure --target=TARGET Where "TARGET" is the target platform that the compiled code should run on: * haiku (default) * r5 * bone * dano (also for Zeta) The configure script generates a file named "BuildConfig" in the "build" directory. As long as configure is not modified (!), there is no need to call it again. That is for re-building you only need to invoke jam (see below). If you don't update the source tree very frequently, you may want to execute 'configure' after each update just to be on the safe side. Building ======== Haiku can be built in either of two ways, as disk image file (e.g. for use with emulators) or as installation in a directory. Image File ---------- jam -q haiku-image This generates an image file named 'haiku.image' in your output directory under 'generated/'. VMware Image File ----------------- jam -q haiku-vmware-image This generates an image file named 'haiku.vmdk' in your output directory under 'generated/'. Directory Installation ---------------------- HAIKU_INSTALL_DIR=/Haiku jam -q install-haiku Installs all Haiku components into the volume mounted at "/Haiku" and automatically marks it as bootable. To create a partition in the first place use DriveSetup and initialize it to BFS. Note that installing Haiku in a directory only works as expected under BeOS, but it is not yet supported under Linux and other non-BeOS platforms. Bootable CD-ROM Image --------------------- * UNSUPPORTED yet * This _requires_ having the mkisofs tool installed. On Debian GNU/Linux for example you can install it with: apt-get install mkisofs On BeOS you can get it from http://bebits.com/app/3964 along with cdrecord. Creating a bootable CD requires burning 2 tracks on a single CD. The first track is an El-Torito bootable ISO file-system containing a boot floppy image, and is created with: jam -q haiku-boot-cd This generates an image file named 'haiku-boot-cd.iso' in your output directory under 'generated/'. The second track is the raw BFS image 'haiku.image' in 'generated/' created with: jam -q haiku-image Under Unix/Linux, and BeOS you can use cdrecord to create a CD with: cdrecord dev=x,y,z -v -eject -dao -data generated/haiku-boot-cd.iso generated/haiku.image Here x,y,z is the device number as found with cdrecord -scanbus, it can also be a device path on Linux. Windows users will find '3rdparty/nero/haiku-cd.cue' useful. Since the CD has two tracks it is not easy to test it from an emulator. Instead it is simpler to use the 'haiku.image' as CD image and the floppy image 'haiku-boot-floppy.image' to boot from it. For Qemu: qemu -cdrom generated/haiku.image -fda generated/haiku-boot-floppy.image -boot a Building Components ------------------- If you don't want to build the complete Haiku, but only a certain app/driver/etc. you can specify it as argument to jam, e.g.: jam Pulse Alternatively, you can 'cd' to the directory of the component you want to build and run 'jam' from there. You can also force rebuilding of a component by using the "-a" parameter: jam -a Pulse Running ======= Generally there are two ways of running Haiku. On real hardware using a partition and on emulated hardware using an emulator like Bochs or QEmu. On Real Hardware ---------------- If you have installed Haiku to its own partition you can include this partition in your bootmanager and try to boot Haiku like any other OS you have installed. To include a new partition in the BeOS bootmanager run this in a Terminal: bootman On Emulated Hardware -------------------- For emulated hardware you should build disk image (see above). How to setup this image depends on your emulater. A tutorial for Bochs on BeOS is below. If you use QEmu, you can usually just provide the path to the image as command line argument to the "qemu" executable. Bochs ----- Version 2.2 of Bochs for BeOS (BeBochs) can be downloaded from BeBits: http://www.bebits.com/app/3324 The package installs to: /boot/apps/BeBochs2.2 You have to set up a configuration for Bochs. You should edit the ".bochsrc" to include the following: ata0-master: type=disk, path="/path/to/haiku.image", cylinders=122, heads=16, spt=63 boot: disk Now you can start Bochs: $ cd /boot/apps/BeBochs2.2 $ ./bochs Answer with RETURN and with some patience you will see Haiku booting. If booting into the graphical evironment fails you can try to hit "space" at the very beginning of the boot process. The Haiku bootloader should then come up and you can select some safe mode options. Docbook documentation ===================== Our documentation can be found in 'src/documentation/'. You can build it by running 'jam' in that folder. The results will be stored in the 'generated/' folder.