| blob | f5f2d3b2a7499ed4a59611ef522069b843b25fc6 |
1 TANGO source code release version 9.2.5a - README (01/2017)\r
2 ==========================================================\r
3 \r
4 \r
5 \r
6 TABLE OF CONTENTS\r
7 -----------------\r
8 \r
9 1 - Introduction\r
10 2 - What's inside\r
11 3 - Prerequisites\r
12 4 - Installing\r
13 5 - Compiling\r
14 6 - Running\r
15 7 - Updating from previous Tango releases\r
16 8 - Documentation\r
17 9 - Remarks\r
18 10 - Questions\r
19 11 - URL\r
20 12 - Changes\r
21 \r
22 \r
23 1 - INTRODUCTION\r
24 ----------------\r
25 This is the README for the TANGO source code release. TANGO is a\r
26 toolkit for building object oriented control systems based on CORBA ans ZMQ. \r
27 TANGO is a joint effort of the several European research institutes.\r
28 \r
29 This source code release is based on the latest version of TANGO 9 (9.2.5a)\r
30 and is intended for Unix platforms. A binary version for Windows of TANGO \r
31 is available. The source code contained in this package \r
32 runs on Windows but the Makefile don't.\r
33 \r
34 Tango 9 and above is compliant to the 64 bit architecture.\r
35 \r
36 This package is foreseen (and was tested) to run with omniORB4.2.1 even if it \r
37 works as well with omniORB 4.1.6, 4.1.7 and 4.2.0, zmq 4.0.5 and Java 1.7\r
38 \r
39 The default Pogo application in this package can generate source code\r
40 for C++, Python and Java device servers.\r
41 \r
42 The database server delivered with this package do not force the database\r
43 user to be root. You have to use the my.cnf configuration files\r
44 or the MYSQL_USER and MYSQL_PASSWORD environment variables to specify\r
45 the database account to be used by the database server.\r
46 \r
47 The TangoTest device server delivered with this package is an example \r
48 implementation of all possible Tango data types. \r
49 The displayed data is animated what creates some CPU load \r
50 when running the server. Starting an atkpanel (generic Tango client)\r
51 on a device of this server is CPU and memory consuming, because\r
52 all possible data are read and displayed.\r
53 \r
54 In the case of upgrading an alreay running Tango system, please follow\r
55 the instructions in the chapter UPGRADING FROM PREVIOUS TANGO RELEASES.\r
56 \r
57 \r
58 2 - WHAT'S INSIDE\r
59 -----------------\r
60 \r
61 This source code release contains :\r
62 \r
63 (1) Tango C++ library source files and java library and application jar files\r
64 \r
65 (2) The Tango database device server source files and the database configuration files (.my.cnf).\r
66 \r
67 (3) The Jive application. \r
68 \r
69 (4) The Astor application and its associated Starter device server source files.\r
70 \r
71 (5) The Pogo application.\r
72 \r
73 (6) The tg_devtest application\r
74 \r
75 (7) A test device server called TangoTest with its source files\r
76 \r
77 (8) The atk graphical toolkit for writing tango applications in java\r
78 \r
79 (9) The atkpanel application as a generic test client\r
80 \r
81 (10 The atktuning application for tuning attributes in a device\r
82 \r
83 (11) The logviewer application for visualising logging messages\r
84 \r
85 (12) The DeviceTree application to display tango device attribute and/or command\r
86 \r
87 (13) The atkmoni application to monitor scalar attribute values in time\r
88 \r
89 (14) The jdraw synoptic editor to create synoptic applications\r
90 \r
91 (15) The synopticAppli to run and test synoptics created with jdraw\r
92 \r
93 (16) The Tango controlled access device server source file\r
94 It is used if you want to run Tango with its controlled access feature\r
95 \r
96 The Jive application is a Tango database browsing tool written in Java. It also\r
97 allows device testing. Its documentation is at\r
98 \r
99 http://www.esrf.eu/computing/cs/tango/tango_doc/tools_doc/jive_doc/index.html\r
100 \r
101 The Astor application is also a Java application. With the help of the Tango\r
102 starter device server, it allows full remote Tango control system administration.\r
103 Its documentation is at :\r
104 \r
105 http://www.esrf.eu/computing/cs/tango/tango_doc/tools_doc/astor_doc/index.html\r
106 \r
107 The Pogo application is a graphical Tango device server code generator.\r
108 Its documentation is at :\r
109 \r
110 http://www.esrf.eu/computing/cs/tango/tango_doc/tools_doc/pogo_doc/index.html\r
111 \r
112 tg_devtest is a device testing application for device server which do not\r
113 use the database. It is a sub-part of Jive. \r
114 \r
115 3 - PREREQUISITES\r
116 -----------------\r
117 \r
118 Before compiling and installing TANGO you need to install :\r
119 \r
120 (1) omniORB available from http://sourceforge.net/projects/omniorb \r
121 (Preferably version 4.2.1 but 4.2.0/4.1.7/4.1.6 is fine).\r
122 OmniORB is mandatory to build the Tango libraries and the delivered Tango \r
123 device servers.\r
124 \r
125 (2) zmq available from http://www.zeromq.org (version >= 4.0.5).\r
126 Zmq is mandatory to build the Tango libraries and the delivered Tango \r
127 device servers.\r
128 \r
129 (3) mysql available from http://mysql.org (version >= 5.5) or MariaDB from https://mariadb.org (version >= 10.0)\r
130 One of these two databases is mandatory to install a Tango database. The default database is still mysql.\r
131 If you want to use MariaDB, use the --enable-mariadb configure option.\r
132 \r
133 (4) doxygen available from http://www.doxygen.org\r
134 \r
135 Remark : doxygen is not mandatory to run Tango. It is just used by our code\r
136 generator (called Pogo) to automatically generates some part of \r
137 the Tango device server documentation. If you don't install it,\r
138 this part of the documenetaion will simply not be generated.\r
139 But in all cases, some HTML pages documenting Tango device server\r
140 will allways be generated.\r
141 \r
142 Also check the tools you are using\r
143 \r
144 (1) If you are using gcc, you need to have gcc release 3.2.0 or above. You can\r
145 download gcc from http://gcc/gnu.org\r
146 \r
147 (2) Only java release 1.7.0 or above is supported, you can download java from\r
148 http://java.sun.com/j2se.\r
149 Java is mandatory to install and run the Tango tools.\r
150 \r
151 \r
152 4 - INSTALLING\r
153 --------------\r
154 \r
155 Once you have installed the packages in prerequisites you can think\r
156 about configuring and compiling TANGO. \r
157 \r
158 To configure TANGO you need to tell it where to find omniORB, ZMQ and\r
159 mysql (if it is in a non-standard place) and where to install\r
160 TANGO.\r
161 \r
162 The main options for configure are:\r
163 --prefix=PREFIX install architecture-independent files in PREFIX\r
164 [/usr/local]\r
165 --enable-static[=PKGS]\r
166 build static libraries [default=no]\r
167 --enable-mariadb MariaDb database instead of mysql. \r
168 Build database server using mariadb instead of mysql\r
169 \r
170 --disable-java disable installation of Java applications\r
171 --disable-dbserver disable installation of Tango database server.\r
172 --disable-dbcreate enable an creation of the Tango database schema\r
173 --disable-jpegmmx disable jpeg mmx optimization\r
174 \r
175 --with-java path to java interpreter\r
176 --with-doxygen path to doxygen utility\r
177 --with-lyx path to LyX utility\r
178 --with-zlib=DIR root directory path of zlib installation defaults to\r
179 /usr/local or /usr if not found in /usr/local\r
180 --with-omni prefix to omniORB installation (default: $OMNI_ROOT)\r
181 --with-zmq prefix to ZMQLIB installation\r
182 \r
183 --with-tango-db-name Name of the database created in mysql (default: tango)\r
184 --with-tango-rc-file Location/name of the tango rc file (default: /etc/tangorc)\r
185 \r
186 --with-mysqlclient-prefix=PFX\r
187 Prefix where mysqlclient is installed\r
188 --with-mysqlclient-include=DIR\r
189 Directory pointing to mysqlclient include files\r
190 --with-mysqlclient-lib=LIB\r
191 Directory pointing to mysqlclient library (Note:\r
192 -include and -lib do override paths found with\r
193 -prefix)\r
194 \r
195 --with-mysql-ho the host of the database (mysql or mariadb) (default: <blank>)\r
196 --with-mysql-admin super user of your database (mysql or mariadb) (default: <blank>)\r
197 --with-mysql-admin-passwd\r
198 super user password of your database (mysql or mariadb) (default:\r
199 <blank>)\r
200 \r
201 The last three options can be replaced with a .my.cnf file in your home \r
202 directory with the following content:\r
203 \r
204 [client]\r
205 user = [db login name]\r
206 password = [password]\r
207 host = [host name]\r
208 \r
209 At the end of the configure script, a status is displayed indicating pathes\r
210 and versions of found software and the parts of the Tango package which are\r
211 ready to be installed.\r
212 Example (using mysql): \r
213 \r
214 Source code location: ../..\r
215 Version: 9.2.5a\r
216 Compiler: gcc,g++\r
217 \r
218 OMNIORB PATH: /segfs/tango/ORB/omniORB4.2.1/ubuntu1404\r
219 OMNIORB VERSION: "4.2.1"\r
220 \r
221 ZMQ PATH: /segfs/tango/transport/zmq4.0.5/ubuntu1404\r
222 ZMQ VERSION: 4.0.5\r
223 \r
224 JAVA PATH: /usr/bin/java\r
225 JAVA VERSION: 1.7.0_79\r
226 \r
227 MYSQL CLIENT LIB: -L/usr/local/mysql/lib/mysql -lmysqlclient\r
228 MYSQL VERSION: 5.7.13\r
229 MYSQL CONNECTION: OK\r
230 \r
231 build:\r
232 libraries: yes\r
233 java application: yes\r
234 event java interface: yes\r
235 access control server: yes\r
236 database server: yes\r
237 database schema create: yes\r
238 \r
239 \r
240 Hints to configure:\r
241 \r
242 The Tango database server\r
243 -------------------------\r
244 To disable the compilation and installation of the database server, \r
245 use --disable-dbserver. \r
246 \r
247 Create the Tango database\r
248 -------------------------\r
249 To allow the configure script to create the Tango database in\r
250 your database, make sure that the mysql version is > 5.5 (or 10.0 for mariadb) and\r
251 the mysqld is running before doing configure.\r
252 Also check that the mysql client (called mysql) is in your path.\r
253 \r
254 If you are not running the configure script on the same host\r
255 where the mysql server is running, use the "--with-mysql-ho" configure\r
256 option or the host entry in the my.cnf file. \r
257 \r
258 The configure script will try to connect to the\r
259 database. Make sure that privileges are granted to\r
260 the user used by configure running on the host where you\r
261 run configure. \r
262 \r
263 The configure options "--with-mysql-admin" and "--with-mysql-admin-passwd"\r
264 allow you to select which database user configure will use.\r
265 You can also use the user and password entries of the my.cnf file\r
266 to set-up your connection to the database.\r
267 \r
268 To disable any access to the database use the --disable-dbcreate option.\r
269 \r
270 Database server, mysql and libz\r
271 -------------------------------\r
272 Depending on how MySql has been installed, the Tango database\r
273 server may need the compress/uncompress library (called "libz").\r
274 By default, configure try to find this compress/uncompress stuff.\r
275 If you don't need it, use the configure "--without-zlib". \r
276 \r
277 Java applications\r
278 -----------------\r
279 Tango arrives with many Java applications. Each java applications has\r
280 its own script (in $prefix/bin) where the CLASSPATH is set before \r
281 starting the java interpreter. These scripts will be modified by the\r
282 configure script to set a correct path to the java interpreter found in\r
283 your PATH when configure was run. You can also use the "--with-java=xxx"\r
284 to define a path to the java interpreter.\r
285 \r
286 It is not mandatory to find the java interpreter in your PATH. You can use \r
287 the "--disable-java" configure option to build Tango. \r
288 When java was not found, disabled, or found with un unsufficient version, \r
289 the installation of the java applications is disabled.\r
290 \r
291 lyx\r
292 ---\r
293 LyX is a document processor used to generate the tango manual documentation.\r
294 One already generated manual is provided in this distribution. Nevertheless,\r
295 if you want to re-generate it, you can use the command "make pdf" but this\r
296 requires LyX to be installed on your host. You can used the "--with-lyx=xxx"\r
297 configure command line to define a path to the LyX utility on your host.\r
298 \r
299 doxygen\r
300 -------\r
301 Doxygen is a documentation generator from C++ source files. It is used by the\r
302 Tango code generator (called Pogo) to generate Tango device server documentation.\r
303 The script used to start Pogo will be modified by the configure script to set\r
304 a correct path to the doxygen command found in your PATH when configure was\r
305 run. You can also used the "--with-doxygen=xxx" to define a path to the\r
306 doxygen command.\r
307 It is not mandatory to find the doxygen command in your PATH or to use the\r
308 "--with-doxygen" configure option to build and run Tango. This will only prevent\r
309 some part of Tango device server documentation to be generated by Pogo.\r
310 \r
311 \r
312 You can type "configure --help" to get a print of all the options\r
313 supported by the configure script.\r
314 \r
315 Here is an example of running configure for TANGO telling it where\r
316 to install (--prefix) TANGO and where omniORB and ZMQ are installed:\r
317 \r
318 cd $directory_where_tango_has_been_installed\r
319 mkdir build\r
320 cd build\r
321 export CC=gcc\r
322 export CXX=g++\r
323 ../configure --prefix=/home/tango/release/install_dir_linux \\r
324 --with-omni=/segfs/tango/ORB/omniORB4.2.1/ubuntu1404 \\r
325 --with-zmq=/segfs/tango/transport/zmq4.0.5/ubuntu1404\r
326 \r
327 \r
328 During the configure procedure the access to the database is tested. Please prepare\r
329 your my.cnf (database configuration file) or use the configure options\r
330 --with-mysql-admin\r
331 --with-mysql-admin-passwd\r
332 --with-mysql-ho\r
333 to specify the access to the database.\r
334 \r
335 \r
336 5 - COMPILING\r
337 -------------\r
338 \r
339 Once configure has run successfully you can compile and install the\r
340 executables, include files, libraries and scripts. Do this by typing :\r
341 \r
342 make all\r
343 \r
344 make install\r
345 \r
346 \r
347 6 - RUNNING\r
348 -----------\r
349 \r
350 To test wether the TANGO build worked do the following :\r
351 \r
352 (1) start the database on port 10000 by typing :\r
353 \r
354 TANGO_INSTALL_DIR/bin/DataBaseds 2 -ORBendPoint giop:tcp::10000\r
355 \r
356 Specify the database account to be used by the database server.\r
357 Two possibilities are available:\r
358 - set the following environment variables to the account and \r
359 password to be used\r
360 \r
361 MYSQL_USER to specify the database login name\r
362 MYSQL_PASSWORD to specify the password\r
363 MYSQL_HOST if required\r
364 \r
365 - configure the database client with the database configuration \r
366 file my.cnf\r
367 \r
368 [client]\r
369 user = [database login name]\r
370 password = [password]\r
371 \r
372 (2) Configure the TANGO_HOST environment variable with the hostname the\r
373 database server is running on and the port number used.\r
374 \r
375 setenv TANGO_HOST hostname:10000\r
376 \r
377 (3) start the test device server tangoTest :\r
378 \r
379 TANGO_INSTALL_DIR/bin/TangoTest test\r
380 \r
381 (4) start jive by typing for example :\r
382 \r
383 TANGO_INSTALL_DIR/bin/jive\r
384 \r
385 (See chapter 4 java sub-chapter to check the jive script) \r
386 \r
387 (5) test your device using the test device in jive\r
388 \r
389 (6) write new device servers using pogo :\r
390 \r
391 TANGO_INSTALL_DIR/bin/pogo\r
392 \r
393 (See chapter 4 java sub-chapter to check the pogo script) \r
394 \r
395 \r
396 7 - UPDATING FROM PREVIOUS TANGO RELEASES\r
397 -----------------------------------------\r
398 \r
399 WARNINGS:\r
400 \r
401 To update the Tango database, the distribution provides some scripts.\r
402 The "make install" command will create these database related scripts in\r
403 <install_dir>/share/tango/db ONLY if the database connection test\r
404 done at configure time is successfull ("database schema create" reported\r
405 as yes at the end of the configure script execution)\r
406 \r
407 7-2 - UPDATING FROM A TANGO 9 DATABASE\r
408 --------------------------------------\r
409 \r
410 Tango 9.2 includes an update of the database. This is one update of\r
411 the stored procedure (release 1.12).\r
412 \r
413 To update your database, follow these instructions:\r
414 \r
415 a - Stop your control system and your database server(s)\r
416 \r
417 b - Backup your database (Recommended, not mandatory)\r
418 \r
419 c - Cd to the <install_dir>/share/tango/db directory\r
420 \r
421 d - Run the update script:\r
422 ./update_db.sh\r
423 \r
424 e - Restart your database server(s)\r
425 \r
426 7-2 - UPDATING FROM A TANGO 8 DATABASE\r
427 --------------------------------------\r
428 \r
429 Tango 9.1 requires an update of the database. This is one update of\r
430 the stored procedure (release 1.11), some new commands in the list of allowed \r
431 commands for the Database class (for Tango Access Control system) and\r
432 some new tables related to the new pipe feature.\r
433 \r
434 To update your database, follow these instructions:\r
435 \r
436 a - Stop your control system and your database server(s)\r
437 \r
438 b - Backup your database (Recommended, not mandatory)\r
439 \r
440 c - Cd to the <install_dir>/share/tango/db directory\r
441 \r
442 d - Run the update script:\r
443 mysql -u[user] -p[password] < ./update_db8.sql\r
444 \r
445 e - Restart your database server(s)\r
446 \r
447 \r
448 7-2 - UPDATING FROM A TANGO 7 DATABASE\r
449 --------------------------------------\r
450 \r
451 Tango 9.1 needs an update of the data in the database. This is one\r
452 update of the stored procedure (release 1.9), some more\r
453 commands definition for the Tango control access and new tables dedicated to pipe.\r
454 \r
455 To update your database, follow these instructions:\r
456 \r
457 a - Stop your control system and your database server(s)\r
458 \r
459 b - Backup your database (Recommended, not mandatory)\r
460 \r
461 c - Cd to the <install_dir>/share/tango/db directory\r
462 \r
463 d - Run the update script:\r
464 mysql -u[user] -p[password] < ./update_db7.sql\r
465 \r
466 e - Restart your database server(s)\r
467 \r
468 \r
469 8 - DOCUMENTATION\r
470 -----------------\r
471 \r
472 Don't forget to READ THE MANUAL (in doc/tango.pdf) !\r
473 \r
474 9 - REMARKS\r
475 -----------\r
476 \r
477 TANGO 9.0:\r
478 Tango 9.0 is a major release. Recompiling a device server with Tango 8.0 \r
479 means recompiling ALL classes of the device server. You need to work with\r
480 coherent include files.\r
481 \r
482 TANGO 8.0:\r
483 Tango 8.0 is a major release. Recompiling a device server with Tango 8.0 \r
484 means recompiling ALL classes of the device server. You need to work with\r
485 coherent include files.\r
486 \r
487 TANGO 7.0:\r
488 Tango 7.0 is a major release. Recompiling a device server with Tango 7.0 \r
489 means recompiling ALL classes of the device server. You need to work with\r
490 coherent include files.\r
491 \r
492 TANGO 6.1:\r
493 The database server in this package uses stored procedures. To make it reliably \r
494 work the MySQL version must be >5.0.\r
495 To exploit the full performance of the new database server, on an already \r
496 installed Tango system, the the chapter UPDATING FROM PREVIOUS TANGO RELEASES.\r
497 \r
498 TANGO 6.0:\r
499 Tango 6.0 is a major release, because it uses omniORB 4.1 which is\r
500 a major release of omniORB. The code generated from the with the IDL\r
501 compiler is not compatible with the code gernerated with omniORB 4.0.x!\r
502 To avoid any confusion with new and old libraries we decided to\r
503 make also a major Tango release.\r
504 \r
505 Recompiling a device server with Tango 6.0 and omniORB 4.1 means \r
506 recompiling ALL classes of the device server. You need to work with\r
507 coherent include files.\r
508 \r
509 \r
510 10 - QUESTIONS\r
511 --------------\r
512 \r
513 You will definitely have some ! Send questions to info@tango-controls.org or on the \r
514 forum: http://www.tango-controls.org/community/forum\r
515 \r
516 11 - URL\r
517 --------\r
518 \r
519 Visit the TANGO website http://www.tango-controls.org for online \r
520 documentation, news and to download add-on packages.\r
521 \r
522 \r
523 12 - CHANGES\r
524 ------------\r
525 \r
526 See the file TANGO_CHANGES to get an overview of all modification\r
527 between the different Tango library versions.\r
528 \r
529 Changes between Tango distribution 9.2.5 and 9.2.5a\r
530 --------------------------------------------------\r
531 \r
532 - Updated Jive to Release 7.10\r
533 - Updated JSSHTerminal to Release 1.10\r
534 - Updated Astor to Release 7.0.9\r
535 - Added DBBench Release 1.3\r
536 \r
537 Changes between Tango distribution 9.2.2 and 9.2.5\r
538 --------------------------------------------------\r
539 \r
540 - Updated C++ library to Release 9.2.5\r
541 - Updated Jive to Release 7.8\r
542 - Updated atkpanel to Release 5.5\r
543 - Updated Pogo to Release 9.4.5\r
544 - Updated DbServer to Release 5.6 (stored procedure release 1.13)\r
545 - Updated JTango to Release 9.1.2\r
546 - Updated ATK to Release 9.1.22\r
547 - Updated Astor to Release 7.0.7\r
548 - Updated Starter to Release 6.9\r
549 - Updated LogViewer to Release 2.0.4\r
550 - Updated TangoAccessControl to Release 2.13\r
551 \r
552 Changes between Tango distribution 9.1.0 and 9.2.2\r
553 --------------------------------------------------\r
554 \r
555 - Updated C++ library to Release 9.2.2\r
556 - Updated Jive to Release 6.9\r
557 - Updated atkpanel to Release 5.4\r
558 - Updated Pogo to Release 9.2.4\r
559 - Updated DbServer to Release 5.4 (stored procedure release 1.11)\r
560 - Updated JTango to Release 9.0.7\r
561 - Updated ATK to Release 9.1.13\r
562 - Updated Astor to Release 6.7.0\r
563 - Updated Starter to Release 6.8\r
564 - Updated TangoTest to Release 2.1\r
565 - Updated TangoAccessControl to Release 2.12\r
566 \r
567 - SourceForge bug 755 : DBserver and TAC : Passing database name at run time\r
568 - SourceForge bug 762 : TangoTest : SegFault writing to long_spectrum attribute\r
569 - SourceForge bug 763 : DBserver : NULL insertion in NOT NULL columns\r
570 - SourceForge bug 766 : Starter : memory leak\r
571 - SourceForge bug 772 : Makefile dependencies to prevent unnecessary rebuilt\r
572 - SourceForge bug 778 : tango.opt defines wrong LDFLAGS\r
573 - SourceForge bug 782 : Bug in common_target.opt file\r
574 \r
575 - TangoTest : Memory not freed in delete_device() method\r
576 - DBserver : Add command DbGetForwardedAttributeForDevice\r
577 - DBserver : Change default value for accessed columns in 2 tables\r
578 - DBserver : Change variable data type in Stored procedure\r
579 \r
580 \r
581 Changes between Tango distribution 8.1.2 and 9.1.0\r
582 --------------------------------------------------\r
583 \r
584 - Updated C++ library to Release 9.1.0\r
585 - Updated Log4Tango to Release 5.0.1\r
586 - Updated Jive to Release 6.7\r
587 - Updated atkpanel to Release 5.2\r
588 - Updated Pogo to Release 9.1.7\r
589 - Updated Astor to Release 6.6.6\r
590 - Updated DbServer to Release 5.2\r
591 - Replacing TangORB with JTango Release 9.0.5\r
592 - Updated ATK to Release 9.1.3\r
593 - Updated LogViewer to Release 2.0.1\r
594 - Updated Starter to Release 6.6\r
595 - Updated TangoTest to Release 2.0\r
596 - Updated TangoAccessControl to Release 2.11\r
597 - Updated tango_admin to Release 1.13\r
598 - Updated AccessControl abstract class to Release 2.7\r
599 \r
600 - notifd2db removed from distribution\r
601 - jzmq removed from distribution\r
602 - removed notify_daemon script\r
603 \r
604 - SourceForge bug 661: DbServer : Wrong initialization of device table int and date columns (created_db script)\r
605 - SourceForge bug 669: Jive : File written with escaped " character\r
606 - SourceForge bug 670: TangoTest : Crash with value < 1 given to attribute float_scalar\r
607 - SourceForge bug 671: DbServer : Attribute alias not deleted during delete_device\r
608 - SourceForge bug 713: DbServer : History ID on 64 bits value\r
609 - DbServer: Characters / and " " forbidden in alias name\r
610 - DbServer: Small memory leak in DbGetInstanceNameList command\r
611 - DbServer: Memory leak when trying to get event from it\r
612 - DbServer: Change the way memorized attribute property (__value) is managed\r
613 - DbServer: Remove history memorization for memorized attribute (including already stored history)\r
614 - DbServer: Replace NULL insertion in not null table colums by actual date (now())\r
615 - Tango_admin: Add options --server-list and --server-instance-list (FR 99)\r
616 - Distribution: Doc images source files (.fig) added to distribution\r
617 - Distribution: Idl file compiled during the package compilation \r
618 \r
619 \r
620 Changes between Tango distribution 8.0.5 and 8.1.2\r
621 ---------------------------------------------------\r
622 \r
623 - Updated C++ library to Release 8.1.2\r
624 - Updated Log4Tango to Release 4.0.8\r
625 - Updated Jive to Release 4.31\r
626 - Updated atkpanel to Release 4.8\r
627 - Updated Pogo to Release 8.1.14\r
628 - Updated Astor to Release 6.3.6\r
629 - Updated DbServer to Release 4.23\r
630 - Updated TangORB to Release 8.3.0\r
631 - Updated ATK to Release 4.5.3\r
632 - Updated Starter to Release 5.12\r
633 - Updated TangoTest to Release 1.9\r
634 - Updated TangoAccessControl to Release 2.9\r
635 - Updated DeviceTree to Release 1.9.6\r
636 - Updated notifd2db to Release 1.14\r
637 - Updated tango_admin to Release 1.11\r
638 - Updated AccessControl abstract class to Release 2.6\r
639 \r
640 - SourceForge bug 88 (1497526) - Updating property with character \\r
641 - SourceForge bug 520 (3543407) - Bug in DbGetDeviceAttributeProperty2\r
642 - SourceForge bug 525 (3559224) - Missing -lzmq for libtango\r
643 - SourceForge bug 555 - Not possible to launch atkpanel from Jdraw\r
644 \r
645 - New attribute alias related commands in Database server\r
646 - New DbRenameServer command in database server\r
647 - The DbDeleteServer command now also delete device properties\r
648 - Improvement in TAC device filter (sr/v-*/* allowed)\r
649 - Add jzmq in source distribution\r
650 - "make pdf" command now generates the Tango book with a new\r
651 --with-lyx configure command line option\r
652 \r
653 \r
654 Changes between Tango distribution 7.2.6a and 8.0.5\r
655 ---------------------------------------------------\r
656 \r
657 - Updated C++ library to Release 8.0.5\r
658 - Updated Log4Tango to Release 4.0.7\r
659 - Updated Jive to Release 4.24\r
660 - Updated atkpanel to Release 4.5\r
661 - Updated Pogo to Release 8.0.7\r
662 - Updated Astor to Release 6.0.4\r
663 - Updated notifd2db to Release 1.13\r
664 - Updated tango_admin to Release 1.10\r
665 - Updated DbServer to Release 4.17\r
666 - Updated TangORB to Release 8.0.0 \r
667 - Updated ATK to Release 4.3.9\r
668 - Updated Starter to Release 5.5\r
669 - Updated TangoTest to Release 1.7.0\r
670 - Updated TangoAccessControl to Release 2.5\r
671 - Updated AccessControl to Release 2.5\r
672 \r
673 - SourceForge bug 3308848: Fix build on kfreebsd system\r
674 - SourceForge bug 3383197: Jpeg mmx option to configure\r
675 - SourceForge bug 3409434: Memory leaks in Database server\r
676 - SourceForge bug 3515206: Bug in PutServerInfo command (Database server)\r
677 \r
678 - Add command DbGetCSDbServerList to database server\r
679 - The database server now unregister itself from database when it is killed\r
680 - Add 3 db commands (DbImportEvent, DbGetDeviceAlias and DbGetCSDbServerList) in allowed command list (For TAC)\r
681 - The database server and TAC server supports a MYSQL_HOST environment variable\r
682 - Add messages around MySQL connection in database server (to ease debugging)\r
683 - New and faster algorithm in database command DbGetDeviceAttributeProperty2\r
684 - Fix two bugs in database stored procedure (release 1.8)\r
685 - Try to prevent SQL injection in command DbMySqlSelect\r
686 - All database class commands now have their arguments description field initialized\r
687 - Database server, TAC server and Tango Test are now compiled with Debian hardenning flags\r
688 \r
689 Changes between Tango distribution 7.2.1 and 7.2.6a\r
690 ---------------------------------------------------\r
691 \r
692 - SourceForge bug 3312284: Could not start jive, astor,...\r
693 \r
694 Changes between Tango distribution 7.2.1 and 7.2.6\r
695 ---------------------------------------------------\r
696 \r
697 - Updated C++ library to Release 7.2.6\r
698 - Updated Jive to Release 4.19\r
699 - Updated LogViewer to Release 1.2.3\r
700 - Updated Pogo to Release 7.2.1\r
701 - Updated Astor to Release 5.4.1\r
702 - Updated notifd2db to Release 1.12\r
703 - Updated tango_admin to Release 1.8\r
704 - Updated DbServer to Release 4.12\r
705 - Updated TangORB to Release 7.4.3\r
706 - Updated ATK to Release 4.2.10\r
707 - Updated Starter to Release 5.2\r
708 - Updated TangoTest to Release 1.4.5\r
709 - Updated TangoAccessControl to Release 2.4\r
710 - Updated AccessControl to Release 2.4\r
711 \r
712 - SourceForge bug 3158150: Architecture issue in configure.in\r
713 - SourceForge bug 3152384: Db Server crash when reading timing attributes\r
714 - SourceForge bug 3138228: A new parameter in tango_admin when pinging database\r
715 - SourceForge bug 3137921: Pogo 7 does not create some output arguments\r
716 - SourceForge bug 3129852: Fix SQL script to update a Tango database from release 6 to 7.2\r
717 \r
718 - Update crate_db_tables.sql script to support MySQL >= 5.1 CREATE TABLE sql statement\r
719 - Implement a retry to MySQl connection in DB server. Needed for binary install\r
720 \r
721 Changes between Tango distribution 7.2.0 and 7.2.1\r
722 --------------------------------------------------\r
723 \r
724 - Updated C++ library Release 7.2.1\r
725 \r
726 - Fix SourceForge bugs number 3092110 and 3092764\r
727 - Split lib/cpp/server/jpeg directory in order to optimize compilation options\r
728 \r
729 Changes between Tango distribution 7.1.1 and 7.2.0\r
730 --------------------------------------------------\r
731 \r
732 - Added tango_admin Release 1.0\r
733 - Updated database device server Release 4.8\r
734 - Updated TangoAccessControl device server Release 1.5\r
735 - Updated TangoTest to Release 1.4.4\r
736 - Updated ATKCore and ATKWidget to Release 4.2.3\r
737 - Updated atkpanel to Release 4.3\r
738 - Updated Jive to Release 4.12\r
739 - Updated Pogo Release 7.0\r
740 - Updated Astor to Release 5.2.9\r
741 - Updated TangORB to Release 7.3.5\r
742 - Updated Jdraw to Release 1.13\r
743 - Updated Starter to Release 4.14\r
744 \r
745 - Fix SourceForge bugs number 3000308 - 3000310 - 3000329\r
746 - After installation, the doc and man folders are now under the "share" folder\r
747 - A new doc/src folder added in the source package. This folder contains all the\r
748 necessary files (lyx format) to generate the Tango bible (tango.pdf).\r
749 If lyx is installed on your computer, to re-generate the bible, go to doc/src\r
750 and type " lyx -e pdf tango.lyx"\r
751 - Pogo release 6 and 7 are available in this release. If you want to start\r
752 pogo release 6, simply use the pogo-6 script available in the bin directory after\r
753 the install\r
754 - After installation, all Pogo code generation related files are in a pogo directory\r
755 - Java jar files are now in <install_dir>/share/java\r
756 - Include files are now in <install_dir>/include/tango\r
757 \r
758 \r
759 Changes between Tango distribution 7.0.2 and 7.1.1\r
760 --------------------------------------------------\r
761 \r
762 - Updated database device server Release 4.5\r
763 - Updated TangoAccessControl device server Release 1.4\r
764 - Updated ATKCore and ATKWidget to Release 4.0.6\r
765 - Updated atkpanel to Release 4.2\r
766 - Updated Jive to Release 4.0\r
767 - Updated Pogo Release 6.2.0\r
768 - Updated Astor to Release 5.2.3\r
769 - Updated TangORB to release 7.1.0\r
770 \r
771 - A new option --with-tango-rc-file allowing the user to select the Tango rc file location has been\r
772 added to the configure script\r
773 - The value passed to the configure script option --with-tango-db-name is now also taken into account\r
774 by the database server and the controlled access server\r
775 - Man pages for binaries have been added\r
776 - omniORB detection done using pkg-config\r
777 - Pictures used in the Tango pdf documentation has been changed in order to clarify their licences\r
778 - In case TANGO_HOST is not defined as a variable environment, scripts to start the provided tools use the rc file if defined\r
779 \r
780 - Fix bug in MySQL detection\r
781 - Fix bug in case doxygen is not available on the host where the installation is performed\r
782 \r
783 \r
784 Changes between Tango distribution 6.1.1.b and 7.0.2\r
785 ----------------------------------------------------\r
786 \r
787 - Added the Tango controlled access server Release 1.3\r
788 - Updated Notifd2db.cpp file Release 1.7\r
789 - Updated database device server Release 4.3\r
790 - Updated starter device server Release 4.8\r
791 - Updated TangoTest device server Release 1.3\r
792 - Updated Astor to Release 5.2\r
793 - Updated ATKCore and ATKWidget to Release 4.0.2\r
794 - Updated Jive Release 3.21\r
795 - Updated Pogo Release 6.0.0\r
796 - Updated TangoORB Release 7.0.2\r
797 - Updated atkpanel to Release 4.1\r
798 Added a tango_wca script to start/stop a Tango control system when used with its controlled access\r
799 \r
800 Changes between Tango distribution 6.1.1.a and 6.1.1.b\r
801 ------------------------------------------------------\r
802 \r
803 - Updated ATKPanel to release 3.5\r
804 - Added the log4j jar file (used by LogViewer and Java device server)\r
805 \r
806 Changes between Tango distribution 6.1.1 and 6.1.1.a\r
807 ----------------------------------------------------\r
808 \r
809 - Notifd2db.cpp file updated to release 1.6\r
810 - Fix bug in the database update script in the history ids tables update\r
811 - Add TangORB.jar file to the CLASSPATH in the jdraw script file\r
812 - Updated TangoORB.jar file to release 6.0.2\r
813 - Added the tool_panels jar file\r
814 - Update TangoTest device server (slower data refresh frequency)\r
815 \r
816 \r