This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: having 1 set of non-bin files w/separate {bin,lib}[32/64)? (was Re: please update the supported Cygwin package list ...)
- From: Earnie Boyd <earnie at users dot sourceforge dot net>
- To: cygwin at cygwin dot com
- Date: Sat, 3 Aug 2013 11:48:05 -0400
- Subject: Re: having 1 set of non-bin files w/separate {bin,lib}[32/64)? (was Re: please update the supported Cygwin package list ...)
- References: <CADex0xxLK3LRfHcat8UYXDUoYxRu5OPzV0_+FXMKd7k_J4G+Vg at mail dot gmail dot com> <51F34FA0 dot 50300 at gmail dot com> <CADex0xwDTvHaOS-_xAr3pARiBQ19zAdOS8US06r+E14b65SC-w at mail dot gmail dot com> <51F35E4A dot 4040207 at gmail dot com> <51F368C4 dot 5030309 at etr-usa dot com> <51F9A3BE dot 4020907 at tlinx dot org> <51F9ABA0 dot 3090205 at etr-usa dot com> <51FCEA73 dot 7030903 at tlinx dot org>
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.
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.
However you the user have a choice of where to put things. Frankly, I
would use /cygwin and /cygwin32 to segregate similar to what MS did
for Windows but that is just me. The one thing with Cygwin you need
to be careful of is that 32bit binaries need the 32bit DLL and mixing
and matching may cause you no end of grief.
--
Earnie
-- https://sites.google.com/site/earnieboyd
--
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