Shulou(Shulou.com)06/03 Report--

1 introduction to ICE

ICE (Internet Communications Engine) is an object-oriented middleware platform, which is mainly used for network communication. It provides a set of good tools and API interfaces for the application of object-oriented client-server model. At present, it is used in many projects all over the world. ICE middleware claims to be unified, open source, cross-platform, cross-language, distributed, security, service transparency, load balancing, object-oriented, superior performance, fire protection penetration, communication shielding. Therefore, compared with the middleware technology such as Corba,DCOM,SOAP,J2EE, it naturally has many advantages without their disadvantages.

2. Resource acquisition

Download third-party middleware resources on the official website, and the official download website of ZeroC ICE is https://zeroc.com/downloads/ice#source. The version used in this article is V3.7, which is downloaded and extracted, and the file directory is shown in figure 2.1.

Figure 2.1 decompressed files of Ice source code

Cpp/, csharp/, java/, js/, objective-c/, php/, python/ and other directories contain the Ice library implementation code of the corresponding language, the config/ directory stores the relevant configuration files that control the compilation mode, and the slice/ stores the code implementation of slice related tools.

3. Compile on Linux platform

ICE supports multiple languages and compiles all language support by default. Here, you only need to migrate C++-related code, modify the supported-languages attribute in config/Make.rules, delete unwanted language support and retain C++ support only, as shown in figure 3.1.

Figure 3.1 supported-languages property modification

After modifying the configuration file, you can start the compilation process directly in the root directory make. In order to facilitate the later migration work, the detailed compilation process is printed and saved to the Make.log file using the Vruns option, and the command: # make vases > Make.log. Check the Make.log content after the compilation to confirm that the compilation is successful.

4. Transplant work

This migration only migrates the main ICE library, namely libIce.so, which is supported by C++, so only the code files under the cpp directory are needed. Because it is C++ code, you need to select the C++ project option when creating the project. The compilation of the ICE main library code depends on libbz2 and requires preparation in advance.

4.1 Project creation

Create a dynamic library project for libIce in Real-Evo IDE. When creating, select the C++ project option and open expert mode, as shown in figure 4.1.

Figure 4.1 create project options

Delete the libIce.c file in the src directory and import the code files related to the main library in the cpp/ directory in the source code package. It is important to note that many code files are created during compilation using the slice tool, so you need to compile successfully in the linux environment before you can export all the files. These include directories cpp/include/generated/Ice/, cpp/include/Ice/, cpp/include/IceUtil/, cpp/src/Ice/, cpp/src/IceUtil/. The final directory structure is shown in figure 4.2.

Figure 4.2 Ice code directory structure

4.2 configure libIce.mk

Analyze the process of compiling libIce.so in Make.log, list all the cpp files that need to be compiled, and add them to LOCAL_SRCS one by one, as shown in figure 4.3.

Figure 4.3 adding a cpp file

Add the relevant header file search directory, including the project path to libbz2, as shown in figure 4.4.

Figure 4.4 header file search path

Add the macro configuration as shown in figure 4.5.

Figure 4.5 adding a macro configuration

Add compilation options, as shown in figure 4.6.

Figure 4.6 add compilation options

Add dependency libraries, including dependencies on the libbz2 library, as shown in figure 4.7.

Figure 4.7 adding dependent libraries

Open the C++ compilation extension, as shown in figure 4.8.

Figure 4.8 Open the C++ compilation extension

4.3 Code modification

There are several compilation errors in the default compilation, and some of the code needs to be modified as follows:

Modify src/ice-master/cpp/src/Ice/Cond.cpp to use CLOCK_REALTIME mode or time information, as shown in figure 4.9.

Figure 4.9 modify the way to get the time

Modify the src/ice-master/cpp/include/IceUtil/Config.h to increase the size of the DSP configuration, as shown in figure 4.10.

Figure 4.10 DSP size side configuration

Modify the interrupt symbol conflict in src/ice-master/cpp/include/Ice/Service.h,DSP and change it to interrupt2, as shown in figure 4.11.

Figure 4.11 interrupt symbol conflict

Modify src/ice-master/cpp/include/IceUtil/Config.h to eliminate GNUC version errors in DSP, as shown in figure 4.12.

Figure 4.12 eliminating GNUC version errors

Modify the operations related to deleting the dynamic library in src/ice-master/cpp/src/Ice/DynamicLibrary.cpp,DSP, as shown in figure 4.13.

Figure 4.13 operations related to deleting dynamic libraries in DSP

Modify src/ice-master/cpp/src/Ice/Instance.cpp and add the header file grp.h, as shown in figure 4.14.

Figure 4.14 add header file grp.h

Modify the src/ice-master/cpp/src/Ice/MetricsAdminI.cpp,DSP to add some missing interfaces, as shown in figure 4.15, figure 4.16, figure 4.17.

Figure 4.15 adding some missing interfaces in DSP

Figure 4.16 added some missing interfaces in DSP

Figure 4.17 adding some missing interfaces in DSP

Add some missing interfaces in src/ice-master/cpp/src/Ice/Network.cpp,DSP, as shown in figure 4.18, figure 4.19, figure 4.20, figure 4.21, figure 4.22.

Figure 4.18 adding missing interfaces in DSP

Figure 4.19 adding missing interfaces in DSP

Figure 4.20 adding missing interfaces in DSP

Figure 4.21 adding missing interfaces in DSP

Figure 4.22 adding missing interfaces in DSP

Src/ice-master/cpp/src/Ice/Service.cpp, remove the code related to the fork call, as shown in figure 4.23.

Figure 4.23 deleting the code related to fork calls

Src/ice-master/cpp/src/Ice/Thread.cpp to correct the difference in the pthread_join return value, as shown in figure 4.24.

Figure 4.24 correcting differences in pthread_join return values

Src/ice-master/cpp/src/IceUtil/RecMutex.cpp, correct the difference in the pthread_mutex_trylock return value, as shown in figure 4.25.

Figure 4.25 correcting differences in pthread_mutex_trylock return values

Strdup is used in src/ice-master/cpp/src/IceUtil/UtilException.cpp,DSP instead of interface _ _ cxa_demangle, as shown in figure 4.26.

Figure 4.26 using strdup instead of interface _ _ cxa_demangle in DSP

5 basic use of ICE

ICE application architecture is a server-client model, including server-side and client-side code. The client and server code are linked together by the interface code generated by the slice tool. Let's run a simple helloworld test routine using ICE.

5.1 generate interface code

Write the interface code demo.ice, as shown in listing 5.1.

Listing 5.1 demo.ice

Module demo {interface printer {void printerstr (string msg);};}

Use the slice tool compiled in the ICE source code in linux to generate the interface code:

# cpp/bin/slice2cpp demo.ice

Interface codes demo.cpp and demo.h can be generated in the current directory.

5.2 create a test project

Create the application project in RealEvo-IDE, import the code demo.cpp, demo.h, and create the code files server.cpp, client.cpp, as shown in listing 5.2.

Listing 5.2 server.cpp and client.cpp

Client.cpp#include # include using namespace demo;using namespace std;intmain (int argc, char * argv []) {int status = 0; Ice::CommunicatorPtr ic; try {ic = Ice::initialize (argc, argv); Ice::ObjectPrx base = ic- > stringToProxy ("SimplePrinter:default-p 10000"); printerPrx printer = printerPrx::checkedCast (base); if (! printer) throw "Invalid proxy" Printer- > printerstr ("Hello World!");} catch (const Ice::Exception & ex) {cerr waitForShutdown ();} catch (const Ice::Exception & e) {cerr

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.