X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=TkwQIRBGLzDMCTaRySu+zEvfW55T
	ts8/WqC4+56UJG1b5eSmUYmoOFf/+0uOMf7qT/7Ga64piEZDMdZZrdwjANZ0LRRB
	X2MgjhHMoAGBbQbKJnglDnGPeuohPWFDPX76O3QzWeNRqwpS1uLw63ROQWIs3XfO
	aOVVwfqB7ANnFIU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id
	:references:to; s=default; bh=3V5cw1tbPb+f/tFg9oKPEUZPE+I=; b=Tl
	IweENCzppIwWhAS6YUyIrEOT2taqx5Lo7D1BCR2CmNOgEE+yXU3S1j5wrE8T95w6
	ZfPxStZxtme7BeQclueBS2m+vOu6f2mbCPeM/KFmhEe8+oDa9uPEvNR8Q2MpjuLM
	pkBjwSOpMQiF76sbtLtCkAKFaQVSs99o0H5ZibSJM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=BAYES_05,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=supplying, Supplying, bother, picked
X-HELO: otter.birch.relay.mailchannels.net
X-Sender-Id: interserver|x-authuser|rda AT lemma-one DOT com
X-Sender-Id: interserver|x-authuser|rda AT lemma-one DOT com
X-MC-Relay: Neutral
X-MailChannels-SenderId: interserver|x-authuser|rda AT lemma-one DOT com
X-MailChannels-Auth-Id: interserver
X-Belong-Attack: 6db6ce4e29823fbd_1551717337702_177296820
X-MC-Loop-Signature: 1551717337702:1797347645
X-MC-Ingress-Time: 1551717337701
Content-Type: text/plain;	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Supplying a patched package
From: Rob Arthan <rda AT lemma-one DOT com>
In-Reply-To: <65cf7307-3bf2-d8fe-6be9-889bdf60bf32@cornell.edu>
Date: Mon, 4 Mar 2019 16:35:33 +0000
Cc: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Message-Id: <1CA67F57-3BF1-448E-A64E-046F4333AD58@lemma-one.com>
References: <03354D05-354F-4C65-9932-2D663EB32B5F AT lemma-one DOT com> <65cf7307-3bf2-d8fe-6be9-889bdf60bf32 AT cornell DOT edu>
To: Ken Brown <kbrown AT cornell DOT edu>
X-AuthUser: rda AT lemma-one DOT com
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x24GZsGK016576



> On 29 Oct 2018, at 14:46, Ken Brown <kbrown AT cornell DOT edu> wrote:
> 
> 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.
> 

Belated thanks for your advice. Creating a Cygwin package for my app (ProofPower)
sounds like a very good idea and I will look into it.

Unfortunately, the enhancements to ProofPower that needed the OpenMotif bug fix
are currently stymied on Cygwin by another problem. So I won’t need to bother anybody about
applying my patch in the short term.

Regards,

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