Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Prepare build environment and build package

 

NOTE:

Please use user 'root' for userland build,
	because we have to update directory tree and files to use correct permissions
	and it is possible now only by user 'root'
update existing packages:
apt-get update
install packages:
apt-get install \
	gnu-make \
	build-essential

for clone/access to repo 'dilos-userland-git' you need to have account on bitbucket and ask to provide you access by info: http://www.dilos.org/conact-me

clone repo:
git clone git@bitbucket.org:dilos/dilos-userland-git.git
go to components directory:
cd dilos-userland-git/components
install additional packages for build environment:
gmake debprep
gmake setup
you are ready to build your package from userland, for example: apt
cd <dilos-userland-git>/components/apt
gmake JOBS=4 deb

( where JOBS - how much parallel build processes you want to use )

You can find your package(s) at: <dilos-userland-git>/i386/debs

How to create new package

create package directory and copy Makefile from another package

update Makefile with build flags (CONFIGURE_OPTIONS)

build package by:
gmake JOBS=4 install
create sample manifest:
gmake sample-manifest

you can find generated manifest at: build/manifest-i386-generated.p5m

move manifest to the root component directory and reame it to another name

example:
mv build/manifest-i386-generated.p5m mycomponent.p5m

update manifest with correct info. If you need more then one package you have to split one manifest to some others. For example take a look another components

build package(s):
gmake JOBS=4 deb

if you want build packages in your component root directory you can add flag WS_DEBS:

example:
gmake JOBS=4 WS_DEBS=`pwd` deb

as result you can find package at your component directory and be able to install it by 'dpkg -i <your package.deb>'

For more information about environment variables or build flags you can take a look <dilos-userland-review>/make-rules/deb.mk

 

 

 

 

  • No labels