This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Documentation on -mno-cygwin Accuracy

On 2/7/2012 3:10 PM, carolus wrote:
On 2/7/2012 1:51 PM, Tim Prince wrote:
On 2/6/2012 2:29 PM, Charles D. Russell wrote:

i686-w64-mingw32-gfortran.exe hello.f -o hello

cdr@dell03 ~/mingtest
$ ./hello
/home/cdr/mingtest/hello.exe: error while loading shared libraries:
3.dll: cannot open shared object file: No such file or directory

The cygwin distribution of mingw puts the support dlls in their own directories. You must act yourself to get them on PATH. This is a consequence of their not being cygwin compilers and giving you a mongrel combination of cygwin and Windows setup. However, cygwin provides useful tools like find and export: export PATH=/usr/x86_64-w64-mingw32/sys-root/mingw/bin/:$PATH

The old -mno-cygwin yielded a standalone executable that I could give to
a colleague and it would "just work" on a Windows machine without
cygwin. It appears that now one must bundle at least one dll. From a
licensing standpoint, are these dll's any different from cygwin1.dll?
Can they be distributed freely without bundling the source code? If not,
I might as well forget about mingw and just supply cygwin1.dll.

Seems off-topic here. Does begin to answer your question? How about the recent suggestion of -static?

-- Tim Prince

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]