Info | Support | Contact | About

Main   FieldTalk Modbus    Overview   Documentation   Evaluation   Testimonials   Platforms    Windows   Linux   QNX   Commercial Unix   Java   Delphi   Product Details    Features   Requirements   Licensing   Support Plans   Documentation    General Description   Module Description   Class Hierarchy   Classes   Functions & Members   Installation   Linking   Modbus Background   Examples   Integration		Linking your Applications against the Library Linux, UNIX and QNX Systems: Compiling and Linking Applications Let's assume the following project directory structure: myprj | +-- fieldtalk | +-- doc +-- src +-- include +-+ lib | +-- linux (exact name depends on your platform) Add the library's include directory to the compiler's include path. Example: c++ -Ifieldtalk/include -c myapp.cpp Add the file name of the library to the file list passed to the linker. Example: c++ -o myapp myapp.o fieldtalk/lib/linux/libmbusmaster.a Windows Systems: Compiling and Linking Applications Let's assume the following project directory structure: myprj | +-- fieldtalk | +-- doc +-- src +-- include +-+ lib | +-- win32_vc (exact name depends on your platform) Add the library's include directory to the compiler's include path. Visual C++ Example: cl -Ifieldtalk/include -c myapp.cpp Borland C++ Example: bcc32 -Ifieldtalk/include -c myapp.cpp Add the file name of the library to the file list passed to the linker. Visual C++ only: If you are using the Modbus/TCP protocol you have to add the Winsock2 library Ws2_32.lib. Visual C++ Example: cl -Fe myapp myapp.obj fieldtalk/lib/win32_vc/libmbusmaster.lib Ws2_32.lib Borland C++ Example: bcc32 -e myapp myapp.obj fieldtalk/lib/win32_vc/libmbusmaster.lib

Back | Top of page			Info | Support | Contact | About

Information in this document is subject to change without notice. Copyright © 2000-2010 proconX Pty Ltd. All rights reserved. All product and brand names mentioned on this page may be trademarks or registered trademarks of their respective owners.