DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:message-id:from:to:subject
	:content-type:date; q=dns; s=default; b=MDGunz8+nw5NwXrK4uwJ0FLe
	gAeq2a6pbUkvK+0wRcBwB4clZbucDh322sAnGN+UdQV2ZL6xLxu8sEQ5qPFRsesi
	+LTaspdsc/PwsnNRGAesWNtDGufcMf4YYRuSXLMjqxj3gUYpJjwVRX5tO0/Kplbf
	7wF/xJdGkXN2EFTaIDc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
Message-ID: <trinity-f19f7555-e19d-4d9b-98bd-3d2da10e8cf1-1506088812465@3c-app-gmx-bs21>
From: "Joachim Eibl" <Joachim.Eibl@gmx.de>
To: cygwin@cygwin.com
Subject: Does Cygwin setup modify dlls?
Content-Type: text/plain; charset=UTF-8
Date: Fri, 22 Sep 2017 16:00:12 +0200
Sensitivity: Normal

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