public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jose Isaias Cabrera <jicman@outlook.com>
To: 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 20:03:16 +0000	[thread overview]
Message-ID: <DB9P251MB0063791D209FB7A612196349DE1E9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <c8f0bfa8-dd62-02d4-2a64-dfb80c8988ec@yahoo.de>


On December 11, 2022 5:23 AM, Michael Soegtrop  expressed:
> 
> Hi José,
> 
> did you try copying the MinGW DLLs as I suggested?

Yes, I did. I think you missed one of my emails. But, here is what I did:
$ ldd sqlite3.exe
        ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ffc1d6f0000)
        ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x778c0000)
        wow64.dll => /cygdrive/c/Windows/System32/wow64.dll (0x7ffc1c830000)
        wow64win.dll => /cygdrive/c/Windows/System32/wow64win.dll (0x7ffc1d540000)

These are in the path, but also copying these to the executatble folder still gives the same error. I am able to get what I need by doing configure and make without any input. Then running the two commands on the previous email. The idea was to create stand-alone CLI tool and DLL without having any dependency of cygwin. I am able to do that with extra steps, but, for now, that is ok.

Grabbing on a very week branch, I think Corinna's changes for v3.4 is "breaking"/"fixing" some things with i686-w64-mingw32. Some of this used to work 3-4 weeks ago. I think I still have a machine with some old software. I am going to try it there and see if that old Cygwin version works.

  reply	other threads:[~2022-12-11 20:03 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
2022-12-11 10:23         ` Michael Soegtrop
2022-12-11 20:03           ` Jose Isaias Cabrera [this message]
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=DB9P251MB0063791D209FB7A612196349DE1E9@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).