From: Oskar Skog <oskar@oskog97.com>
To: cygwin@cygwin.com
Subject: Re: Building SQLite3 CLI without
Date: Fri, 2 Dec 2022 23:37:20 +0200 [thread overview]
Message-ID: <fd07602a-62d5-e72d-7363-825dc709b59b@oskog97.com> (raw)
In-Reply-To: <DB9P251MB00638FF81903EC8818615065DE179@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM>
On 2022-12-02 22:37, Jose Isaias Cabrera via Cygwin wrote:
>
> Greetings and salutations!
>
> I can build SQLite DLL and use it under Windows without any problem using this command:
>
> i686-w64-mingw32-gcc -shared -static-libgcc sqlite3.c -o sqlite3.dll
>
> And I can use that DLL outside cygwin without any problem. I can also build the SQLite3.exe tool using this command:
>
> i686-w64-mingw32-gcc -shared -static-libgcc shell.c -o sqlite3.exe
>
> The problem is that when I run this sqlite3.exe outside the cygwin environment, it gives me the error:
>
> "The code execution cannot proceed because cygwin1.dll was
> not found. Reinstalling the program may fix this problem."
>
> Is there an option that I can do to build the tool without the need of the cygwin1.dll? I know that I can move the file in the same spot, but I want to create it without the need of it. Thanks for your support.
>
> josé
>
https://cygwin.com/faq/faq.html#faq.programming.static-linking
"No. If your program uses the Cygwin API, then your executable cannot
run without cygwin1.dll. In particular, it is not possible to statically
link with a Cygwin library to obtain an independent, self-contained
executable."
next prev parent reply other threads:[~2022-12-02 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 20:37 Jose Isaias Cabrera
2022-12-02 21:37 ` Oskar Skog [this message]
2022-12-02 21:53 ` Jose Isaias Cabrera
2022-12-03 21:14 ` Jose Isaias Cabrera
2022-12-03 22:20 ` Ken Brown
2022-12-03 23:15 ` Jose Isaias Cabrera
2022-12-03 16:23 ` Andrey Repin
2022-12-03 18:34 ` 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=fd07602a-62d5-e72d-7363-825dc709b59b@oskog97.com \
--to=oskar@oskog97.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).