Changeset 3040 in Sophya for trunk/SophyaLib/Manual/sophya.tex

Timestamp:

Jul 19, 2006, 1:20:51 AM (19 years ago)

Author:

ansari

Message:

petit ajout concernant pb d initialisation des shared libs ds la doc , Reza 19/07/2006

File:

• trunk/SophyaLib/Manual/sophya.tex (modified) (1 diff)

trunk/SophyaLib/Manual/sophya.tex

@@ -415 +415 @@
 of SOPHYA persistence, as well as FITS I/O facilities. 
 Initialisation of many SOPHYA modules is performed through an initialiser class,
-which inherits from {\bf SophyaInitiator}. Static instance of each 
-initialiser class exist in the library and the various SOPHYA services
-should be operational when the user code ({\tt main()}) starts.
-However, in some cases the run time loader may not perform correctly the static 
-object initialisation. You may thus need to instanciate the initialiser class
-for the modules you use in the beginning of your main program: \\
-{\tt TArrayInitiator , HiStatsInitiator , SkyMapInitiator \ldots }
+which inherits from {\bf SophyaInitiator}. 
+\par
+Static instance of each initialiser class exist in the library and the various SOPHYA services
+should be operational when the user code ({\tt main()}) starts, except for 
+modules in the second or third shared libraries 
+({\tt libextsophya.so libPI.so}). Indeed, a problem related 
+to the initialisation of shared libraries arises on some systems
+(Darwin/Mac OS X in particular) causing program crash at start-up, 
+if static instance of initialiser class is present in the second shared library. 
+The FitsIOServer module should thus be explicitly initialised in the user 
+program. 
+\par 
+In cases where the run time loader does not perform correctly the static 
+object initialisation, the initialiser class for the modules used in the 
+program must be instanciated in the beginning of your main program: \\
+{\tt TArrayInitiator , HiStatsInitiator , SkyMapInitiator , FitsIOServer \ldots}
 %%%
 \subsection{SOPHYA persistence}