llvm dev - Dec 2004 - [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfileor directory

----Original Message Follows----
From: Jeff Cohen <jeffc at jolt-lang.org>
Reply-To: jeffc at jolt-lang.org,        LLVM Developers Mailing List 
<llvmdev at cs.uiuc.edu>
To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': 
No	suchfileor directory
Date: Thu, 23 Dec 2004 08:05:39 -0800
>Yes, it should find windows.h with the default configuration.  But you have 
>to be suspicious of >beta code that Microsoft gives out for free.  It
might
>just be very buggy, or it might be >deliberately crippled.  Considering
the
>price tag on Visual Studio, it's one or the other (and >probably
both).
For a month ago I was at a .NET seminar hosted by MS and the spokesman said, 
you should be cautios with beta software. They don't delibrately cribble the
software, but sometimes, depending on the scope of the build, known errors 
e.t.c., they disable known buggy or other functionality.

And I did take it that way.
>Out of curiosity, did it accept the solution and project files as is, or 
>did it want to "upgrade" >them?  If the latter, I cannot accept
any patches
>for those files because they would break VC++ >7.1 (which in turn broke 
>7.0, which in turn broke 6.x).
No, it didn't take the project files out of the box. It insisted to upgrade 
the soulution and project files.

Henrik.

Henrik Bach wrote:
>----Original Message Follows----
>From: Jeff Cohen <jeffc at jolt-lang.org>
>Reply-To: jeffc at jolt-lang.org,        LLVM Developers Mailing List 
><llvmdev at cs.uiuc.edu>
>To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h':
No
>suchfile    or directory
>Date: Tue, 21 Dec 2004 16:29:47 -0800
>
>>Windows.h is part of Microsoft's Platform SDK that's bundled
with Visual
>>Studio.  It should never >have been in the llvm source tree.  Why
don't
>>you have it?  You have VC++, right?
>
>
>Yes, I  had the express beta version of VC++, but something weird happened 
>with my installation, so I've uninstalled it for the moment.
>
>I assume, It should have found <windows.h> implicit from it's own 
>installation directory. Correct?
>Next, I searched for it, and found it. Then I thought, I had to upgrade 
>with the newest VC++ october TCP installation. But with the result that 
>windows.h file has disappeared. I ripped off VC++ ;-)
>
>I'll try later with a fresh installation.
>
>Henrik
>
>_________________________________________________________________
>Del din verden med MSN Spaces  http://spaces.msn.com
>
>_______________________________________________
>LLVM Developers mailing list
>LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev

_________________________________________________________________
Del din verden med MSN Spaces http://spaces.msn.com

Henrik Bach wrote:
> ----Original Message Follows----
> From: Jeff Cohen <jeffc at jolt-lang.org>
> Reply-To: jeffc at jolt-lang.org,        LLVM Developers Mailing List 
> <llvmdev at cs.uiuc.edu>
> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h':
> No    suchfileor directory
> Date: Thu, 23 Dec 2004 08:05:39 -0800
>
>> Out of curiosity, did it accept the solution and project files as is, 
>> or did it want to "upgrade" >them?  If the latter, I
cannot accept
>> any patches for those files because they would break VC++ >7.1
(which
>> in turn broke 7.0, which in turn broke 6.x).
>
>
> No, it didn't take the project files out of the box. It insisted to 
> upgrade the soulution and project files.
>
> Henrik.
Groan...  it's bad enough they keep breaking backwards compatibility, 
but what's much worse is that the upgrade is never 100% correct.  Builds 
are broken in subtle and hard to track down ways.  It's why VS upgrades 
get put off for as long as possible.  I won't even think of upgrading to 
Whidbey until several years after its release.

On Thu, 2004-12-23 at 08:40, Jeff Cohen wrote:
> Groan...  it's bad enough they keep breaking backwards compatibility, 
> but what's much worse is that the upgrade is never 100% correct. 
Builds
> are broken in subtle and hard to track down ways.  It's why VS upgrades
> get put off for as long as possible.  I won't even think of upgrading
to
> Whidbey until several years after its release.
Hopefully you won't have to. By then LLVM and XPS should be a suitable
replacement :)

Reid.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20041223/0d490423/attachment.sig>

Hi Jeff and Morten,

I was just wondering if below wisdom is true, why not prefix every solution 
and project file with VC71 in front of the file name to signal the case that 
it is only designed for that specific IDE/tool?

This gives us room for comming up with other solution and project files for 
another MS specific IDE/tool independt of each other.

Henrik.


----Original Message Follows----
From: Jeff Cohen <jeffc at jolt-lang.org>
Reply-To: jeffc at jolt-lang.org,        LLVM Developers Mailing List 
<llvmdev at cs.uiuc.edu>
To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
Subject: Re: [LLVMdev] VC++: Cannot open include file: 
'windows.h':No	suchfileor directory
Date: Thu, 23 Dec 2004 08:40:13 -0800

Henrik Bach wrote:
>----Original Message Follows----
>From: Jeff Cohen <jeffc at jolt-lang.org>
>Reply-To: jeffc at jolt-lang.org,        LLVM Developers Mailing List 
><llvmdev at cs.uiuc.edu>
>To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h':
No
>suchfileor directory
>Date: Thu, 23 Dec 2004 08:05:39 -0800
>
>>Out of curiosity, did it accept the solution and project files as is, or
>>did it want to "upgrade" >them?  If the latter, I cannot
accept any
>>patches for those files because they would break VC++ >7.1 (which in
turn
>>broke 7.0, which in turn broke 6.x).
>
>
>No, it didn't take the project files out of the box. It insisted to
upgrade
>the soulution and project files.
>
>Henrik.
Groan...  it's bad enough they keep breaking backwards compatibility, but 
what's much worse is that the upgrade is never 100% correct.  Builds are 
broken in subtle and hard to track down ways.  It's why VS upgrades get put 
off for as long as possible.  I won't even think of upgrading to Whidbey 
until several years after its release.

_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev

_________________________________________________________________
Del din verden med MSN Spaces  http://spaces.msn.com