RE: [ROOT] problem in accessing shared library from within Cint

From: Philippe Canal (pcanal@fnal.gov)
Date: Wed Feb 26 2003 - 16:15:34 MET 

>  Given a xyz.H file,  is there a tool that can generate xyzLinkDef.h
>   instead of manually typing in the entries ???

There are no tools per se.  However you can generate (or auto generate) a
linkdef file using the pragma:
	#pragma link C++ defined_in full_pathname_of_file/xyz.h;

This will generated the dictionary for classes defined in the file xyz.h

Cheers,
Philippe.

-----Original Message-----
From: owner-roottalk@pcroot.cern.ch
[mailto:owner-roottalk@pcroot.cern.ch]On Behalf Of HP Wei
Sent: Tuesday, February 25, 2003 7:11 PM
To: roottalk@cern.ch
Subject: Re: [ROOT] problem in accessing shared library from within Cint


Hi rooters,
   I took Rene's suggestion to use

   #ifndef __CINT__
   #else
   #endif

   to hide the lower level include files below the
   one which contains the desired class.

   Plus, a little bit of cleaning up the code.

   Those 'undefined references' that I posted this morning
   arose because the linker cannot find the proper libraries.

   Anyway,
   I managed to access the Box class from within CINT.
   I have not tested all the functionality yet but
   the simple test looks encouraging.

   The is the first step toward fully accessing our class library
   from within CINT.  The Box class is only the very low level
   class.  But if this works out alright, the higer level stuff
   should too in principle.

   -------------------------------------------

   Now I have another question:

   Given a xyz.H file,  is there a tool that can generate xyzLinkDef.h
   instead of manually typing in the entries ???

 THanks,
 HP

This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:09 MET