First, you must have a compiler for the system on which you intend to run AcuSolve, as the distribution does not include a compiler. I believe that most Linux64 distributions include a compiler. For Windows systems, it is simplest to download Microsoft Visual Studio Express 2013, which now supports 64-bit systems. (Previous versions only supported 32-bit.)
When running on Windows, there are different ways to link the compiler with the AcuSolve environment. I find the simplest is to open the Compiler Command Prompt, making sure to use the appropriate version of the prompt for 32-bit or 64-bit installations. Then execute ‘acusim.bat’ in the \bin\ directory of the AcuSolve installation. For
Now in the problem directory you can issue acuMakeDll as necessary to compile your user function. Or on Linux, you would issue acuMakeLib.
See the Programs Reference Manual and/or add ‘-h’ to see the options.
On Windows, make sure you specify the type of message passing environment you will use when running AcuSolve. For example, if you will be running a single-processor job (-np 1) on Windows you would use:
acuMakeDll -mp none
or if you will be using pmpi for a parallel job on Windows you would use:
acuMakeDll -mp pmpi
By default, AcuSolve always looks for shared libraries libusr.so on Linux and libusr.dll on Windows, which are the default names generated by acuMakeLib and acuMakeDll.
In the latest AcuSolve 310 update acuMakeDll on Windows automatically searches for an installed compiler to use. So simply open the AcuSolve Command Prompt, browse to the directory with the user function coding and issue acuMakeDll with the appropriate options. (See the AcuSolve 12.0.310 Release Notes in the section ‘Summary of New/Changed Command Line Options.’)