Building Your Application

Note: The SPAha_bridge, SPAha_part, and admhoops DLLs shipped with ACIS were built with HOOPS version 17.0, arch nt_x64_vc80 (NT_AMD_64 with VC8.0), arch nt_i386_vc80 (NT_VC8 with VC8.0), arch nt_x64_vc90 (NT_VC9_64 with VC9.0), arch nt_i386_vc90 (NT_VC9 with VC9.0), arch nt_x64_vc90 (NT_VC10_64 with VC9.0), and arch nt_i386_vc90 (NT_VC10 with VC9.0).

1. Open a command prompt window.
2. Set environment variables:

   set A3DT to your ACIS installation: for example,

   SET A3DT=c:\Progra~1\Spatial\acisR20

   set HOOPS_INSTALL_DIR to your HOOPS installation directory, if applicable

3. Open the project file:

   cd %A3DT%\scm\acis3dt

   devenv acis3dt_amd_64.sln (NT_AMD_64)

   devenv acis3dt_vc8.sln (NT_VC8)

   devenv acis3dt_vc9_64.sln (NT_VC9_64)

   devenv acis3dt_vc9.sln (NT_VC9)

   devenv acis3dt_vc10_64.sln (NT_VC10_64)

   devenv acis3dt_vc10.sln (NT_VC10)

4. Choose one of the two available configurations: Release or Debug.
5. Add optional ACIS products (if applicable)

   Open "Properties" for ACIS3DT

   Select C/C++ - Preprocessor; Add:

   ACIS_DM (for 3D ACIS Deformable Modeling)

   ACIS_PHLV5 (for 3D ACIS PHL V5)

6. Add the corresponding library.

   Release configuration: Release Libraries

   (Spatial arches: NT_VC8_DLL, NT_AMD_64_DLL, NT_VC9_DLL, NT_VC9_64_DLL, NT_VC10_DLL, NT_VC10_64_DLL)

   For each of the following libraries, open "Properties" and change "Excluded from Build" to No.

   3D ACIS DM Release Lib

   3D ACIS PHL V5 Release Lib

   Debug configuration: Debug Libraries

   (Spatial arches: NT_VC8_DLLD, NT_AMD_64_DLLD, NT_VC9_DLL, NT_VC9_64_DLL, NT_VC10_DLL, NT_VC10_64_DLL)

   For each of the following libraries, open "Properties" and change "Excluded from Build" to No.

   3D ACIS DM Debug Lib

   3D ACIS PHL V5 Debug Lib

7. Choose Build>Build acis3dt.exe

Note: 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.

Note: If you are relinking acis3dt against a HOOPS version other than 17.0, you must also rebuild the SpaHBridge and SpaHPart libraries using the projects or makefiles in src/ha_bridge and src/ha_part.

1. Set environment variables:

   Set A3DT to your ACIS installation.

   Set ARCH to the architecture you would like to build, for example, aix4_so.

   Set HOOPS_INSTALL_DIR to the location of your HOOPS installation, if applicable.

   Set HOOPS_VER to the version of your HOOPS installation, if applicable.

2. Change your directory.

   cd $A3DT/scm/acis3dt

3. Build the executable.

   If not using a HOOPS installation:

   make TARGET=<target>

   If using a HOOPS installation:

   make –f makefile_hoops TARGET=<target>

   where <target> is one of the following:

   • ACIS - 3D ACIS Modeler
   • ACIS_DM - 3D ACIS Modeler and 3D ACIS Deformable Modeling
   • ACIS_PHLV5 - 3D ACIS Modeler and 3D ACIS PHL V5
   • ACIS_ALL - 3D ACIS Modeler, 3D ACIS Deformable Modeling and 3D ACIS PHL V5

4. The executable (acis3dt) is created in $A3DT/bin/$ARCH.

1. Open the Xcode project file in <A3DT>:scm:acis3dt, where A3DT 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:
   • acis3dt - 3D ACIS Modeler using ACIS release mode macub libraries
   • acis3dt_d - 3D ACIS Modeler using ACIS debug mode macub libraries
   • acis3dt_dm - 3D ACIS Modeler and 3D ACIS Deformable Modeling using ACIS release mode macub libraries
   • acis3dt_dm_d - 3D ACIS Modeler and 3D ACIS Deformable Modeling using ACIS debug mode macub libraries
   • acis3dt_phlv5 - 3D ACIS Modeler and 3D ACIS PHL V5 using ACIS release mode macub libraries
   • acis3dt_phlv5_d - 3D ACIS Modeler and 3D ACIS PHL V5 using ACIS debug mode macub libraries
   • acis3dt_all - 3D ACIS Modeler, 3D ACIS Deformable Modeling and 3D ACIS PHL V5 using ACIS release mode macub libraries
   • acis3dt_all_d - 3D ACIS Modeler, 3D ACIS Deformable Modeling and 3D ACIS PHL V5 using ACIS debug mode macub libraries
2. Choose your desired build target from the Active Targets dropdown list.
3. Update settings regarding your HOOPS installation, if applicable. These settings must be updated in both build styles.
   1. Highlight the active target under the Targets section in Groups & Files pane. Click the Info button in the main toolbar, or select File->Get Info.
   2. Select the Build pane.
   3. Select the desired configuration or select "All Configurations" from the Configuration drop down menu.
   4. Select "Edit>Change Existing Settings" and then change the two custom build settings HOOPS_INSTALL_DIR and HOOPS_VER.
   5. Using the Active Build Style drop down list, change the build configuration from Development to Deployment and repeat the previous two steps.
   6. Close the Info window.
4. Select Build. Open the detailed build window (Build->Detailed Build Results) to view detailed build results, switch build style, or switch the active build target.
5. The application bundle is placed in <A3DT>/scm/acis3dt/build, which is Xcode's default build location. To change the destination location:
   1. In the Groups & Files window, select the project icon at the top of the window (titled acis3dt).
   2. Select Info in the main toolbar, or select "File>Get Info".
   3. Select the General pane.
   4. Change the "Place Build Products In" setting to "Separate location" and enter your desired location.
6. 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.
   1. The libtool table of contents update discussed below is performed in a Shell Script phase.
   2. The HOOPS library is copied from $(HOOPS_INSTALL_DIR)/Dev_Tools/hoops_3dgs/lib to acis3dt*.app/Contents/MacOS.
   3. The ACIS dynamic libraries are copied from the ACIS bin directory to acis3dt*.app/Contents/MacOS.

1. Open a command prompt window.
2. Set the following environment variables:

   set A3DT to your ACIS installation, for example, set A3DT=c:\Progra~1\Spatial\acisR20

   set HOOPS_INSTALL_DIR to your HOOPS installation directory>

3. Open the desired project:

   cd %A3DT%\src\ha_bridge (or src\ha_part or src\admhoops) and then

   devenv ha_bridge_amd_64.sln (or ha_part_amd_64.sln or admhoops_amd_64.sln) (for NT_AMD_64) or

   devenv ha_bridge_vc8.sln (or ha_part_vc8.sln or admhoops_vc8.sln) (for NT_VC8)

4. Choose one of these configurations:

   Release - Use with HOOPS version 10 or higher to link release ACIS to VC8.0 release HOOPS or

   Debug - Use with HOOPS version 10 or higher to link debug ACIS to VC8.0 debug HOOPS.

5. Select from menu: Build>Build the library.

1. Open a command prompt window.
2. Set the following environment variables:

   set A3DT to your ACIS installation, for example, set A3DT=c:\Progra~1\Spatial\acisR20

   set HOOPS_INSTALL_DIR to your HOOPS installation directory>

3. Open the desired project:

   cd %A3DT%\src\ha_bridge (or src\ha_part or src\admhoops) and then

   devenv ha_bridge_vc9_64.sln (or ha_part_vc9_64.sln or admhoops_vc9_64.sln) (for NT_VC9_64) or

   devenv ha_bridge_vc9.sln (or ha_part_vc9.sln or admhoops_vc9.sln) (for NT_VC9)

4. Choose one of these configurations:

   Release - Use with HOOPS version 10 or higher to link release ACIS to VC9.0 release HOOPS or

   Debug - Use with HOOPS version 10 or higher to link debug ACIS to VC9.0 debug HOOPS.

5. Select from menu: Build>Build the library

1. Open a command prompt window.
2. Set the following environment variables:

   set A3DT to your ACIS installation, for example, set A3DT=c:\Progra~1\Spatial\acisR20

   set HOOPS_INSTALL_DIR to your HOOPS installation directory>

3. Open the desired project:

   cd %A3DT%\src\ha_bridge (or src\ha_part or src\admhoops) and then

   devenv ha_bridge_vc10_64.sln (or ha_part_vc10_64.sln or admhoops_vc10_64.sln) (for NT_VC10_64) or

   devenv ha_bridge_vc10.sln (or ha_part_vc10.sln or admhoops_vc10.sln) (for NT_VC10)

4. Choose one of these configurations:

   Release - Use with HOOPS version 10 or higher to link release ACIS to VC9.0 release HOOPS or

   Debug - Use with HOOPS version 10 or higher to link debug ACIS to VC9.0 debug HOOPS.

5. Select from menu: Build>Build the library

1. Set the following environment variables:

   set A3DT to your ACIS installation

   set ARCH to the ACIS architecture you would like to build against

   set HOOPS_INSTALL_DIR to the location of your HOOPS installation

   set HOOPS_VER to the version of your HOOPS installation.

2. Change your working directory:

   cd $A3DT/src/ha_bridge (or src/ha_part or src/admhoops)

3. Build the library:

   make arch;

   where arch is one of the following: aix, aix64, linux, or linux_amd_64.

1. Open the desired Xcode project in A3DT/src/ha_bridge (or src/ha_part or src/admhoops), where A3DT is your ACIS installation location.
2. Update the settings regarding your HOOPS installation.
   1. In the Groups & Files window, expand the Target Category and select the target (ha_bridge, ha_part or admhoops).
   2. Click the Info Button in the main toolbar, or select File>Get Info.
   3. Select the Build pane.
   4. Scroll down through the settings to the two custom build settings HOOPS_INSTALL_DIR and HOOPS_VER.
   5. Select Edit Setting for each one and enter the appropriate value.
3. Click Build on the main window. The library is placed in A3DT/src/ha_bridge/build, which is Xcode's default build location. To change the destination location:
   1. In the Groups & Files window, select the project icon at the top of the window (titled ha_bridge, ha_part, or admhoops).
   2. Click the Info Button in the main toolbar, or select File>Get Info.
   3. Select the General pane.
   4. Change the "Place Build Products In" setting to "Separate location" and enter your desired location.

      Note: The project supports two build styles, both of which link against ACIS release libraries and the HOOPS release library. The Development style builds with debug symbols on and optimization off. The Deployment style builds with debug symbols off and optimization level -O1.

   5. Upon opening the project for the first time, the active Build Style is Development. To switch the style:
      1. Open the build results window by selecting Build>Detailed Build Results.
      2. Select Deployment from the Active Build Style drop down list.

// MyfirstAcisProject.cpp : Defines the entry point for the console application.
//
#include "acis.hxx"
#include "kernapi.hxx"
#include "lists.hxx"
#include "acistype.hxx"
#include "fileinfo.hxx"
 
void		process(outcome result);
void		process_file(FILE* fp);
ENTITY_LIST	retrieve_sat_file (char *fileName);
void		create_sat_file	(ENTITY *ent, char *fileName);
void		create_sat_file (ENTITY_LIST elist, char *fileName);
void		Initialize_ACIS ();
void		Terminate_ACIS ();
void	        Check_Entity (ENTITY* input);
 
void main()
{
    api_start_modeller(0);
 
    Initialize_ACIS ();
 
    //add unlock license key here
 
    //add ACIS calls here
 
    Terminate_ACIS();
 
    api_stop_modeller();
}
 
void Initialize_ACIS ()
{
  outcome result;
 
  FileInfo fileinfo;
  fileinfo.set_units (1.0);
  fileinfo.set_product_id ("ACIS (c) SPATIAL");
 
  result = api_set_file_info (3, fileinfo);
  process (result);
}	
 
void Terminate_ACIS ()
{
 
}
 
void process(outcome result)
{
  if (!result.ok()) 
  {										
    print_warnerr_mess("API", result.error_number(), stdout);			
  } 
  err_mess_type* warnings =NULL;  
  int nwarn = get_warnings(warnings);  
  for (int i = 0; i < nwarn; ++i)
  {
    printf("Warning %d : %s\n", warnings[i],   find_err_mess(warnings[i]));  
  }
}
 
void process_file(FILE* fp)
{
  if (!fp) 
  {		
    printf ("Unable to open input/output File\n");
    exit(0);									
  } 
}
 
ENTITY_LIST retrieve_sat_file (char *fileName)
{
  outcome result;
// NOTE: to retrieve a binary sab file, use the following code:
//  FILE *input_file = fopen (fileName, "rb");
  FILE *input_file = fopen (fileName, "r");
  process_file (input_file);
 
  ENTITY_LIST elist;
  result = api_restore_entity_list (input_file, TRUE, elist);
  process(result);
  fclose (input_file);
 
  return elist;
}
 
void create_sat_file (ENTITY *ent, char *fileName)
{
  outcome result;
 
  // Setting the units and product_id
 
  FileInfo fileinfo;
 
  fileinfo.set_units (1.0);
  fileinfo.set_product_id ("ACIS (c) SPATIAL");
 
  result = api_set_file_info (3, fileinfo);
  process (result);
 
  FILE *output_file = fopen (fileName, "w");
  process_file (output_file);
 
  ENTITY_LIST save_list;
  save_list.add (ent);
 
  result = api_save_entity_list (output_file, TRUE, save_list);
  process (result);
 
  fclose (output_file);
}
 
void create_sat_file (ENTITY_LIST elist, char *fileName)
{
  outcome result;
 
  // Setting the units and product_id
 
  FileInfo fileinfo;
 
  fileinfo.set_units (1.0);
  fileinfo.set_product_id ("ACIS (c) SPATIAL");
 
  result = api_set_file_info (3, fileinfo);
  process (result);
 
  FILE *output_file = fopen (fileName, "w");
  process_file (output_file);
 
  result = api_save_entity_list (output_file, TRUE, elist);
  process (result);
 
  fclose (output_file);
}