DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-id:content-transfer-encoding
	:mime-version; q=dns; s=default; b=O1XncGRrV3Mv924HIkTqFH4oXBLQn
	yJ3CBz2D+wu6S6y0rN7np9CVsDuT8uGd1ywjP5+FU7Ie7Kb5WX0KnSPo3svLluhD
	acul1lqf6+iesHM8M12yMG1BU9U3ksRN+L67PH2UE6Ibq6bbWO42OR6SuFe4Epaf
	O2epdVwSs/2Y7k=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Ken Brown <kbrown AT cornell DOT edu>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Supplying a patched package
Date: Mon, 29 Oct 2018 14:46:57 +0000
Message-ID: <65cf7307-3bf2-d8fe-6be9-889bdf60bf32@cornell.edu>
References: <03354D05-354F-4C65-9932-2D663EB32B5F AT lemma-one DOT com>
In-Reply-To: <03354D05-354F-4C65-9932-2D663EB32B5F@lemma-one.com>
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
received-spf: None (protection.outlook.com: cornell.edu does not designate permitted sender hosts)
Content-Type: text/plain; charset="utf-8"
Content-ID: <F376235FA0D3CB4C99E201ECB5DC1A28 AT namprd04 DOT prod DOT outlook DOT com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

On 10/28/2018 12:43 PM, Rob Arthan wrote:
> I have an application that is available for the main UN*X implementations
> and uses the OpenMotif library. It currently works fine on Cygwin using
> the motif-2.3.6-1 package. I am working on enhancing it to use Unicode
> and UTF-8 to display mathematical symbols and this has exposed a bug
> in OpenMotif. I have a patch for the bug and have successfully built
> the OpenMotif library as a DLL and tested it on Cygwin.
> 
> The bug has been reported but the turn-round time for a fix to OpenMotif
> is likely to be 6 or 12 months and I don’t how long it will take for it to
> get picked up on Cygwin (2.3.6 is 2 versions and 18 months behind the
> latest version). So my question is what is the best way to supply my fix to
> users on Cygwin in the interim.
> 
> Building the DLL seems a bit tricky, so I’d prefer users not to have to
> do that. If I supply the DLL, then the simplest thing seems to be just
> to include the DLL in a bin folder alongside the executable for my app.
> Is that a robust and portable solution? Will I need to build different DLLs
> for different architectures or can I safely assume that people running
> on a reasonably recent MS Windows installation will only want the x86_64 DLL?
> 
> Apologies if the answer should be obvious: I am a reasonably proficient
> UN*X programmer, but just a naive end-user feeling my way on MS
> Windows. Am I right in inferring from experiments that Cygwin and/or
> MS Windows looks for DLLs on the list of folders given $PATH and/or
> %PATH% list but has a look in the folder containing the executable that
> wants the DLL first?

Have you considered creating a Cygwin package for your app?  See

   https://cygwin.com/packages.html

for information about this.

As for OpenMotif, I suggest sending your patch to the cygwin-apps mailing list 
where the motif maintainer (Yaakov) might see it and update the package.  Or you 
could offer to take over as maintainer if Yaakov is too busy to update it and is 
willing to give it up.

Ken

--
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