From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] xxhash 0.7.4-1
Date: Tue, 14 Jul 2020 06:42:15 +0200 [thread overview]
Message-ID: <877dv6oggo.fsf@Otto.invalid> (raw)
In-Reply-To: <CAJ1FpuMoyKT4=NRYw0OaRc4SKkdacdpO-O-RQ=3ATL7DukskDA@mail.gmail.com> (Doug Henderson via Cygwin-apps's message of "Mon, 13 Jul 2020 16:09:34 -0600")
Doug Henderson via Cygwin-apps writes:
> I have some issues to resolve.
Yes, hand-written Makefiles that change constantly. X-(
> The install places files into the /usr/local tree instead of the /usr
> tree. Usually I would just do "PREFIX=/ make", but that does not work,
> so I'm not sure how to do this from the cygport file.
You're missing an export in front of setting that variable, I'd think.
> How do I change the name of the shared library to something like
> cygxxhash.0.dll?
By patching the Makefile, just like you need to do for all the other
stuff from the same author. You can have a look at the zstd packages.
> Do I need the libxxhash.a file?
No, the static library shouldn't be packaged.
> I think I should split the package into devel and non-dev packages.
Yes please.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2020-07-14 4:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 22:09 Doug Henderson
2020-07-14 4:42 ` ASSI [this message]
2020-07-14 16:29 ` ASSI
2020-07-14 19:51 ` Doug Henderson
2020-07-14 21:57 ` Ben RUBSON
2020-08-02 10:41 ` Ben RUBSON
2020-08-03 3:36 ` Doug Henderson
2020-08-03 5:58 ` Marco Atzeri
2020-08-03 16:08 ` Marco Atzeri
2020-08-25 15:46 ` Ben RUBSON
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=877dv6oggo.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).