how to build blktap from sources?

borzel

hui ... will try that ...

borzel

@nraynaud said in how to build blktap from sources?:

repo-7.4

whats inside this directory? content of the XenServer 7.4 source iso?

borzel

ahh... maybe this? https://updates.xcp-ng.org/7/dev/builddeps/x86_64/Packages/

borzel

ok, got it working! my own blktap is running Thanks for your help!

nraynaud

@borzel sorry, I missed your question, glad you got it working.

what changes are you making?

borzel

First just playing around to get knowledge of this, maybe I find some usefull things. Don't know exactly, but I want to understand a bit more what I'm using here.

Can sometimes be handy to know such things. Everytime I learned something I was using it later at work or privat

olivierlambert

Good idea We are glad to have more potential contributors on board. More the XCP-ng knowledge is spread, better the community!

r1

@borzel Congratulations! And I can relate to the feeling

stormi

There's now a new and reproducible way to build blktap in a clean environment:

https://github.com/xcp-ng/xcp-ng-build-env

I will not copy the readme here, but basically, you can do something like that:

Preparation

# create the build image, target current dev branch of XCP-ng (which is the future 7.5)
# There's no support for 7.4 because of different repository structure and missing devel packages
# You need to do it just once, though doing it from time to time won't hurt.
./build.sh dev

# create an useful alias for later. You should probably add it to you .bashrc so that it stays
# The --rm part is not mandatory but I find it useful to keep docker's disk usage low.
alias xcp-build="$(pwd)/run.py --rm"

Build

Here I'll show you how to build from our new git repositories. Not all packages are present there, but blktap is and this is a good occasion to make you become accustomed to using them since that's where we'll commit patches and also experimental stuff.

# from the directory of your choice...
git clone https://github.com/xcp-ng-rpms/blktap.git # or a forked version if you intend to send pull requests
cd blktap
# ... here make changes... or not...
# use our shiny new alias to build it
xcp-build --build-local . # or simply 'xcp-build -l .'

The resulting built RPMs will be in the SRPMS and RPMS subdirectories of your git working directory.

Just tested with blktap. If it fails at building another package, open a separate thread and I'll try to fix it.

Bonus: build with experimental changes applied

Our blktap package can be built with an experimental patch for better ZFS support. Build it this way:

xcp-build --build-local . --define 'xcp_ng_section extras'

borzel

~~If someone fails to build, maybe the git-lfs in not properly initialised. To fetch the lfs-files after git clone you can do a git lfs fetch.~~
weird ... after the second time installing git-lfs and again cloning the repo, it worked...