[cfe-dev] Compiling a simple Win32 program

[Nikola Smiljanic]

MinGW users should be in the clear since GnuWin32 only collides with
link.exe from VS, or so I think. The question is how to decide whether to
search for msvc or mingw, but this is where the default triple comes into
play?

On Wed, Jun 13, 2012 at 9:59 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote:

> Hehe, what if the user prepends the GnuWin32 tools or MSYS to the path
> AFTER having run vcvarsall.bat?  Anyway, I figure that most LLVM users are
> bright enough that they'll figure it out quickly.
>
>
> 2012/6/13 Michael Spencer <bigcheesegs at gmail.com>
>
>> On Tue, Jun 12, 2012 at 8:09 PM, Mikael Lyngvig <mikael at lyngvig.org>
>> wrote:
>> > Just be aware that GnuWin32 includes a link.exe command, which creates
>> > symbolic or hard links (not sure which).  It is part of GNU coreutils.
>>  So
>> > if the user sets up an environment to use GnuWin32 and Mingw32, so as
>> to be
>> > able to run the llvm test suite, you'll bug into this one.
>>
>> vcvars prepends it's paths to PATH, so it will not find gnuwin32 or
>> mingw/msys link.
>>
>> - Michael Spencer
>>
>> > 2012/6/12 Nikola Smiljanic <popizdeh at gmail.com>
>> >>
>> >> It will search the path to find the first link.exe. The one from Visual
>> >> Studio should be first if Command prompt or vcvars.bat are used.
>> >>
>> >>
>> >> On Tue, Jun 12, 2012 at 2:23 PM, Kim Gräsman <kim.grasman at gmail.com>
>> >> wrote:
>> >>>
>> >>>
>> >>> That sounds like it would match my expectations for behavior, good
>> idea!
>> >>>
>> >>> Can you have it fall back on %PATH% if no VS environment variables are
>> >>> found?
>> >>>
>> >>> Thanks,
>> >>> - Kim
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20120613/f8f021df/attachment.html>