From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: cygport does not automatically generate dependencies
Date: Fri, 12 Jun 2020 09:03:13 +0200 [thread overview]
Message-ID: <87pna4epfy.fsf@Otto.invalid> (raw)
In-Reply-To: <f3100486-6674-1f07-dc64-4aded81ce649@users.sourceforge.net> (DRC via Cygwin-apps's message of "Fri, 12 Jun 2020 00:44:18 -0500")
DRC via Cygwin-apps writes:
> I am attempting to create a new Cygwin package for my open source
> software (VirtualGL) using cygport. The package is generated correctly,
> but the "requires" field in the auto-generated hint is empty. The
> documentation for cygport implies that it should automatically generate
> package dependencies.
That only works when you don't cross-compile and you didn't say whether
you are or not.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2020-06-12 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 5:44 DRC
2020-06-12 7:03 ` ASSI [this message]
2020-06-12 9:29 ` Marco Atzeri
2020-06-12 15:06 ` DRC
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=87pna4epfy.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--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).