/haiku/docs/user/interface/ |
H A D | _layout_intro.dox | 57 Before we can add anything to our layout, we must attach it to something, 62 Now that we've got our BGroupLayout in place, we can start adding things 70 a single BView. However, if we want to ensure that our BStringView is always 80 Now our BStringView will always be right in the middle of the space 90 Because we want our BMenuBar to appear at the very top of the window, we 92 We also use BTwoDimensionalLayout::SetInsets() to make sure that our 94 space between our BMenuBar and our BStringView, but \c group's spacing has 98 Now that we've put our BGroupLayout to good use, we can rest easy, assured 104 example, that we wanted to add a grid of BButtons under our BStringView. 112 Because we want a bit of breathing room between our buttons, we'll leave [all …]
|
H A D | LayoutBuilder.dox | 39 At this point our stack just contains a single builder, it looks like this: 58 Now our stack looks like this:
|
/haiku/docs/develop/kernel/boot/ |
H A D | Debugging_Bootloaders_GEF.rst | 48 our Raspberry Pi 2 dtb. If you don’t have a dtb for the machine 63 Open gdb with our symbols. 66 First we run gdb pointed at our boot loader. We use the native ELF 67 binary as that seems to give gdb/gef the most accurate knowledge of our 95 debugging process. All of our bootloaders start in a ``start_gen``
|
/haiku/src/add-ons/kernel/network/protocols/ipv4/ |
H A D | ipv4_address.cpp | 482 const sockaddr_in *our = (const sockaddr_in *)ourAddress; in ipv4_hash_address_pair() local 485 bool haveOur = our && our->sin_len != 0; in ipv4_hash_address_pair() 489 ((haveOur ? our->sin_port : 0) in ipv4_hash_address_pair() 491 ^ (haveOur ? our->sin_addr.s_addr : 0) in ipv4_hash_address_pair()
|
/haiku/src/kits/screensaver/ |
H A D | Jamfile | 4 # we also need our headers when build for BeOS
|
/haiku/src/data/mime_db/image/ |
H A D | x-pcx | 6 // version 5, encoding 1 is all our translator currently supports
|
/haiku/src/libs/glut/ |
H A D | LICENSE.txt | 25 > At the moment, we have the unmodified GLUT source code in our tree to 27 > BeOS R5). However, our developers feel anxious distributing any
|
/haiku/src/bin/screen_blanker/ |
H A D | Jamfile | 4 # we also need our headers when build for BeOS
|
/haiku/src/tests/add-ons/translators/ |
H A D | Jamfile | 7 # Let Jam know where to find some of our source files
|
/haiku/src/preferences/screensaver/ |
H A D | Jamfile | 4 # we also need our headers when build for BeOS
|
/haiku/docs/develop/kernel/arch/arm/ |
H A D | rpi2.rst | 64 - Build our loader using ``jam -q haiku_loader_linux.ub`` 65 - Build our initial ram disk using ``jam -q haiku-floppyboot.tgz.ub``
|
H A D | rpi1.rst | 61 - Build our loader using ``jam -q haiku_loader_linux.ub`` 62 - Build our initial ram disk using ``jam -q haiku-floppyboot.tgz.ub``
|
/haiku/docs/develop/build/ |
H A D | jam.rst | 12 require us to generate versions of our bootloader that run on a wide variety of environments 24 control on the compilation process for our needs. 42 Haiku provides its own variant, as we needed to extend Jam in various ways to make it work for our 126 system) and the fact that a large part of the build is made with our own compiler and libraries, 139 so simple, and a lot of these rules need to be redefined, in particular to handle our setup
|
H A D | ide.rst | 8 tools such as clangd_ in live analyzing our source code.
|
/haiku/ |
H A D | .gitignore | 1 # Files generated by our buildsystem or reserved for local changes by the user
|
H A D | ReadMe.md | 44 one of our web-based source code browsers: 60 ### Contributing to our infrastructure
|
/haiku/src/kits/ |
H A D | Jamfile | 12 # -- needed until the app server runs on our kernel. 22 # Build our libbe.so
|
/haiku/3rdparty/kallisti5/ |
H A D | howto-iommu-old.md | 61 the matching BUS ID and we get our PCI ID: 67 Now that we have our target PCI ID (`1002:68f9`), we can bind this device to 87 Now we reboot and cross our fingers.
|
/haiku/3rdparty/pulkomandy/ |
H A D | haiku_arm_qemu_gdb | 24 # Set a breakpoint at our entry point, so we can watch things roll after the
|
/haiku/src/kits/app/ |
H A D | Jamfile | 12 # -- needed until the app server runs on our kernel.
|
/haiku/docs/develop/kernel/vm/ |
H A D | swap_file_support.rst | 24 therefore our swap system implementation is borrowed from FreeBSD. 66 The swap system also manages allocation/deallocation of swap space. In our 81 used. I have ported the radix bitmap structure to Haiku, so our swap system
|
/haiku/src/tests/kits/support/ |
H A D | Jamfile | 5 # Let Jam know where to find some of our source files
|
/haiku/src/bin/debug/strace/ |
H A D | Jamfile | 46 # Whatever our compiler (gcc 2.95.3) thinks it is doing when compiling the
|
/haiku/data/boot/efi/keys/ |
H A D | README.md | 11 To trust Haiku's EFI bootloader, you'll need to append our DB key to your BIOS's
|
/haiku/docs/develop/busses/agp_gart/ |
H A D | ReadMe.rst | 19 far. Since our videodrivers are only doing modesetting, they do not need
|