[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Libary Packaging



2009/5/29 Yonah Brendon Franklin <yonah@gmx.net>:
> Hi,
> i still have problems to understand how to build libraries.
>
> why do i have only directories and no libfiles?
>
> where can i find this?
>
> yonah
>

try building the software without debian/ dir at all. (as if you are
trying to compile something as a direct upstream users) this will give
you good idea about the upstream build-system.

Then set the correct configure/compile/install flags such that the
software is compiled and linked with prefix /usr/ but set the
destanation directory for the install target to debian/tmp/

After you think you have done this correctly try running

./debian/rules build

this should build everything that needs building

after that you can try

./debian/rules install (if you create such target)

or you should be able to run

./debian/rules binary

this step should install everything what needs to be install into debian/tmp

if you see not enough files in debian/tmp then probably some of your
configure flags were wrong.

If you see eveything what's needed in debian/tmp then move onto next step.

dh_install* commands do the dirty work of sorting out what goes into
which package. So you need to provide correct lists of files you want
to end up in which package for dh_install(1) you create
debian/libfoo1.install and list all run-time required files; then
you'll probably also need debian/libfoo-dev.install and you'll put
header's there (so and you have one of those files for each package in
the debian/control) based on those files dh_install sorts stuff into
packages which are located in debian/package_name check those folders
after you have run ./debian/rules binary to see what will end up in
them.

-- 
With best regards


Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич


Reply to: