5 == Environment variables ==
7 If the software you are compiling requires $ACE_ROOT to be set (for
8 example, the tutorials), you may set it to /usr/lib/ace. For bash,
9 the command to do this is
11 export ACE_ROOT=/usr/lib/ace
15 export TAO_ROOT=${ACE_ROOT}/TAO
18 == Compiling examples ==
20 To compile ACE or TAO examples (in libace-doc and libtao-orbsvcs-doc), you'll
22 1. to define ACE_ROOT and TAO_ROOT as explained above.
23 2. to install mpc-ace package if needed.
24 3. to copy and uncompress the example you want to test, e.g.:
26 cp /usr/share/doc/libtao-orbsvcs-doc/examples/CosEC $HOME/ex1
27 find $HOME/ex1 -type f -name '*.gz' | xargs gunzip
29 4. to regenerate the GNUmakefiles for this new location:
32 mwc-ace -recurse -value_project install=. -value_project libout=.
34 5. now you can compile your example.
37 == Service Configuration ==
39 You'll need to carefully review server.conf files to ensure ACE service
40 configuration will work. Indeed in a lot of examples, the library name
41 in dynamic directives is a library root name which might need some
44 For example, in the following server.conf excerpt (taken from #656040
47 dynamic Server_Logging_Service Service_Object * netsvcs:_make_ACE_Server_Logging_Acceptor() active "-p 20009"
49 netsvcs refers to libnetsvcs.so. And this is what will be looked for. Unless
50 you have libnetsvcs-dev package installed, the lookup will fail. Another
51 way to fix this would be to replace netsvcs with the full library name, e.g.
55 -- Thomas Girard <thomas.g.girard@free.fr>, Sun, 23 May 2010 11:04:27 +0200