Answers Database
V1.5, V1.4 COREGEN: How VLLINK.BATand VLLINK are invoked by the COREGEN GUI in v1.4 and v1.5 / debugging problems with VLLINK
Record #3625
Product Family: Software
Product Line: Coregen
Product Part: Coregen
Product Version: c1_5
Problem Title:
V1.5, V1.4 COREGEN: How VLLINK.BATand VLLINK are invoked by the COREGEN GUI in v1.4 and v1.5
/ debugging problems with VLLINK
Problem Description:
Urgency: standard
General Description:
How VLLINK.BAT is invoked by the COREGEN GUI in the
1.4 and 1.5 releases /
debugging problems with VLLINK
Solution 1:
In the 1.5 release, the VLLINK.BAT file is launched
using a new tool called "xstart". Because it is invoked using
xstart, invoking the batch file does not cause a separate DOS
window to pop up to run VLLINK.
In general, if you are doing manual debugging of problems
associated with Viewlogic symbol or WIR file generation in
any COREGen release, you can simply execute the VLLINK batch
file directly. The only thing that the xstart program does
in COREGen 1.5 is standardize the interface and redirect the
output of the command.
However, if you need to run the xstart program manually
for some reason, you can use the same command line that is
issued from within COREGen (the following is a single
command line):
coregen/bin/win/xstart.exe vllink.log coregen/bin/win/vllink.bat
<module_name> <project_path> <project_drive> <proser_path> <target_architecture>
<library_alias>
Solution 2:
On Workstations:
coregen/bin/win/vllink <comp_name> <project_path> <powerview_path> <target_architecture> <project_li
brary_name>
End of Record #3625 - Last Modified: 07/29/99 19:22 |
