public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jose Isaias Cabrera <jicman@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Creating the sqlite3.exe stand-alone w/o cygwin dependency
Date: Fri, 9 Dec 2022 21:34:35 +0000	[thread overview]
Message-ID: <DB9P251MB00639C367F5AA38BF0F18B55DE1C9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM> (raw)


Greetings!

Using these commands,

./configure --host=i686-w64-mingw32 CFLAGS=-shared CFLAGS=-static-libgcc
make sqlite3.exe sqlite3.dll

I can create the sqlite3 DOS application and the sqlite3 Windows 10 DLL. I have no problem with the DLL. But with the sqlite3.exe CLI tool, I can run it in the Cygwin environment, and I can also double click on the app from the Windows 10 environment and run it, and that also works perfectly. The problem happens after I move that sqlite3.exe to C:\bin directory. When I run it from the DOS Command Prompt, I get this error:

DOS|16:19:00.58>sqlite3
DOS|sqlite3: FATAL: Couldn't find sqlite3.

If I add .exe to the end,

DOS|16:19:57.46>sqlite3.exe
DOS|
DOS|16:21:33.36>

It appears as if it starts and does nothing. I tried chatting with SQLite folks, but, apparently, I am the only one that uses Cygwin. I have been using Cygwin for a long time, and I like it. Thoughts? Suggestions? Any help would be greatly appreciated.

PS: This is the make sqlite.exe run:

E608313@HOR711318E ~/b/sqlite/SQLite-78723a9a
$ make sqlite3.exe
./libtool --mode=link i686-w64-mingw32-gcc -shared -static-libgcc -DSQLITE_OS_WIN=1 -I. -I/home/E608313/b/sqlite/SQLite-78723a9a/src -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/rtree -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/icu -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/fts3 -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/async -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/session -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/userauth -D_HAVE_SQLITE_CONFIG_H -DBUILD_sqlite -DNDEBUG -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS     -DHAVE_READLINE=0  -DHAVE_EDITLINE=0 -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_EXPLAIN_COMMENTS -DSQLITE_ENABLE_UNKNOWN_SQL_FUNCTION -DSQLITE_ENABLE_STMTVTAB -DSQLITE_ENABLE_DBPAGE_VTAB -DSQLITE_ENABLE_DBSTAT_VTAB -DSQLITE_ENABLE_BYTECODE_VTAB -DSQLITE_ENABLE_OFFSET_SQL_FUNC -o sqlite3.exe \
        shell.c sqlite3.c \
          -rpath "/usr/local/lib"
libtool: link: i686-w64-mingw32-gcc -shared -static-libgcc -DSQLITE_OS_WIN=1 -I. -I/home/E608313/b/sqlite/SQLite-78723a9a/src -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/rtree -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/icu -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/fts3 -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/async -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/session -I/home/E608313/b/sqlite/SQLite-78723a9a/ext/userauth -D_HAVE_SQLITE_CONFIG_H -DBUILD_sqlite -DNDEBUG -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_MATH_FUNCTIONS -DHAVE_READLINE=0 -DHAVE_EDITLINE=0 -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_EXPLAIN_COMMENTS -DSQLITE_ENABLE_UNKNOWN_SQL_FUNCTION -DSQLITE_ENABLE_STMTVTAB -DSQLITE_ENABLE_DBPAGE_VTAB -DSQLITE_ENABLE_DBSTAT_VTAB -DSQLITE_ENABLE_BYTECODE_VTAB -DSQLITE_ENABLE_OFFSET_SQL_FUNC -o .libs/sqlite3.exe shell.c sqlite3.c  -L/usr/local/lib



             reply	other threads:[~2022-12-09 21:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 21:34 Jose Isaias Cabrera [this message]
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
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=DB9P251MB00639C367F5AA38BF0F18B55DE1C9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM \
    --to=jicman@outlook.com \
    --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).