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:from:content-type:content-transfer-encoding :mime-version:subject:message-id:date:to; q=dns; s=default; b=xI Qqm4V8IY+btArIpL4T1mnstaN7NTWTQ0kfwvJ9sMPUacp7hWhOQUa97qnGC9kqnb QIJVKGz47EjUB2e7BzcK8SzxOshJMqkUeXNTouej6EQc19+pecdxRDuo0F+aMdrX 3SPA9UXNgF1ZFYyMacPrPidWRV9ThcmM1n9+c5RL0= 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:from:content-type:content-transfer-encoding :mime-version:subject:message-id:date:to; s=default; bh=n29BT7El W8q84vuCGVOdtdBavfg=; b=szAdCeNxUvUANfoFcTKE0DDPkDbJd33noXinaBEE 1zOOQq59L91j2WpE/YP2sdIpJ9/QRKjwo1HZu9eEiXi4OCR4bI49EdMguSWMUE06 d9DUAZMvqq2qiEr7LH/fdcp5PtFgK9/LCXQAPySL8+mzttGeoZBkT217A0WNxXYb sgc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=interim, exposed, rob, alongside X-HELO: gecko.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-Tangy-Wiry: 7cffd6f633cf3ad1_1540745019777_3024749193 X-MC-Loop-Signature: 1540745019777:261505915 X-MC-Ingress-Time: 1540745019777 From: Rob Arthan Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Supplying a patched package Message-Id: <03354D05-354F-4C65-9932-2D663EB32B5F@lemma-one.com> Date: Sun, 28 Oct 2018 16:43:36 +0000 To: cygwin AT cygwin DOT com 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 w9SGhsZ6019320 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? Cheers, 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