public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <andrex@alumni.utexas.net>
To: cygwin@cygwin.com
Subject: Re: setting Win32 environment variables in Cygwin
Date: Thu, 21 Jul 2005 10:40:00 -0000	[thread overview]
Message-ID: <dbnpsc$mrg$1@sea.gmane.org> (raw)
In-Reply-To: <9bbd2794050720120434ea1470@mail.gmail.com>

> Specifically, I need to do
> 
> Set PATH=C:\Program Files\Microsoft Visual C++ Toolkit 2003\bin;%PATH%
> Set INCLUDE=C:\Program Files\Microsoft Visual C++ Toolkit
> 2003\include;%INCLUDE% Set LIB=C:\Program Files\Microsoft Visual Studio
> .NET 2003\Vc7\lib;C:\Program Files\Microsoft Visual C++ Toolkit
> 2003\lib;%LIB%
> 
> So that VC++ will run properly from the command line. Any suggestions?

Since these variables are to be used by a Windows app, it would make most
sense to set them in Windows.  Then they'll be available to all Windows
apps (including others that might start VC++), and also in Cygwin.  In XP,
you can use the so-well-hidden-it's-almost-gone environment variables pane: 
right click on my computer, Properties, Advanced, Environment Variables. 
You may find it easier just to enter them directly into the registry: 
HKCU\Environment for user-specific variables, or
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment for
system-wide variables.

For path variables that you want to use in both Windows and Cygwin, there is
a path conversion problem, as Igor says.  If you're using VC++ and not gcc,
then you can just leave INCLUDE et al. as Windows-format paths.  But if you
want to launch both from Cygwin, then you have a problem, because either
path format (Windows or Cygwin) will be wrong for one of them.  I guess
what's needed is to put the paths into Cygwin format, and write a wrapper
script for VC++, that converts them back to Windows format first. 
Fortunately cygpath(1) can make these conversions for you.

Good luck,
Andrew.



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

      parent reply	other threads:[~2005-07-21  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 19:21 Alex Goldman
2005-07-20 21:47 ` Mark Hadfield
2005-07-20 23:51   ` Igor Pechtchanski
2005-07-21 10:40 ` Andrew Schulman [this message]

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='dbnpsc$mrg$1@sea.gmane.org' \
    --to=andrex@alumni.utexas.net \
    --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).