From: tibor@alteon.com (Tibor Polgar) Subject: Re: Re comments in gnuwin32 30 Sep 1997 13:56:40 -0700 Message-ID: <9709302035.AA11200.cygnus.gnu-win32@mtlyell.acteon.com> References: <342fa1e6.127616432@smtp.netzone.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII To: jeffdbREMOVETHIS@netzone.com Cc: Eric Mills , gnu-win32@cygnus.com > Unfortunately there seems to be some confusion over > what a "native" file mode is, personally I think that > worrying what the "native" file mode is in an emulation > dll is kind of backwards, an emulation dll is there to > create a non "native" environment in the first place > so having cygwin32 open files in TEXT mode by default > just because 95/NT do is rather silly ;^) > AND breaks many otherwise working posix programs ;^( Agreed. -b should be default. any file under / to me is under posix control vs. any //drive/ (or thankfully drive:/) is under MS control and needs to be treated as text!=binary (unless mounted). > Unfortunately if you work that way, when you > send the software to your customers/buddys > and they install it, it sets up the default text!=binary > mount table, and you get calls wondering why > things don't work ;^( I've repackaged the cygnus cdk/usertools into a local cygwin.exe install file. It builds a standard(?!) unix directory tree (/bin, /lib, /usr,...) and loads everything into the right spot. It then directly hammers the registry with all the correct mounts, adds $HOME, $GCC_EXEC_PREFIX and finally adds all to the $PATH MS style paths to the bins and libs. Its the only way i could guarantee a predictable environment. Tibor - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".