Hi Jaap,

27 May 96 11:22, Jaap Keuter wrote to All:

 JK> The only thing missing is an IPFC replacement

I don't think you'll be able to find one, but the money paid for DevCon is
well-spend money. That's for sure!

 JK>    ICC.EXE {at}<<
 JK>  /B" /de /nologo /m:full"
 JK>  /Fe"$(EXECUTABLE)" /Fm"$(MAPFILE)" $(DEFFILE)
 JK> $(OBJECT1)
 JK> $(OBJECT2)
 JK> $(OBJECT3)
 JK> $(OBJECT4)
 JK> $(COMMON)
 JK> <<
 JK>    RC $(RESOURCE) $(EXECUTABLE)
 JK>    MAPSYM $(MAPFILE)

This part invokes the linker (LINK386.EXE) through ICC. The prime reason to
use ICC instead of just calling LINK386 is to my knowledge that ICC
resolves any template-definitions (if flag /Tdp is used, ie.).

All options between the quotes in /B"options" are passed on to
LINK386 as-is.
/Fe"name" is used to tell LINK386 the name of the executable
/Fm"name" "    "   "   "     "    
"    "   "  "  map-file

RC binds the resources to the EXE - I think that EMX uses another approach,
but I'm not sure.

MAPSYM transform the MAP-file into a SYM-file for when you want to debug
you program with the kernel debugger (I doubt it ;-)


Yours,
  Dufva/2

--- GoldED/2 2.50+