From: Randy Geyer <randy.geyer@gmail.com>
To: libffi-discuss@sourceware.org
Subject: How to change the name of the libffi-3.3 generated dll/lib files on windows?
Date: Fri, 20 Nov 2020 15:56:11 -0800 [thread overview]
Message-ID: <CAKmEa0rjOw5ja9a64eugVTDv8c92a5=kWP4Kt99y+DMUVY35VQ@mail.gmail.com> (raw)
I have successfully build a libffi-3.3 on windows using this Configure:
./configure CC="$(shell pwd)/libffi/msvcc.sh -m64" CXX="$(shell
pwd)/libffi/msvcc.sh -m64" CPP="cl -nologo -EP"
CPPFLAGS="-DFFI_BUILDING_DLL" --build=x86_64-w64-cygwin
--host=x86_64-w64-cygwin';
The libffi-7.dll and libffi-7.lib file are generated under
pwd\libffi\x86_64-w64-cygwin\.libs. libffi-7.lib has named references to
libffi-7.dll so I can't just rename the dll or our application build fails
because the libffi-7.dll references in the .lib.
Is there a way to have the libffi make produce ffi.dll and ffi.lib instead?
so that the .lib refers to ffi.dll not libffi-7.dll.
Note: I tried adding --program-transform-name='s/libffi-7/ffi/' as a
Configure parameter, but that had no effect.
reply other threads:[~2020-11-20 23:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKmEa0rjOw5ja9a64eugVTDv8c92a5=kWP4Kt99y+DMUVY35VQ@mail.gmail.com' \
--to=randy.geyer@gmail.com \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).