Explore >> Select a destination
|
You are here 
|
momi.ca | ||
| | | | |
nathanchance.dev
|
|
| | | | | As a Linux kernel developer, I will often need to build and boot new kernels to hunt down issues or test new functionality for regressions. While it is possible to manually install these kernels on machines, it is easiest to use the distribution's package manager, as the kernel does not need to be built on the machine it is being installed on. With .deb and .rpm-based systems, it is easy to build a kernel package within the kernel source itself, using the bindeb-pkg and binrpm-pkg targets respectively. However, for Arch Linux, my distribution of choice, that is not so simple. Furthermore, when doing certain types of development, such as bisecting an issue, it is more convenient to do all the building in an actual source tree, rather than one that is managed by the Arch Build System. The following process might not be the most efficient or optimal way to do this process (the Arch wiki has a whole article about doing a git bisect with a PKGBUILD) but it works for me :) | |
| | | | |
www.grendelman.net
|
|
| | | | | ||
| | | | |
blog.nillsf.com
|
|
| | | | | ||
| | | | |
wittchen.io
|
|
| | | Introduction Some time ago, Ive written an article about Test coverage report for Android application. It got some interest (many comments below article and many visits according to Google Analytics), so I decided to refresh this topic. Previously, Ive written instrumentation unit tests, which needed to be executed on a real device or an emulator. Its a good approach when you want to test functionalities strongly connected with the device. E. | ||
