Re: generic C++ code for uniform b-spline processing

[Andreas Tille <tille@debian.org>]

Hi Kay,

please permit that I continue this conversation in public where it
started.  I'm sorry to admit that I have no time for private teaching
and on one hand public discussion provides better input from different
people on the other hand your learning process is archived for later
reference that might help others.

On Thu, Jun 22, 2017 at 07:17:57PM +0200, Kay F. Jahnke wrote:
> Okay, I'm back online. I'm trying to go through the process described in
> 
> http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
> 
> But I'm not really getting anywhere.

I guess this is probably not the best first reading.  I'd recommend

   https://www.debian.org/doc/manuals/maint-guide/

   https://www.debian.org/doc/manuals/developers-reference/

as the first step rather than gbp manual.

> My intended package is a header-only
> C++ library plus a few examples, there is nothing to 'build', and somehow I
> can't seem to make gbp to understand that all I want to do is provide a few
> sources and a some collateral files, have them put in usr/... and specify a
> few dependencies on other packages, which provide headers I include.

I'd like to repeat as a helpful example

    apt-get source cimg

the debian/ dir should possibly answer all your questions.
 
> What I can do though is build a simple package with dpkg-deb, which does all
> I want it to do. I have a control file in vspline/DEBIAN/control:

Please do NOT create DEBIAN/control manually.  The developer should just
edit files in debian/ (lowercase!).
 
> When I issue 'dpkg-deb --build vspline' I get the .deb package.

I would not recommend to use dpkg-deb but rather wrappers like debuild or
pdebuild - please read in the linked docs about these.

I just CC debian-science list for completion with the remaining text
of yours.  May be others might like to comment here but I think what
I wrote should bring you back on track.

Kind regards

      Andreas.

 
> So now I'd like to move on to using gbp.
> 
> The directory 'vspline' contains a git repository with two branches. One
> branch is master, which is a straight pull of the master branch of my
> bitbucket git repo containing the sources, with all the headers at the top
> level, so that cloning the repo to /usr/local/lib produces a directory
> vspline there with all the relevant headers. The other branch is
> 'debian/sid' and has the headers and collateral files moved to
> vspline/usr/... so that they end up in /usr/include/... etc.
> 
> I think this setup is pretty close to what I need, but I can't get from here
> to a state that gbp accepts - I renamed DEBIAN to debian, added a changelog
> file and, since I didn't know what else to do, an empty rules file, and
> issued
> 
> gbp buildpackage --git-ignore-new --git-pristine-tar
> --git-pristine-tar-commit --git-upstream-tag='%(version)s'
> 
> getting this output:
> 
> dpkg-buildpackage: Information: Quellpaket vspline
> dpkg-buildpackage: Information: Quellversion 0:0.1-1ubuntu1~1.gbp37a0b1
> dpkg-buildpackage: Information: Quelldistribution UNRELEASED
> dpkg-buildpackage: Information: Quelle geändert durch Kay F. Jahnke
> <kfj@laxmi>
>  dpkg-source -i -I --before-build vspline
> dpkg-buildpackage: Information: Host-Architektur amd64
> dpkg-source: Fehler: Syntaxfehler in vspline/debian/control in Zeile 27: im
> ersten Block fehlt ein Feld »Source«
> dpkg-buildpackage: Fehler: Fehler-Exitstatus von dpkg-source -i -I
> --before-build vspline war 255
> debuild: fatal error at line 1376:
> dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed
> gbp:error: 'debuild -i -I' failed: it exited with 29
> 
> If I add Source:vspline as a separate Paragraph, I get a lot of other
> errors.
> 
> Maybe you can suggest what I should try to get gbp to accept my code? Or am
> I barking up the wrong tree?
> 
> with regards
> Kay
> 
> 
> 
> 
> 
> 
> 

-- 
http://fam-tille.de