From: Tony Kelman <tony@kelman.net>
To: Jose Isaias Cabrera <jicman@outlook.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: How to build a DLL without cygwin DLL dependencies
Date: Wed, 29 May 2019 17:55:00 -0000 [thread overview]
Message-ID: <CY4PR22MB0773AD002D202CE1D084A227A71F0@CY4PR22MB0773.namprd22.prod.outlook.com> (raw)
In-Reply-To: <DB7PR01MB5386F8869A992304E8979E4DDE1F0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com>
> I am trying to build the latest sqlite windows DLL, and I am
> succeeding, but I am getting an error that cygwin1.dll is missing,
> when I am trying to use the DLL from outside cygwin in the Windows
> environment. I am using,
>
> gcc -shared sqlite3.c -o sqlite3.dll
>
> to build it, but this command creates a dependency for cygwin1.dll.
> Is there any way to build the dll as a standalone DLL with no
> dependency? Thanks.
Yep, you want the mingw-w64 cross compiler, x86_64-w64-mingw32-gcc
(or i686-w64-mingw32-gcc for 32 bit). There's a cross-compiled sqlite
package already available under mingw64-x86_64-sqlite3 in setup - or
http://mirrors.kernel.org/sourceware/cygwin/noarch/release/mingw64-x86_64-sqlite3/mingw64-x86_64-sqlite3-3.19.3-1.tar.xz
if you're okay with that particular release.
--
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-29 17:55 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 [this message]
2019-05-29 18:27 ` Jose Isaias Cabrera
2019-05-29 20:18 ` Tony Kelman
2019-05-30 2:51 ` Jose Isaias Cabrera
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=CY4PR22MB0773AD002D202CE1D084A227A71F0@CY4PR22MB0773.namprd22.prod.outlook.com \
--to=tony@kelman.net \
--cc=cygwin@cygwin.com \
--cc=jicman@outlook.com \
/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).