From: Andrey Repin <anrdaemon@yandex.ru>
To: Yucong Sun <sunyucong@gmail.com>, cygwin@cygwin.com
Subject: Re: Running a program using a DLL under Cygwin
Date: Thu, 08 Oct 2015 15:20:00 -0000 [thread overview]
Message-ID: <393201296.20151008181210@yandex.ru> (raw)
In-Reply-To: <CAJygYd3DLkzj=Va7uuU8-NSjUG6kog0YqBuvhDMMA=0vZwY+=Q@mail.gmail.com>
Greetings, Yucong Sun!
https://cygwin.com/acronyms/#TOFU pretty please...
> I think symlink is a cygwin thing. Windows won't find that DLL (just
> like you won't find it using windows explorer.)
Unless he have created a Windows symlink, that is correct.
Explorer, however, may find it, as Cygwin symlinks are Windows LNK files.
> Windows only support loading DLL from project directory, or system32
> as far as I know.
That's not correct. Windows can be told to load DLL's from multiple places,
and you can add to that by registering your DLL in AppPaths registry key.
But a bottom point of the issue is that the OP's project is poorly designed
and needs a rework in the part of finding and loading custom plugins
(I suppose).
There should be no need to move DLL's around, least to place them in a shared
location like user's ~/bin...
--
With best regards,
Andrey Repin
Thursday, October 8, 2015 18:08:16
Sorry for my terrible english...
--
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:[~2015-10-08 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 13:37 Dr Rainer Woitok
2015-10-08 13:56 ` Yucong Sun
2015-10-08 14:54 ` Csaba Raduly
2015-10-08 15:20 ` Andrey Repin [this message]
2015-10-11 5:54 ` Linda Walsh
2015-10-11 14:35 ` Andrey Repin
2015-10-11 22:38 ` Problems w/cygsym links vs. winsymlnks: (was Re: Running a program using a DLL under Cygwin) Linda Walsh
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=393201296.20151008181210@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=sunyucong@gmail.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).