V3 Porting Guide

David Edelsohn dje@watson.ibm.com
Wed Nov 22 10:35:00 GMT 2000


	Great start, Mark.

	I think that the libtool section needs a comment about "--tags
CXX".  How about the following?

David


Index: porting.texi
===================================================================
RCS file: /cvs/gcc/egcs/libstdc++-v3/porting.texi,v
retrieving revision 1.1
diff -c -p -r1.1 porting.texi
*** porting.texi	2000/11/21 22:59:13	1.1
--- porting.texi	2000/11/22 18:32:32
*************** __atomic_add (_Atomic_word* __mem, int _
*** 417,429 ****
  @node Libtool
  @chapter Libtool
  
! The C++ library is linked with libtool.  Explaining the full workings of
! libtool is beyond the scope of this document, but there is one
! particular bit that should be explained here.  The C++ run-time library
! contains initialization code that needs to be run as the library is
! loaded.  Often, that requires linking in special object files when the
! C++ library is built as a shared library, or taking other
! system-specific actions.
  
  The V3 library is linked with the C version of libtool, even though it
  is a C++ library.  Therefore, the C version of libtool needs to ensure
--- 417,438 ----
  @node Libtool
  @chapter Libtool
  
! The C++ library is compiled, archived and linked with libtool.
! Explaining the full workings of libtool is beyond the scope of this
! document, but there are a few, particular bits that are necessary for
! porting.
! 
! Some parts of the V3 library are compiled with the libtool --tags CXX
! option (the C++ definitions for libtool).  Therefore, @file{ltcf-cxx.sh}
! in the top-level directory needs to have the correct logic to compile
! and archive objects equivalent to the C version of libtool,
! @file{ltcf-c.sh}.  Some libtool targets have definitions for C but not
! for C++, or C++ definitions which have not been kept up to date.
! 
! The C++ run-time library contains initialization code that needs to be
! run as the library is loaded.  Often, that requires linking in special
! object files when the C++ library is built as a shared library, or
! taking other system-specific actions.
  
  The V3 library is linked with the C version of libtool, even though it
  is a C++ library.  Therefore, the C version of libtool needs to ensure


More information about the Libstdc++ mailing list