Home
| Search
| C & C++
| D
| DMDScript
| News Groups
| index
| prev
| next
|
Archives
D Programming
DD.gnu digitalmars.D digitalmars.D.bugs digitalmars.D.dtl digitalmars.D.dwt digitalmars.D.announce digitalmars.D.learn digitalmars.D.debugger C/C++ Programming
c++c++.announce c++.atl c++.beta c++.chat c++.command-line c++.dos c++.dos.16-bits c++.dos.32-bits c++.idde c++.mfc c++.rtl c++.stl c++.stl.hp c++.stl.port c++.stl.sgi c++.stlsoft c++.windows c++.windows.16-bits c++.windows.32-bits c++.wxwindows digitalmars.empire digitalmars.DMDScript |
c++ - Re: USE16/USE32.. ah ha!
Well, looks like I was right on my hunch about the def file. Seems to me that dmc defaults to 32bit linking if no memory model is specified, however if using a def file, if EXETYPE is not specified win 3.11 code is assumed. Adding "EXETYPE nt" fixed (one of) my problems. Now when I run the created executable I get an error message: Application failed to initialize properly(0xc0000005). Looks like it's to figure out this one now.. :-/ May 08 2003
Yeah, there are some tweaks the IDDE would prevent you from... For one, it would create the .DEF file for you with all the necessary lines in it... ;-) What kind of application (MFC, Win32-API, ???) are you trying to build? Jan Darren Fitzpatrick wrote:Well, looks like I was right on my hunch about the def file. Seems to me that dmc defaults to 32bit linking if no memory model is specified, however if using a def file, if EXETYPE is not specified win 3.11 code is assumed. Adding "EXETYPE nt" fixed (one of) my problems. Now when I run the created executable I get an error message: Application failed to initialize properly(0xc0000005). Looks like it's to figure out this one now.. :-/ May 08 2003
|