On 11/13/2015 08:40 AM, Jeff Law wrote:
On 11/10/2015 11:16 AM, Andris Pavenis wrote:
One may need to execute extra steps after linking program. This is required
for example for DJGPP to run stubify.exe on file generated by linker.
The only way how to achieve was to use LINK_COMMAND_SPEC. It
On 11/10/2015 11:16 AM, Andris Pavenis wrote:
One may need to execute extra steps after linking program. This is required
for example for DJGPP to run stubify.exe on file generated by linker.
The only way how to achieve was to use LINK_COMMAND_SPEC. It would be
much easier
and less error prone
On 11/10/2015 09:30 PM, Andris Pavenis wrote:
On 11/10/2015 11:20 PM, Jeff Law wrote:
On 11/10/2015 11:16 AM, Andris Pavenis wrote:
One may need to execute extra steps after linking program. This is
required
for example for DJGPP to run stubify.exe on file generated by linker.
The only way
One may need to execute extra steps after linking program. This is required
for example for DJGPP to run stubify.exe on file generated by linker.
The only way how to achieve was to use LINK_COMMAND_SPEC. It would be much
easier
and less error prone to use new macro POST_LINK_SPEC introduced in
On 11/10/2015 11:16 AM, Andris Pavenis wrote:
One may need to execute extra steps after linking program. This is required
for example for DJGPP to run stubify.exe on file generated by linker.
The only way how to achieve was to use LINK_COMMAND_SPEC. It would be
much easier
and less error prone
On 11/10/2015 11:20 PM, Jeff Law wrote:
On 11/10/2015 11:16 AM, Andris Pavenis wrote:
One may need to execute extra steps after linking program. This is required
for example for DJGPP to run stubify.exe on file generated by linker.
The only way how to achieve was to use LINK_COMMAND_SPEC. It
