building_your_application.htm
来自「acis说明文档」· HTM 代码 · 共 909 行 · 第 1/5 页
HTM
909 行
</dd></dl></dd><dd><b>Debug configuration: Debug Libraries</b></dd><dd><b>(Spatial arches: <tt>NT_V<strong class='error'>Failed to parse (Missing texvc executable; please see math/README to configure.): C_8</strong></dd></dl></li></ol><p>_DLLD</tt>, <tt>NT_NET_DLLD</tt>, <tt>NT_AMD_64_DLLD</tt>)</b></p><ol><li><dl><dd>For each of the following libraries, open "Properties" and change "Excluded from Build" to <b>No</b>.<dl><dd> <tt>3D ACIS DM Debug Lib</tt></dd><dd> <tt>3D ACIS PHL V5 Debug Lib</tt></dd></dl></dd></dl></li><li> Choose Build->Build <tt>acis3dt.exe</tt></li></ol><blockquote class="templatequote"><div><p><i><b>Note:</b> Once you have completed this step and if there are unresolved symbols at link time, then Visual Studio has not recognized that the libraries were added. Save and close the solution file, reopen it and rebuild. This should resolve the link error.</i></p></div></blockquote><a name="Building_on_UNIX"></a><h2> <span class="mw-headline"> Building on UNIX </span></h2><blockquote class="templatequote"><div><p><i><b>Note:</b> If you are relinking acis3dt against a HOOPS version other than 15.0, you must also rebuild the SpaHBridge and SpaHPart libraries using the projects/makefiles in src/ha_bridge and src/ha_part.</i></p></div></blockquote><ol><li> Set environment variables: <dl><dd>Set A3DT to your ACIS installation. </dd><dd>Set ARCH to the <a href="/r18/index.php/Architecture" title="Architecture">architecture</a> you would like to build, for example, aix4_so. </dd><dd>Set HOOPS_INSTALL_DIR to the location of your HOOPS installation, if applicable. </dd><dd>Set HOOPS_VER to the version of your HOOPS installation, if applicable.</dd></dl></li><li> Change your directory.<dl><dd><pre>cd $A3DT/scm/acis3dt</pre></dd></dl></li><li> Build the executable. <dl><dd>Not using a HOOPS installation:</dd><dd><pre>make TARGET=<target></pre></dd><dd>Using a HOOPS installation:</dd><dd><pre>make f makefile_hoops TARGET=<target></pre></dd><dd>where <tt><target></tt> is one of the following:<ul><li> <tt>ACIS</tt> - <a href="/r18/index.php/3D_ACIS_Modeler" title="3D ACIS Modeler">3D ACIS Modeler</a></li><li> <tt>ACIS_DM</tt> - 3D ACIS Modeler and 3D ACIS Deformable Modeling</li><li> <tt>ACIS_PHLV5</tt> - 3D ACIS Modeler and 3D ACIS PHL V5</li><li> <tt>ACIS_ALL</tt> - 3D ACIS Modeler, 3D ACIS Deformable Modeling and 3D ACIS PHL V5</li></ul></dd></dl></li><li>The executable (acis3dt) is created in <tt>$A3DT/bin/$ARCH</tt>.</li></ol><a name="Building_on_Macintosh"></a><h2> <span class="mw-headline"> Building on Macintosh </span></h2><ol><li> Open the Xcode project file in <tt><A3DT>:scm:acis3dt</tt>, where <tt>A3DT</tt> is your ACIS installation. The project contains targets that build slightly different configurations of the acis3dt application. The project supports two build styles, both of which work for each of the targets. The Development style builds with debug symbols on and optimization off. The Deployment style builds with debug symbols off and optimization level -O1. Upon opening the project for the first time, the active Build style is Development. The targets are:<ul><li> <tt>acis3dt</tt> - 3D ACIS Modeler using ACIS release mode macub libraries</li><li> <tt>acis3dt_d</tt> - 3D ACIS Modeler using ACIS debug mode macub libraries</li><li> <tt>acis3dt_dm</tt> - 3D ACIS Modeler and 3D ACIS Deformable Modeling using ACIS release mode macub libraries</li><li> <tt>acis3dt_dm_d</tt> - 3D ACIS Modeler and 3D ACIS Deformable Modeling using ACIS debug mode macub libraries</li><li> <tt>acis3dt_phlv5</tt> - 3D ACIS Modeler and 3D ACIS PHL V5 using ACIS release mode macub libraries</li><li> <tt>acis3dt_phlv5_d</tt> - 3D ACIS Modeler and 3D ACIS PHL V5 using ACIS debug mode macub libraries</li><li> <tt>acis3dt_all</tt> - 3D ACIS Modeler, 3D ACIS Deformable Modeling and 3D ACIS PHL V5 using ACIS release mode macub libraries</li><li> <tt>acis3dt_all_d</tt> - 3D ACIS Modeler, 3D ACIS Deformable Modeling and 3D ACIS PHL V5 using ACIS debug mode macub libraries</li></ul></li><li> Choose your desired build target using the Active Target drop down list.</li><li> Update settings regarding your HOOPS installation, if applicable. These settings must be updated in both build styles.<ol><li> Click the Info button in the main toolbar, or select File->Get Info.</li><li> Select the Build pane.</li><li> Select the desired configuration or select "All Configurations" from the Configuration drop down menu.</li><li> Select "Edit>Change Existing Settings" then change the two custom build settings HOOPS_INSTALL_DIR and HOOPS_VER.</li><li> Using the Active Build Style drop down list, change the build configuration from Development to Deployment and repeat the previous two steps.</li><li> Close the Info window.</li></ol></li><li> Click Build. Open the detailed build window (Build->Detailed Build Results) to view detailed build results, switch build style or switch the active build target.</li><li> The application bundle is placed in <tt><A3DT>/scm/acis3dt/build</tt>, which is Xcode's default build location. To change the destination location:<ol><li> In the Groups & Files window, select the project icon at the top of the window (titled acis3dt).</li><li> Click the Info button in the main toolbar, or select File->Get Info.</li><li> Select the General pane.</li><li> Change the "Place Build Products In" setting to "Separate location" and enter your desired location.</li></ol></li><li> Note that three custom phases have been added to the Xcode build sequence to prepare the acis3dt bundle for runtime. Hence, additional disc space is occupied by the library copies.<ol><li> The libtool table of contents update discussed below is performed in a <a href="/r18/index.php?title=Shell&action=edit" class="new" title="Shell">Shell</a> Script phase.</li><li> The HOOPS library is copied from <tt>$(HOOPS_INSTALL_DIR)/Dev_Tools/hoops_3dgs/lib</tt> to <tt>acis3dt*.app/Contents/MacOS.</tt></li><li> The ACIS dynamic libraries are copied from the ACIS bin directory to <tt>acis3dt*.app/Contents/MacOS</tt>.</li></ol></li></ol><a name="Note_Regarding_Building_and_Using_ACIS_Scheme_AIDE_Program_on_Macintosh"></a><h3> <span class="mw-headline"> Note Regarding Building and Using ACIS Scheme AIDE Program on Macintosh </span></h3><a name="ACIS_Dynamic_Libraries"></a><h4> <span class="mw-headline"> ACIS Dynamic Libraries </span></h4><p>ACIS dynamic libraries must be present in an application bundle's executable directory at runtime. Rather than installing an extra copy of the ACIS dynamic libraries inside the acis3dt application shipped with ACIS, your ACIS package supplies a script that creates relative links inside the acis3dt bundle pointing to each dynamic library in the bin/$ARCH directory. You must run this script before acis3dt can execute.</p><p>After installing ACIS, open a terminal window.cd $A3DT/bin/macub ./RUNFIRST.sh. where $A3DT is your ACIS installation.</p><a name="Scheme_Initialization_File"></a><h4> <span class="mw-headline"> Scheme Initialization File </span></h4><p>Note that the scheme initialization file, acisinit.scm, is not automatically loaded by the Scheme AIDE program. This file defines some commonly used <a href="/r18/index.php?title=Scheme_procedures&action=edit" class="new" title="Scheme procedures">scheme procedures</a>, such as zoom-all. On other platforms, Scheme AIDE looks for the file in either a path relative to the executable's location or a path relative to the current working directory. When running an application from the Finder on Mac OSX, neither of these <a href="/r18/index.php?title=Options&action=edit" class="new" title="Options">options</a> works.</p><p>To load the file, type the following command at the Scheme prompt:</p><pre class="source-scheme"><span class="br0">(</span><span class="kw1">load</span> <span class="st0">"$A3DT/scm/examples/acisinit.scm"</span><span class="br0">)</span></pre> <p>where </p><dl><dd><tt>$A3DT</tt> is your ACIS installation.</dd></dl><a name="Loading_acisinit.scm"></a><h4> <span class="mw-headline"> Loading acisinit.scm </span></h4><p>For the default toolkit applications that are provided with product installation, the acisinit.scm does not load automatically as it does on other platforms. The file, acisinit.scm is found in $A3DT/scm/examples/acisinit.scm, where $A3DT is the installation directory. You may load it after starting a Scheme session by using the command:load "<path the ACIS>/scm/examples/acisinit.scm"</p><a name="Scheme_Static_Libraries"></a><h4> <span class="mw-headline"> Scheme Static Libraries </span></h4><p>Prior to use, all static libraries must have their table of contents updated once using libtool. The libtool emits an error when linking the executable if the table of contents of an included static library is older than the library's creation date. This error occurs if the library has been copied without retaining its original creation date, although the table of contents of the library is not actually out of date. The acis3dt.xcode sample project performs this step during the build, after which the libraries can be linked into any application.</p><p>To link the static libraries into your application without running the acis3dt.xcode sample project, you must perform this step manually: </p><pre>for mylib in $A3DT/lib/$ARCH/*.a do libtool -static -o $mylib $mylib done</pre><p>where $A3DT is your ACIS installation and $ARCH is either macub or macub_debug.</p><a name="Building_the_HOOPS.2FACIS_Bridge"></a><h1> <span class="mw-headline"> Building the HOOPS/ACIS Bridge </span></h1><p>ACIS ships projects and makefiles on all platforms for rebuilding the HOOPS/ACIS Bridge and ACIS Deformable Modeling HOOPS. This section discusses how to build the bridge.</p><blockquote class="templatequote"><div><p><i><b>Note:</b> In order to rebuild the Spatial samples, you must add your license to the sample source code. The sample source file unlock_license.cpp contains a function <code>unlock_license()</code> which is called by every sample at startup. Modify this file to call your application license function.</i></p></div></blockquote><a name="HOOPS.2FACIS_Bridge_Projects_and_Makefiles"></a><h2> <span class="mw-headline"> HOOPS/ACIS Bridge Projects and Makefiles </span></h2><p>The HOOPS/ACIS Bridge libraries shipped with ACIS are linked against HOOPS 15.0. The source code for the HOOPS/ACIS Bridge is shipped with ACIS so that you may:</p><ul><li> view how the HOOPS/ACIS bridge is implemented</li><li> link against various versions of HOOPS other than version 15.0</li><li> customize the source code for other purposes as needed</li></ul><p>Projects and makefiles for rebuilding the two libraries in the bridge, SpaHPart and SpaHBridge, are included in the src/ha_bridge and src/ha_part directories. For those using ACIS Deformable Modeling, Spatial includes an additional set of projects for rebuilding the admhoops library in src/admhoops.</p><blockquote><i><b>WARNING:</b>If you are building a custom version of the HOOPS/ACIS Bridge, you must perform a rebuild when a new service pack is installed. This requirement results from the service pack's need to reinstall libraries linked against HOOPS 15.0 and to ensure that functionality changes in the bridge source code are incorporated into your bridge libraries.</i></blockquote><p>If you have used these projects in previous releases, you must note that the projects have been changed to support different versions of HOOPS. Thus, UNIX makefiles now require that the environmental variable, HOOPS_VER, be set. For the .NET 7.1 projects, the HOOPS V<strong class='error'>Failed to parse (Missing texvc executable; please see math/README to configure.): C_6</strong></p><pre>configurations (nt_i386) have been removed from the acis3dt, ha_bridge, ha_part, and admhoops projects. The project configurations have been renamed to reflect this change.</pre><a name="Building_the_SpaHPart.2C_SpaHBridge.2C_and_admhoops_Libraries_on_Windows"></a><h2> <span class="mw-headline"> Building the SpaHPart, SpaHBridge, and admhoops Libraries on Windows </span></h2><a name="Microsoft_Visual_C.2B.2B_6.0"></a><h3> <span class="mw-headline"> Microsoft Visual C++ 6.0 </span></h3><ol><li> Open a command prompt window. </li><li> Set the following environment variables<dl><dd>set <tt><b>A3DT</b></tt> to <tt><your ACIS R17 installation></tt>, for example: <tt>set A3DT=c:\Progra~1\Spatial\acisR17</tt></dd><dd><tt>set <b>HOOPS_INSTALL_DIR</b> to <your HOOPS installationdirectory> </tt></dd></dl></li><li> Open the desired project:<dl><dd><tt>cd %A3DT%\src\ha_bridge</tt>(or src\ha_part or src\admhoops) and then </dd><dd><tt>msdev ha_bridge.dsw</tt> (or ha_part.dsw or admhoops.dsw)</dd></dl></li><li> Choose the configuration (release/debug): <i>Win32 Release Win32 Debug</i> </li><li> Select from menu : <tt> Build->Set Active Configuration</tt> </li><li> Select from menu: <tt>Build->Build the library</tt></li></ol><a name="Microsoft_Visual_Studio_.NET_7.1"></a><h3> <span class="mw-headline"> Microsoft Visual Studio .NET 7.1 </span></h3><ol><li> Open a command prompt window. </li><li> Set the following environment variables<dl><dd>set <tt><b>A3DT</b></tt> to <tt><your ACIS R17 installation></tt>, for example, <tt>set A3DT=c:\Progra~1\Spatial\acisR17 </dd><dd>set <b>HOOPS_INSTALL_DIR</b> to <your HOOPS installationdirectory></tt> </dd></dl></li><li> Open the desired project: <dl><dd><tt>cd %A3DT%\src\ha_bridge</tt> (or src\ha_part or src\admhoops) and then </dd><dd><tt>devenv ha_bridge.sln</tt> (or ha_part.sln or admhoops.sln)</dd></dl></li><li> Choose one of these configurations:<dl><dd><i>Release</i> - Use with HOOPS version 10 or higher to link release ACIS to V<strong class='error'>Failed to parse (Missing texvc executable; please see math/README to configure.): C_7</strong></dd></dl></li></ol><p>.1 release HOOPS or</p><ol><li><dl><dd><i>Debug</i> - Use with HOOPS version 10 or higher to link debug ACIS to V<strong class='error'>Failed to parse (Missing texvc executable; please see math/README to configure.): C_7</strong></dd></dl></li></ol><p>.1 debug HOOPS. </p><ol><li> Select from menu: <tt>Build->Build the library</tt></li></ol><a name="Microsoft_Visual_C.2B.2B_8.0_.28NT_VFailed_to_parse_.28Missing_texvc_executable.3B_please_see_math.2FREADME_to_configure..29:_C_8.0A_and_NT_AMD_64.29"></a><h3> <span class="mw-headline"> Microsoft Visual C++ 8.0 (NT_V<strong class='error'>Failed to parse (Missing texvc executable; please see math/README to configure.): C_8</strong> and NT_AMD_64) </span></h3><ol><li> Open a command prompt window. </li><li> Set the following environment variables<dl><dd>set <tt><b>A3DT</b></tt> to <tt><your ACIS R17 installation></tt>, for example, <tt>set A3DT=c:\Progra~1\Spatial\acisR17 </dd><dd>set <b>HOOPS_INSTALL_DIR</b> to <your HOOPS installationdirectory></tt></dd></dl></li><li> Open the desired project:<dl><dd><tt>cd %A3DT%\src\ha_bridge</tt> (or src\ha_part or src\admhoops) and then </dd><dd><tt>devenv ha_bridge_amd_64.sln</tt> (or ha_part_amd_64.sln or admhoops_amd_64.sln) (for NT_AMD_64) or <dl><dd><tt>devenv ha_bridge_v<strong class='error'>Failed to parse (Missing texvc executable; please see math/README to configure.): c_8</strong></dd></dl></dd></dl></li></ol><p>.sln</tt> (or ha_part_v<strong class='error'>Failed to parse (Missing texvc executable; please see math/README to configure.): c_8</strong>.sln or admhoops_v<strong class='error'>Failed to parse (Missing texvc executable; please see math/README to configure.): c_8</strong>
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?