DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 583JvQFU4007648 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 583JvQFU4007648 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=QZvCEgUF X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BC8AD3858D26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1756929444; bh=S6j4iL/iSuhSW8AaZ+QFakcCk6yOrINgRxh+IlZqCMA=; h=Date:To:cc:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=QZvCEgUF+AEgaPGcqYCcmFqU1Xgb/3brmxV9deoWXLzkyh2xMQd27Rwz7RGid69l/ rwlF3IuoK58eW7sLGCLLh2cC+/ZOT5anFIMHGQsan5td5MaSEesKA/R2lyRWHiyb4k dN4tNyPOGKEsh5RKcBWVMtbMe/I/0+KRLxLLVY1o= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1F95E3858C53 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 1F95E3858C53 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1756929378; cv=none; b=BIvDm5owydEUFyAnokAz/ydUlLQkA2Vne3JtohFzxcVy6yoFznJCuFYNYuIHj1CvkXy3RiazraIVkYL5ii4pn4GbvrXg2PT2rNkQSEEOkydXUnRn71+b6iplz7acWxm4N3mXKIcKlEnO4jOslS4ymxD7D/tHLw3X39S9UKph5gM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1756929378; c=relaxed/simple; bh=QKYHYAY/oOhKKzF3zlMtYZ3TuFKEnAueQgsznUsddXc=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=jxxXJw6H0VGGLNGf4cfEmi1xNnEh7YNhX4mi2BROSKrQ8jZ+pMrRhFY0xXvGK3tYvZE7MhhuyLmyY/s6SsUntYSnScbjzmUf2VEGGDq3xAS/+DX0IVcnEYs1IoigTi3byuj7pf7hdjtqwJsy5IEB3Bg4y52ueBu4UrRgP34x9EU= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1F95E3858C53 Date: Wed, 3 Sep 2025 12:56:17 -0700 (PDT) X-X-Sender: jeremyd AT resin DOT csoft DOT net To: Mark Liam Brown cc: cygwin AT cygwin DOT com Subject: Re: Deploy DLL for ARM64 and AMD64 in the same PATH? In-Reply-To: Message-ID: References: MIME-Version: 1.0 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Jeremy Drake via Cygwin Reply-To: Jeremy Drake Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Wed, 3 Sep 2025, Mark Liam Brown via Cygwin wrote: > Greetings > > Our software needs a 3rd party DLL (we cannot change the name...), but > we want to support ARM64 together with AMD64. > > Does Windows or Cygwin have a mechanism to deal with the situation > that both expects the DLL to be in the same path? Not really. The closest thing is ARM64EC and ARM64X, a DLL built with those will let you use the same DLL for both ARM64 and x64, but only on ARM64. I know there has been work to support those in LLVM/LLD and mingw-w64, don't know about gcc/binutils support. I think they expect the installer to decide which type of DLL to install based on the host machine... -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple