On Wed, Mar 15, 2006 at 11:24:17AM +0000, Steve Hay wrote: > Steve Peters wrote: > >+# With .NET 1.1 and 2.0, setargs.obj is not available with the .NET SDK. > >It > >+# only comes with Visual Studio 2003 and Visual Studio 2005. > > This is not quite true (at least of .NET 1.1) -- setargs.c is supplied, > so setargs.obj can be compiled from it.
Hmmm....I didn't get one with my .NET 1.1 SDK, so it might have been a timing issue on my part. Still, as a macro, it can be defined on the command line, so it can be enabled. On the other hand, it isn't like we've had that many complaints over the past couple of years... > > People building perl with "MSVC70FREE" are instructed to do this in the > section entitled "Microsoft Visual C++ Toolkit 2003" in the README.win32. > > The README.win32 could also do with updating to mention experimental > support for the new compilers. I'll note the current support (or lack thereof :) ) for the .NET 2.0 compilers in a few minutes. > > Also, could you please keep win32/makefile.mk in sync with any changes > that you make in win32/Makefile. Thanks! Understood. I just wanted to get it working in one Makefile before I set about making the rest work. Currently, .NET 2.0 support isn't there yet. Work to add the manifest files to all the EXEs still needs to be done. It doesn't look all that complicated, but these groundwork issues needed to be handled first before setting out to that task. I also need to find out if the assemblies/DLLs need to have manifests embedded as well. The volume of deprecation warnings while compiling Perl with .NET 2.0 is also troubling, but I can at least build a perl.exe with minimal effort. Steve Peters [EMAIL PROTECTED]
signature.asc
Description: Digital signature
