public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jose Isaias Cabrera <jicman@outlook.com>
To: Jose Isaias Cabrera <jicman@outlook.com>,
	Michael Soegtrop <MSoegtrop@yahoo.de>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Creating the sqlite3.exe stand-alone w/o cygwin dependency
Date: Sun, 11 Dec 2022 03:31:06 +0000	[thread overview]
Message-ID: <DB9P251MB0063C4C766B3FCE4FD1A32A4DE1E9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DB9P251MB0063D46AB1B34F75B4FAB365DE1F9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM>


On Saturday, December 10, 2022 1:01 PM, Jose Isaias Cabrera expressed:
>
> These reported DLL are in the search path, and also moving these to the executable 
> folder still gives the same error. I also moved the sqlite3.exe file from the built
> folder to the previous folder in the Cygwin environment, and the same problem
> happens:

Just to put this to rest, and I am sure that there is a way of doing this using i686-w64-mingw32, but the only way that it appears to work is just doing plain ./configure and make. 

./configure
make

And then doing these commands:

To create the DLL:
i686-w64-mingw32-gcc -shared -static-libgcc sqlite3.c -o sqlite3.dll

To create the CLI tool:
i686-w64-mingw32-gcc -static-libgcc shell.c -o sqlite3.exe sqlite3.c

Both sqlite3.dll and sqlite3.exe CLI tool will work outside the cygwin environment. Just in case someone ever needs this. Thanks for all the support.

josé

  reply	other threads:[~2022-12-11  3:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 21:34 Jose Isaias Cabrera
2022-12-09 23:33 ` Eliot Moss
2022-12-10  2:43   ` Jose Isaias Cabrera
2022-12-10 14:47     ` Eliot Moss
2022-12-10 15:36       ` Cristobal Escamilla Cavazos
2022-12-10 16:35       ` Jose Isaias Cabrera
2022-12-10 14:42 ` Ken Brown
2022-12-10 15:20   ` Michael Soegtrop
2022-12-10 18:00     ` Jose Isaias Cabrera
2022-12-11  3:31       ` Jose Isaias Cabrera [this message]
2022-12-11 10:23         ` Michael Soegtrop
2022-12-11 20:03           ` Jose Isaias Cabrera
2022-12-11 20:41             ` Michael Soegtrop
2022-12-12 23:22               ` Jose Isaias Cabrera

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=DB9P251MB0063C4C766B3FCE4FD1A32A4DE1E9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM \
    --to=jicman@outlook.com \
    --cc=MSoegtrop@yahoo.de \
    --cc=cygwin@cygwin.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).