From: Jose Isaias Cabrera <jicman@outlook.com>
To: Tony Kelman <tony@kelman.net>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: How to build a DLL without cygwin DLL dependencies
Date: Thu, 30 May 2019 02:51:00 -0000 [thread overview]
Message-ID: <AM0PR01MB5377DDC6AE970F5742556FC9DE180@AM0PR01MB5377.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CY4PR22MB0773A4B996F728085A569EB4A71F0@CY4PR22MB0773.namprd22.prod.outlook.com>
Tony Kelman, on Wednesday, May 29, 2019 04:18 PM, wrote...
>and you can avoid the issue by building a 64 bit dll, or in 32 bit via
>
>i686-w64-mingw32-gcc -shared -static-libgcc sqlite3.c -o sqlite3.dll
>
This is what I needed above. The command I was using,
i686-w64-mingw32-gcc -shared sqlite3.c -o sqlite3.dll
will create a DLL, but it will have dependencies on some cygwin libs. This command,
i686-w64-mingw32-gcc -shared -static-libgcc sqlite3.c -o sqlite3.dll
creates a DLL with no dependencies. So, the option -static-libgcc is what I needed. Thanks.
To summarize, when creating SQLite3 DLL or building any SQLite3 tools with cygwin,
1. Download the i686-w65-mingw32-gcc compiler with the setup tools (the 64 bit)
2. Get the source from sqlite.org
3. untar source
4. cd to the source directory
5. run this command:
i686-w64-mingw32-gcc -shared -static-libgcc sqlite3.c -o sqlite3.dll
Thanks,
josé
--
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
next prev parent reply other threads:[~2019-05-30 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 17:02 Jose Isaias Cabrera
2019-05-29 17:55 ` Tony Kelman
2019-05-29 18:27 ` Jose Isaias Cabrera
2019-05-29 20:18 ` Tony Kelman
2019-05-30 2:51 ` Jose Isaias Cabrera [this message]
2019-05-31 17:01 ` Tatsuro MATSUOKA
2019-05-31 17:14 ` Jose Isaias Cabrera
2019-05-31 18:24 ` Brian Inglis
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=AM0PR01MB5377DDC6AE970F5742556FC9DE180@AM0PR01MB5377.eurprd01.prod.exchangelabs.com \
--to=jicman@outlook.com \
--cc=cygwin@cygwin.com \
--cc=tony@kelman.net \
/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).