Watch, Follow, &
Connect with Us
Public Report
Report From: C++BuilderX/IDE/Build tools    [ Add a report in this area ]  
Report #:  6200   Status: Reported
TASM32 not included as build tool in Borland tool chain
Project:  C++BuilderX/BC++ 2005 Build #:  1786
Version:    1.0 Submitted By:   Justin Nye
Report Type:  Basic functionality failure Date Reported:  10/15/2003 3:06:16 AM
Severity:    Commonly encountered problem Last Updated: 10/17/2003 3:25:34 AM
Platform:    All platforms Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (1 Total Rating)
5.00 out of 5
Total Votes: 2
Although tasm32.exe is included with CBuilderX it is not included as a build tool.  Adding tasm32.exe as an external build tool is possible and the .asm files are then assembled, however the resulting .obj files are not passed on to the linker.
Steps to Reproduce:
Add an .asm file to a project.

Ivan Tsybankov at 10/9/2004 10:15:09 PM -
The only way I know is to create your own .tool file for tasm32 and modify toolset you'd want to use with it. For example, if you want to use 'Borland Win32 Compiler Tools' toolset with tasm32 ,.tool file
must contain at least two options in optionparamgroup(tag name) : one with infoid(tag) set to input
and another with infoid set to output. To redirect assembler's output to linker's input this option
(with infoid set to output) also must have a parameter inputid(tag) set to objinput. Example:

<param key="outfiles" type="filelist" limit="1">

<name>Output filename</name>

<desc>Output filename</desc>

<presep> </presep>


<separator> </separator>

<-- this means that there

(in command line)IDE places the name

for output file

<-- output treats as objinput


linker adds objinput to its input (from ilink32.tool):

<!-- expected parameters on the command line -->

<param key="objfiles" type="filelist">

<name>Object files</name>

<desc>List of object files</desc>

<presep> </presep>


<separator> </separator>



<--files treated as objinput placed here

another toolsets can have other types of connection between compiler and linker.
There is another way to solve the problem - you must explicitly add .obj file (the result of compiling .asm file) to your project.

Server Response from: ETNACODE01