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: having 1 set of non-bin files w/separate {bin,lib}[32/64)? (was Re: please update the supported Cygwin package list ...)


Earnie Boyd wrote:
On Sat, Aug 3, 2013 at 7:33 AM, Linda Walsh wrote:

Hello Linda,

It seems to be the only reliable 32-bit redirection -- and MS chose to put
it in the /windows dir... so they must want customers to put anything
needing
that feature in that dir...right?? ;-)  Oi...

Absolutely not what MS intended for the /windows directory.  That is
the OS directory and only MS installations should use it.
----
		Sorry, I assume you did catch the irony.

The /"Program Files" (64bit) and /"Program Files (x86)" (32bit)
directories are where MS directs developers to put their binaries.
However we don't like spaces in path names so this isn't a good
location.
---
	Which is why you create /prog->one /prog{32,64}->point to the other
as mklink /d symlinks in the root of the fs.



However you the user have a choice of where to put things.  Frankly, I
would use /cygwin and /cygwin32
----
	And how does that get you the autoredirection I suggested with
the links in Windows/syswow64 and windows/system32?




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


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