📄 main41.htm
字号:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta name="GENERATOR" content="Quadralay WebWorks Publisher Professional Edition 6.0.5">
<meta name="TEMPLATEBASE" content="noindex_htm">
<meta name="LASTUPDATED" content="12/04/03 16:47:07">
<title>8.2 ST Visual Develop</title>
<STYLE TYPE="text/css">
<!--
span.Signal { text-transform: uppercase; font-family: Verdana }
-->
</STYLE>
</head>
<body link="#3366CC" vlink="#9999CC" text="#000000" alink="#0000CC" bgcolor="#FFFFFF"
background="images/backgrnd.gif">
<p><img src="images/stlogo.gif" width="106" height="83" align="left"
alt="logo here!"> </p>
<table border="0" align="right" cellpadding="0" cellspacing="0">
<tr>
<td><a href="a_delman.htm"><img src="images/navtoc.gif" width="84" height="23"
border="0" alt="TOC"></a></td>
<td><a href="main40.htm"><img src="images/navprev.gif" width="80" height="23"
border="0" alt="PREV"></a></td>
<td><a href="main42.htm"><img src="images/navnext.gif" width="83" height="23"
border="0" alt="NEXT"></a></td>
</tr>
</table>
<p><br clear="all">
</p>
<hr align="left">
<blockquote>
<h2>
<a name="1218284"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">8.2 ST Visual Develop</font>
</h2><hr>
<h3>
<a name="1220781"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">8.2.1 Starting st20dev</font>
</h3>
<p>
<a name="1222759"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">ST Visual Develop can started from the desktop shortcut, by double clicking on the executable or by typing <font size=2 face=Courier><strong>st20dev</strong></font> at the command line. <strong>st20dev</strong> supports the same command line options as <strong>st20run</strong>.</font>
</p>
<h3>
<a name="1222756"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">8.2.2 Windows registry increase in size</font>
</h3>
<p>
<a name="1222762"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">A bug existed in R2.0.4 where the registry would drastically increase in size causing ST Visual Develop to become very slow to respond (logged as INSbl20481). This has been fixed in this release.</font>
</p>
<h3>
<a name="1222746"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">8.2.3 Using st20dev with existing build systems</font>
</h3>
<p>
<a name="1222781"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">There are several approaches to using a ST Visual Develop in conjunction with existing build system environments. These are detailed below.</font>
</p>
<h3>
<a name="1222751"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">Complete import of a project</font>
</h3>
<p>
<a name="1222811"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">ST Visual Develop has the notion of projects, and a dependency chain of projects may be constructed. It is anticipated that a master project will exist with a set of dependencies. When the master project is built the final LKU or ROM image is created. When a sub-project is built a library is created which is linked into the final executable when building the master project.</font>
</p>
<p>
<a name="1222816"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">Each project must be created manually, and file sets added to each using the Windows 'multiple selection' idiom from the Open dialog.</font>
</p>
<h3>
<a name="1222752"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">Partial import of a project</font>
</h3>
<p>
<a name="1222833"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">It may be undesirable to add all the files in an application into ST Visual Develop projects. A partial solution may be adopted where the final image is linked by <strong>st20dev</strong> but existing libraries are built by calling an external <strong>make</strong> utility. This can be achieved by creating projects, one for each library in the application, which 'wraps' an existing makefile. Details of how to create a project from a makefile are given in the <em>Creating a new project</em> section of the <em>Working with projects</em> chapter of the <em>ST20 Embedded Toolset User Manual</em>. Individual makefile based projects may be imported into a native <strong>st20dev</strong> project to gain the full benefits of the IDE.</font>
</p>
<p>
<a name="1222839"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">A simple example workspace '<font size=2 face=Courier><strong>wrap_make.stw</strong></font>' exists in the examples <font size=2 face=Courier><strong>\st20dev\projects_and_makefiles</strong></font>爏ubdirectory under the toolset installation directory.</font>
</p>
<p>
<a name="1222843"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">A bug exists whereby <strong>make</strong> is not called for a makefile-wrapped project once the library has been built for the first time. This is logged as INSbl20797. The work around is to manually delete the library (<font size=2 face=Courier><strong>.lib</strong></font>) file, prior to starting a build.</font>
</p>
<h3>
<a name="1222753"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">Using the existing build methodology</font>
</h3>
<p>
<a name="1222852"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">ST Visual Develop may be used as a debugger and a source editor without importing existing makefile-based projects into the ST Visual Develop project environment. In such a scenario, existing projects should be built using the current, established build methodology (such as running a make utility from the command console), and the LKU or ROM image produced then debugged with <strong>st20dev</strong>.</font>
</p>
<h3>
<a name="1222775"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">Debugging earlier binary images</font>
</h3>
<p>
<a name="1222863"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">Binary images (both LKUs and ROMs) built with R1.9.6 may be debugged with this release.</font>
</p>
<h3>
<a name="1223508"> </a><font color="#003366" face="Verdana, Arial, Helvetica, sans-serif">8.2.4 Debug working folder</font>
</h3>
<p>
<a name="1223511"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">If a workspace is loaded from the command line, for example: </font>
</p>
<a name="1223535"> </a><font size=2 face=Courier><strong>st20dev example.stw<br></strong></font>
<p>
<a name="1223536"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">the <strong>Debug working folder</strong> is set to the current working directory.</font>
</p>
<p>
<a name="1223513"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">This may need to be changed manually (in the Workspace settings dialog) to specify the directory in which the binary image (LKU or DBG file) exists (for example, <font size=2 face=Courier><strong>Debug</strong></font>).</font>
</p>
<p>
<a name="1223517"> </a><font size=2 face="Verdana, Arial, Helvetica, sans-serif">If using the command line interface to <strong>st20dev</strong> to run the <strong>st20dev</strong> examples supplied with the toolset, this change will be necessary. This bug is logged as INSbl20981.</font>
</p>
</blockquote>
<hr>
<table border="0" align="left" cellpadding="0" cellspacing="0">
<tr>
<td><a href="a_delman.htm"><img src="images/navtoc.gif" width="84" height="23"
border="0" alt="TOC"></a></td>
<td><a href="main40.htm"><img src="images/navprev.gif" width="80" height="23"
border="0" alt="PREV"></a></td>
<td><a href="main42.htm"><img src="images/navnext.gif" width="83" height="23"
border="0" alt="NEXT"></a></td>
</tr>
</table>
<font size=1 face="Verdana, Arial, Helvetica, sans-serif"> © 2001, 2002, 2003 STMicroelectronics. All Rights Reserved.<br>
ADCS 7257995G</font>
</body>
</html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -