huilin@hpindda.HP.COM (Hui Lin Lim) (02/15/89)
Does anyone know if QuickC 2.0 can be used with the Windows SDK
2.1 now that it's supposed to support all the different memory
models? I'm trying to save while moving into Windows
programming.
Hui-Lin Lim
ARPA: huilin%hpda@hplabs.hp.com
UUCP: {ucbvax,hplabs}!hpda!huilin
Phone: (408)447-2835dennis@se-sd.sandiego.ncr.com (Dennis Foster) (02/16/89)
In article <40130003@hpindda.HP.COM> huilin@hpindda.HP.COM (Hui Lin Lim) writes: >Does anyone know if QuickC 2.0 can be used with the Windows SDK >2.1 now that it's supposed to support all the different memory >models? I'm trying to save while moving into Windows >programming. QuickC 2.0 will not work for Windows. The problem is not one of memory models, but one of generating the proper calling sequences for windows programs. The MS C compiler generates special function prologue and epilogue code that QuickC (or Turbo C, Aztec C, ...) cannot generate.
dick@venera.isi.edu (Richard Gillmann) (02/18/89)
In article <1782@se-sd.sandiego.ncr.com> dennis@se-sd.sandiego.NCR.COM (Dennis Foster(AEP)) writes: >In article <40130003@hpindda.HP.COM> huilin@hpindda.HP.COM (Hui Lin Lim) writes: >>Does anyone know if QuickC 2.0 can be used with the Windows SDK >>2.1 now that it's supposed to support all the different memory >>models? I'm trying to save while moving into Windows >>programming. > >QuickC 2.0 will not work for Windows. The problem is not one of memory >models, but one of generating the proper calling sequences for windows >programs. The MS C compiler generates special function prologue and epilogue >code that QuickC (or Turbo C, Aztec C, ...) cannot generate. I have gotten QuickC to generate a proper Windows program. The QuickC code and libraries are very similar to the optimizing compiler's. The problem is that the QuickC libraries are not quite right for Windows. You can fix that by installing the MS C 5.1 libraries instead. To do this, you install QuickC 2.0, then install MS C 5.1 (using the same directories), then you install the Windows SDK. You must use the command line interface to the QC compiler, too. But since you need the MS C 5.1 libraries you won't save any money this way.