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: Question about link.exe?


I found that setting the complier and linker (all the tools, actually) to the full path is the most reliable means to ensure the correct executables are picked up.

ie.

CC = full_path_to_ds_8_bin/cl.exe
LINK = full_path_to_ds_8_bin/link.exe

you can use the registered environment variables for DS to build the full path up. (can't remember the name right now, I'm at home).

-lee

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.

Cheers
Chris Howell
Software Engineer
the PYXIS innovation inc
Kingston Ontario,
w: www.pyxisinnovation.com
p: 613-389-3430

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

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


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