#include Note If you don't want to use the static Multi-threaded (/MT) runtime libraries, but the dynamic linking Multi-threaded DLL (/MD), then please use the MLPI library "libmlpiwin32_msvcrt.lib" instead of "libmlpiwin32.lib" in the pragma comment or your project settings. In the following Subsection ( Setting Up the Project) a different mannet to link the dynamic library is presented. This library will automatically link the shared library located in the same folder. In order to link the static library into the desired project, it is necessary to link the corresponding library with extension ".lib" located in the \mlpiCore\bin path. Note Starting at Server Version 1.18 the use of static libraries has been deprecated. Do the same for the Library Files, but insert the path to your library \mlpiCoreClient\bin\. In the right combo box, choose Include Files and add the path to your \mlpiCoreClient\include directory. In the left combo box called Platform, you have to select Win32. To do this, open Visual Studio 2005 and go to Tools->Options->Projects And Solutions->VC Directories. This way, you don't need to worry about absolute paths or copying the libs and headers to your project directory. You may want to include the paths to the MLPI-SDK as the default search path of your development environment. Please keep in mind that hard real-time from your application to the control is not possible using this setup. All MLPI function calls are tunneled through TCP/IP over an Ethernet connection to the control. Learn how to set up a simple Microsoft Visual Studio 2005 project which runs on a standard windows platform and is able to connect to a MLPI device using MLPI function calls. Although we recommend using Microsoft Visual Studio 2010 for MLPI Application development on a windows platform, it is also possible to use the older Microsoft Visual Studio 2005 version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |