X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 15 May 2008 15:49:02 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin@cygwin.com To: Chris Howell cc: cygwin@cygwin.com Subject: Re: Question about link In-Reply-To: <482C8ECC.9030202@pyxisinnovation.com> Message-ID: References: <1210879461.20883.ezmlm@cygwin.com> <482C8ECC.9030202@pyxisinnovation.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, 15 May 2008, Chris Howell wrote: > I am running on Vista, and what I am doing is I open up a Dev Studio > 2008 command shell. From that command shell I launch cygwin/bash... > Things like cl.exe are inherited from the first shell I've opened in the > bash environment. What I want is link to be the path that is found under > my BIN directory of my DevStudio install. However possibily because > they're the same name when I query link, or try and use it to make a > dll. Bash thinks I am using link to make a symbolic link as opposed to a > dll. > > Any suggestions or help would be appreciated. Hmm, does export PATH="$(dirname "$(which cl.exe)"):$PATH" not solve this for you? You could also do alias link="$(dirname "$(which cl.exe)")/link.exe" but that will only give you "link", not "link.exe" (in case you care). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "That which is hateful to you, do not do to your neighbor. That is the whole Torah; the rest is commentary. Go and study it." -- Rabbi Hillel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/