question for anyone out there familiar with building an HLC executable...
in chapter 2, sec. 2.2 of the Progress External Program Interface for Version 8, there a figure (2-1) that shows Progress Object files being linked into the build of an HLC executable.
Why in the world would you include Progress Object Code in the HLC exectuable? wouldn't you just include C code and the dispatch routine and then run the created executable ... which will bring up a progress session from which you can run your progress object code? I can't figure out why they mention including progress object code in the executable.
After this fig, they give 4 steps to build an executable. step 4 again mentions including progress object code in the link script to build the executable. anyone out there that can explain this?
tia,
shane.
in chapter 2, sec. 2.2 of the Progress External Program Interface for Version 8, there a figure (2-1) that shows Progress Object files being linked into the build of an HLC executable.
Why in the world would you include Progress Object Code in the HLC exectuable? wouldn't you just include C code and the dispatch routine and then run the created executable ... which will bring up a progress session from which you can run your progress object code? I can't figure out why they mention including progress object code in the executable.
After this fig, they give 4 steps to build an executable. step 4 again mentions including progress object code in the link script to build the executable. anyone out there that can explain this?
tia,
shane.