public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: having 1 set of non-bin files w/separate {bin,lib}[32/64)? (was Re: please update the supported Cygwin package list ...)
Date: Sat, 03 Aug 2013 11:33:00 -0000	[thread overview]
Message-ID: <51FCEA73.7030903@tlinx.org> (raw)
In-Reply-To: <51F9ABA0.3090205@etr-usa.com>

Warren Young wrote:
>> then maybe in your bashrc have
>> it do a cygmount or create a softlinke from /bin32 -> /bin or 
>> /bin64->/bin
>> (and same for lib)?
> 
> You can't just merge the two bin/lib dirs.  The executable names 
> conflict.  My solution involving a "cygwin2.dll" is the only solution I 
> see.  And again, it's packed with potential pain.
---
Sorry, didn't mean to be misunderstood ;-).

I meant if something (pie in the sky?) in a bash startup script
(maybe always running out of the 32-bit dir for arguments sake),
could mount directories ... neh....only if everything was running
32/64... windows only implemented redirection insides the /windows
folder...

hmmm...
so if one put the cygwin 32-bit binaries under /windows/syswow64
and the 64-bit binaries under /windows/sysnative (as seen by 32bit)
or system32 when running 64, then a program would always be
able to refer to say, /windows/system32/cygwin/{bin,lib} as hard
paths -- and 32-bit binaries would always be redirected to /windows/syswow64
while 64-bit binaries would really access the stuff natively/directly.

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

Seriously, it might not be the most loved location, but it is the only one
that would work and allow auto translation.

A link made with mklink forms a symlink, so they could be used to point at
the dir location under system32 ... but 32-bit processes would be autodirected to
the syswow64 dir....

Dang... nowif you can think of another way to do it automatically and not
change names etc...

It might be possible to just put symlinks in system32 and syswow, that would
be seen by 64-bit and 32-bit procs that point to real dirs located in the
root of the vol (/cygwin or /...)...that likely would be better -- less junk
in the windir... but the links would still have to travel through the redirector.


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

  reply	other threads:[~2013-08-03 11:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27  3:32 please update the supported Cygwin package list to be distinct for 32-bit, 64-bit or both; and help on how install both in a merged fashion Kenneth Wolcott
2013-07-27  5:20 ` marco atzeri
2013-07-27  5:24   ` Kenneth Wolcott
2013-07-27  6:20     ` LRN
2013-07-27  7:26       ` Andrey Repin
2013-07-27 10:30         ` LRN
2013-07-27  6:29     ` marco atzeri
2013-07-27  7:57       ` Warren Young
     [not found]         ` <51F9A3BE.4020907@tlinx.org>
2013-08-01  0:28           ` having 1 set of non-bin files w/separate {bin,lib}[32/64)? (was Re: please update the supported Cygwin package list ...) Warren Young
2013-08-03 11:33             ` Linda Walsh [this message]
2013-08-03 15:48               ` Earnie Boyd
2013-08-04  2:19                 ` Linda Walsh
2013-08-04  3:54                   ` Earnie Boyd
2013-08-04  4:56                     ` Linda Walsh
2013-07-27  5:28 ` please update the supported Cygwin package list to be distinct for 32-bit, 64-bit or both; and help on how install both in a merged fashion Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51FCEA73.7030903@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).