At http://www.devside.net we have been building Perl 5.8.x for some time now with VS.NET 2002 (that links against msvcr70.lib and uses the msvcr70.dll that comes with .NET 1.0/1.0a)

We have a guide for building Perl under win32 with VC++...
(it is a very simple task)

http://www.devside.net/web/server/windows/perl
http://www.devside.net/web/server/windows

I’m not exactly sure what the problem here is, but to clarify a point...

MSVCRT.dll is the Microsoft C Runtime Library.
If you use MS VC++, your programs will only link and run with specific versions of this file; managed code or not.
(the version of MSVCRxx used by the compiler cannot be changed or specified by the user)

VS98 links only against msvcrt.lib (or maybe even an earlier version)
VS.NET 2002 links only against msvcr70.lib
VS.NET 2003 links only against msvcr71.lib

I would assume that the free MS VC++ 2003 toolkit would only link against MSVCR71.lib

msvcr70.dll is part of .NET 1.0(a)
msvcr71.dll is part of .NET 1.1

Please excuse me if I missed a point, it just seemed to me that there was a difficulty with building Perl under win32 with VC++ above 6.0 in this thread. If someone could clarify, I would be grateful.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.