|Do you know where your variables are?|
|( #3333=superdoc: print w/replies, xml )||Need Help??|
Ok, to summarize our CB conversation. Linking to libc is all wrong. Forget that. The /Gf changes appear harmless. As for msvcrt7.lib I assume you are trying to statically link against that lib. Dont bother, dynamically link against it and you should be ok. Additional resources are available in the "full SDK" or in the .Net Framework which you will need installed from WU afaik.
Can I just say how aboslutely PHENOMENAL this is for Win32 Perl and Perl in general. Once we can get Perl to build on Win32 with the new compiler clean then the need for PPM's disappears. The arguments about different perl versions being built on different compilers should effectively disappear. The lack of Win32 portability due to no developers ahving compilers disappears. This is absolutely amazing stuff.
We need to begin a project to "enhance" the Perl packaging mechanisms to handle downloading and installing the C compiler on demand. And we need to do it IMO, FAST. Ill be working on this, I hope you'll help, and any other volunteers are very welcome.
Update: I successfulyl built A recent bleadperl (patch 22609) with the new compiler, all tests were good. Unfortunately i have the normal VC7 on my system as well as the free one. This may mean it used resources from the normal kit that it wouldnt be able to find on your system. Ill double check this later.
First they ignore you, then they laugh at you, then they fight you, then you win.
In reply to Re: Building Perl with the free MSVC tools