From: "Joachim Eibl" <Joachim.Eibl@gmx.de>
To: cygwin@cygwin.com
Subject: Does Cygwin setup modify dlls?
Date: Fri, 22 Sep 2017 14:00:00 -0000 [thread overview]
Message-ID: <trinity-f19f7555-e19d-4d9b-98bd-3d2da10e8cf1-1506088812465@3c-app-gmx-bs21> (raw)
Hi,
In our project we like the Cygwin-Setup tool so much that we use it for our own files too.
Adding our archives to our setup.ini was easy enough and almost everything worked as expected.
But then a certain tool didn't work and we found that dll-files that were unpacked by the Cygwin-installer didn't match the files in the archive.
The problem seems to be dll-specific. Other filetypes are not modified.
When unpacking using normal Cygwin-tools (tar xf ...) all files were correct. So somehow the installation via Cygwin modifies them.
Is this known behaviour? Is this intentional? Can it be turned off? (Is there some postprocessing like "strip" etc?)
Or do you think we have another kind of problem, that is not related to Cygwin?
Our Cygwin-setup-version is 2.877, x86_64, running on Windows 10 or Windows 7.
Best regards,
Joachim
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2017-09-22 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 14:00 Joachim Eibl [this message]
2017-09-22 14:11 ` Eliot Moss
2017-09-22 14:46 ` Marco Atzeri
[not found] ` <trinity-4204847c-6bba-4606-b43c-8b376b96a945-1506094235587@3c-app-gmx-bs22>
2017-09-22 15:31 ` Joachim Eibl
2017-09-22 16:49 ` Marco Atzeri
2017-09-27 4:50 ` Andrey Repin
2017-09-27 10:04 ` Joachim Eibl
2017-09-22 15:49 ` Eliot Moss
2017-09-23 19:53 ` Achim Gratz
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=trinity-f19f7555-e19d-4d9b-98bd-3d2da10e8cf1-1506088812465@3c-app-gmx-bs21 \
--to=joachim.eibl@gmx.de \
--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).