From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Cc: alois.schloegl@gmail.com
Subject: Re: newcomer issues when packaging biosig,stimfit, etc.
Date: Sat, 8 Jan 2022 20:24:28 +0100 [thread overview]
Message-ID: <e72ab3da-75d1-f0eb-db64-5cc58b8b57df@gmail.com> (raw)
In-Reply-To: <44c5a1de-dbfe-625d-8ff8-049d8047277e@gmail.com>
On 08.01.2022 20:15, Marco Atzeri wrote:
> following on cygwin-apps
>
> On 08.01.2022 18:41, Marco Atzeri wrote:
>> 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
>>
>
> I looked on libb64, as it is not using autoconf/automake
> you can not use the default src_* but you need to define them.
>
> As the Makefile is building only static lib and has no install
> procedure I modified to build only shared and I used
> cygport for the installation.
> I also separated the test.
>
> See attached update cygport and patch.
>
as we have already base64
$ cygcheck -l coreutils | grep base64
/usr/bin/base64.exe
/usr/share/man/man1/base64.1.gz
I wonder if is it really useful.
Otherwise you need to change name to the binary
Regards
Marco
next prev parent reply other threads:[~2022-01-08 19:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99eff890-3d7f-7fa9-1f42-d8d611b92ded@gmail.com>
2022-01-08 17:41 ` Marco Atzeri
2022-01-08 19:15 ` Marco Atzeri
2022-01-08 19:24 ` Marco Atzeri [this message]
[not found] ` <a3f8e657-1e1d-c582-2a07-806c6c03be02@gmail.com>
2022-01-12 5:47 ` Marco Atzeri
2022-01-12 6:16 ` Brian Inglis
2022-01-12 22:59 ` [ITP] biosig [was: Re: newcomer issues when packaging biosig, stimfit, etc.] Alois Schlögl
2022-01-14 10:09 ` Marco Atzeri
2022-01-14 21:48 ` Alois Schlögl
2022-01-15 18:01 ` Marco Atzeri
2022-01-15 20:44 ` Achim Gratz
2022-01-17 21:44 ` Alois Schlögl
2022-01-18 5:32 ` Brian Inglis
2022-01-18 21:50 ` Alois Schlögl
2022-01-18 22:56 ` Brian Inglis
2022-01-19 3:51 ` Brian Inglis
2022-01-20 20:48 ` Alois Schlögl
2022-01-21 12:53 ` Jon Turney
2022-01-16 22:13 ` Alois Schlögl
2022-01-22 17:52 ` Marco Atzeri
2022-01-25 23:50 ` Alois Schlögl
2022-01-26 4:52 ` Marco Atzeri
2022-01-26 22:47 ` Marco Atzeri
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=e72ab3da-75d1-f0eb-db64-5cc58b8b57df@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=alois.schloegl@gmail.com \
--cc=cygwin-apps@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).