From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Cc: cygwin@cygwin.com
Subject: Re: newcomer issues when packaging biosig,stimfit, etc.
Date: Sat, 8 Jan 2022 18:41:07 +0100 [thread overview]
Message-ID: <dffefb30-94b4-392a-793d-1d723551f820@gmail.com> (raw)
In-Reply-To: <99eff890-3d7f-7fa9-1f42-d8d611b92ded@gmail.com>
On 08.01.2022 18:34, Alois Schlögl wrote:
> Dear Cygwin community,
>
Hi Alois,
> I intend to package Stimfit [1] and Biosig [2] (and perhaps
> libb64,libbiosig,sigviewer) for cygwin. The packages are already
> available in Debian, but when trying to package them for cygwin, I run
> into some difficulties.
> I read the documentation [3-5], but I got stuck, and I'd appreciate your
> help on this. Attached are my current versions of *.cygports and *.hint
> files
please subscribe to cygwin-apps.
The discussion about maintainership and packaging are handled there
>
> When trying to build them with cygport I run into these difficulties:
>
> $ cygport libb64.cygport all
> >>> Preparing libb64-1.2.1-1.x86_64
> >>> Unpacking source libb64-1.2.1.zip
> >>> Preparing working source directory
> >>> Compiling libb64-1.2.1-1.x86_64
> *** ERROR: Could not find configure.ac or configure.in
>
> libb64 does not require running configure, the Makefile is already
> available and a simple "make" command would do.
> How can I specifiy this in the libb64.cygport file ?
>
>
> "cygport biosig.cygport all"
> ....
> config.status: creating biosig4c++/tcl/Makefile
> config.status: creating config.h
> config.status: config.h is unchanged
> make: *** No rule to make target 'Makefile.in', needed by 'Makefile'.
> Stop.
> *** ERROR: make failed
>
> Makefile.in is in the sources, why do I see this error when trying to
> build it with cygport ?
>
> Attached are also stimfit.cygport and sigviewer.cygport, they require
> libbiosig, and are most likely incomplete. If you have suggestions to
> make it work, please let me know.
>
>
> Cheers,
> Alois
>
>
>
> [1] https://github.com/neurodroid/stimfit
> [2] http://biosig.sourceforge.net/
> [3] https://cygwin.com/packages.html
> [4] https://cygwin.com/packaging-contributors-guide.html
> [5] https://cygwin.com/packaging-hint-files.html
>
regards
Marco
prev parent reply other threads:[~2022-01-08 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 17:34 Alois Schlögl
2022-01-08 17:41 ` Marco Atzeri [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dffefb30-94b4-392a-793d-1d723551f820@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).