Documentation on -mno-cygwin Accuracy

[carolus]

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:
>> libgfortran-
>> 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.


--
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