"Rainer Schuetze" <r.sagita...@gmx.de> wrote in message news:jit3hk$tgb$1...@digitalmars.com... > > A good step forward would be a better separation of the object file format > from the target OS and the host OS. Removing that preprocessor hell is > needed anyway if you want to switch between object file formats by a > command line switch. > In addition, it would be pretty nice if you could at least compile with > predefined version OSX, even if you are working on Windows. >
Yeah, this would be nice. >> Generating Microsoft coff objects means deciphering the spec to see what >> everything should look like, generating every kind of entry with msvc to >> see >> what it _actually_ does, then translating all the record/fixup/section >> types >> from omf to the coff equivalents. With this (and maybe updates to the >> runtime to use msvc's instead of dmc's c runtime) you have 32 bit coff on >> windows. > > Don't forget debug info: as far as I can tell, the Microsoft linker > accepts codeview debug info in the object file, you don't have to write > pdb files. From my experience with cv2pdb, the debug records are a > straight forward extension of the debug info currently written by dmd. (I did forget it) But that's great! Not having to add a new debug info format can only be a good thing.
