Re: [vos-d] struggling with Windows...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 14 Aug 2005, res wrote: Don't know if you have tried yet, but check out gdb-6.3 (from mingw.org, a bit down the downloads list). I had to do some (little) debugging recently, and while gdb-5.something failed to get CS plugin debug info, 6.3 worked well in this regard. Ok, good suggestion. I'll look into that. By the way, when I run anything in gdb, I get the following warning over and over and over again: SIGTRAP: Invalid Address specified to RtlFreeHeap( XX, XX ) I thought maybe it was the multiple-heaps issue with Windows DLLs, except that a) I can continue and it doesn't crash and b) I'm pretty sure mingw compiles everything against the same C runtime DLL (msvcrt.dll), so there should only *be* one heap. Have you ever seen this before? There are the Debugging Tools which also contain a GUI debugger, WinDbg. I never used it, though. Aha, I'll look for that. The VC 2003 Toolkit is limited in other regards, too. For example, it doesn't get shipped with the libraries to link with the DLL version of the C runtime (msvcr71.dll). If you google around, you'll find instructions and workarounds to use the VC Toolkit for a number of OSS projects - but it seems it's actually a bit of work to get the VC Toolkit properly support a project. What's the difference between msvcrt.dll and msvcr71.dll? I thought the latter is just a newer version shipped with the newer compiler, or is it more complicated than that? What limits do you mean? At least CrystalSpace compiles with it. There were some rough edges first, though, but I eventually sorted them out. Well, specifically the inability to add include search paths, so I couldn't point it at the Win32 SDK. I eventually googled and found the instructions on a Microsoft developers fucking BLOG (great documentation guys), but when I tried it it didn't work (although I didn't spend that much time tinkering with it). I would very much appreciate some hints on how to compile Crystal Space with VC++ Express Beta 2. [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDAL8GaeHUyhjCHfcRAp8aAJ92nMVuqajQwGtmt5RU4aNFQg5AiQCfTpfu JxhmBL9/T0FP5NRAbjVMQG4= =FjBl -END PGP SIGNATURE- ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] struggling with Windows...
msvcrt.dll is the old pre-.net dll, msvcr71.dll is the .net dll The import libraries have teh same name in each case (msvcrt.lib, msvcprt.lib) but point towards a differently named dll, one of those above, depending on the compiler version.On 8/15/05, Peter Amstutz [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE-Hash: SHA1On Sun, 14 Aug 2005, res wrote: Don't know if you have tried yet, but check out gdb-6.3 (from mingw.org, a bit down the downloads list). I had to do some (little) debugging recently, and while gdb-5.something failed to get CS plugin debug info, 6.3 worked well in this regard.Ok, good suggestion.I'll look into that.By the way, when I run anything in gdb, I get the following warning over and over and over again:SIGTRAP:Invalid Address specified to RtlFreeHeap( XX, XX )I thought maybe it was the multiple-heaps issue with Windows DLLs, exceptthat a) I can continue and it doesn't crash and b) I'm pretty sure mingw compiles everything against the same C runtime DLL (msvcrt.dll), so thereshould only *be* one heap.Have you ever seen this before? There are the Debugging Tools which also contain a GUI debugger, WinDbg. I never used it, though.Aha, I'll look for that. The VC 2003 Toolkit is limited in other regards, too. For example, it doesn't get shipped with the libraries to link with the DLL version of the C runtime (msvcr71.dll). If you google around, you'll find instructions and workarounds to use the VC Toolkit for a number of OSS projects - but it seems it's actually a bit of work to get the VC Toolkit properly support a project.What's the difference between msvcrt.dll and msvcr71.dll?I thought thelatter is just a newer version shipped with the newer compiler, or is itmore complicated than that? What limits do you mean? At least CrystalSpace compiles with it. There were some rough edges first, though, but I eventually sorted them out.Well, specifically the inability to add include search paths, so I couldn't point it at the Win32 SDK.I eventually googled and found theinstructions on a Microsoft developers fucking BLOG (great documentationguys), but when I tried it it didn't work (although I didn't spend that much time tinkering with it).I would very much appreciate some hints on how to compile Crystal Spacewith VC++ Express Beta 2.[ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED]][Lead Programmer][Interreality Project][Virtual Reality for the Internet][ VOS: Next Generation Internet Communication][ http://interreality.org ][ http://interreality.org/~tetron ][ pgpkey:pgpkeys.mit.edu18C21DF7 ]-BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux)iD8DBQFDAL8GaeHUyhjCHfcRAp8aAJ92nMVuqajQwGtmt5RU4aNFQg5AiQCfTpfuJxhmBL9/T0FP5NRAbjVMQG4==FjBl-END PGP SIGNATURE-___ vos-d mailing listvos-d@interreality.orghttp://www.interreality.org/cgi-bin/mailman/listinfo/vos-d ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] struggling with Windows...
It's almost like Microsoft is trying to discourage distributed development (typical of free software) Yeah, it sucks, but hey theres a lot of people out there using Windows, and thats not going to change overnight. Hi Hugh, haven't heard from you in a while.Last I heard you had been sucked into the World of Warcraft?:-) Back in Paris, took my old job back for a few months for the summer. Hugh On 8/15/05, Peter Amstutz [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE-Hash: SHA1Hi Hugh, haven't heard from you in a while.Last I heard you had beensucked into the World of Warcraft?:-)On Sun, 14 Aug 2005, Hugh Perkins wrote: windebug works ok.Its free, and it basically does everything that the full Visual Studio debugger does.Obviously it only works with msvc-compiled objects.Well, it's still a step up from no debugger at all. You can get the C runtime by installing .net runtime followed by .net sdk (in that order).It will appear in c:\program files\microsoft .net sdk (something like that, but definitely on C:, in program files), independent of the directory you actually chose to install the .net sdk into. The C++ runtime is a little trickier to get.Theres a CERN site that has the import library for download. http://root.cern.ch/root/Procedure/Procedure%20to%20install%20the%20free%20Microsoft%20Visual%20C.htm Argh.Why do they make this so complicated? Other than that, the visual C++ toolkit is the full, optimizing compiler that comes with Visual Studio .Net professional/enterprise. You can use Cygwin/mingw to use msvc compiler from a configure file, by using cccl.On the other hand cygwin and mingw have unresolved issues with forking not releasing memory on certain windows xp machines (independent of which compiler is used), so using gnumake could be more reliable.I tried cccl and couldn't get it to do anything useful, so what I ended updoing was writing a makefile script that ran from automake files and produced nmake files.A nice hack and actually worked pretty well, butall in all nmake is fairly useless and most people would prefer to avoidit.What might make more sense would be to do something similar that automatically produces visual studio project files.Of course, then youget into the issue of what _version_ project files you generate, since VS7.1 is not backwards compatible with 7.0, which is not backwards compatible with 6.0.I don't know if VS 8.0 (.NET 2005) projects arecompatible with 7.1. Theres some detailed info on the Visual C++ Toolkit at http://manageddreams.com/osmpwiki/index.php?title=Notes_on_Microsoft_Visual_CPP_Toolkit_2003It's almost like Microsoft is trying to discourage distributed development(typical of free software) by making it impossible for any given group of people to be able to collaborate unless they're using exactly the sameversion of exactly the same compiler... ***Argh!!!***[ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED]][Lead Programmer][Interreality Project][Virtual Reality for the Internet][ VOS: Next Generation Internet Communication][ http://interreality.org ][ http://interreality.org/~tetron ][ pgpkey:pgpkeys.mit.edu18C21DF7 ]-BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux)iD8DBQFDAMIpaeHUyhjCHfcRAiUjAJ4jE8oVy22WVcd+TO31Z4ZZb43oBQCeISPer6OBWp6avJfaH/OKT9rWeV4==/ecl-END PGP SIGNATURE-___ vos-d mailing listvos-d@interreality.orghttp://www.interreality.org/cgi-bin/mailman/listinfo/vos-d ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] struggling with Windows...
On 15.08.2005 18:12, Peter Amstutz wrote: SIGTRAP: Invalid Address specified to RtlFreeHeap( XX, XX ) I thought maybe it was the multiple-heaps issue with Windows DLLs, except that a) I can continue and it doesn't crash and b) I'm pretty sure mingw compiles everything against the same C runtime DLL (msvcrt.dll), so there should only *be* one heap. Have you ever seen this before? Never seen that. Perhaps the additional heap comes from some driver or so. What's the difference between msvcrt.dll and msvcr71.dll? I thought the latter is just a newer version shipped with the newer compiler, or is it more complicated than that? Well, basically it is a newer version, but who knows what changes they made to the runtime, so I wouldn't hold my breath for compatibility. Well, specifically the inability to add include search paths, so I couldn't point it at the Win32 SDK. I eventually googled and found the instructions on a Microsoft developers fucking BLOG (great documentation guys), but when I tried it it didn't work (although I didn't spend that much time tinkering with it). Yeah, pretty annoying bug. They even give instructions somewhere on how to use the Platform SDK with VCExpress and say that you should add the Platform SDK paths there - so I don't think not being able to edit paths was intentional... still a rather serious flaw. I ended up editing the relevant configuration file manually - Documents and Settings\YourNameHere\Local Settings\Application Data\Microsoft\VCExpress\8.0\VCComponents.dat . I would very much appreciate some hints on how to compile Crystal Space with VC++ Express Beta 2. Once you have the PSDK set up, open the VC 7 projects, have them converted, and hit Build Solution. -f.r. signature.asc Description: OpenPGP digital signature ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d