Re: Support for creating shared C++ libraries on BeOS

[Ralf Wildenhues]

Hi Christian,

* Christian Biesinger wrote on Sun, Oct 09, 2005 at 03:41:42AM CEST:
> Hi,
> the attached patch fixes (implements) C++ support for shared libraries 
> on BeOS. It just copies the C part to the C++ section; this works fine, 
> I tested on Zeta.

Thank you for the patch!

> The patch was made against libtool 1.5.16; it seems to apply to 1.5.20 
> as well.
> 
> Would be great if you could check it in. Looking at branch-2-0, it seems 
> that the same idea can be applied there, as well as on HEAD (assuming 
> libltdl/m4/libtool.m4 is the right file to look at).

branch-2-0 is dead, 2.0 will be released from what is now CVS HEAD.
I have checked in the following patches to CVS HEAD and branch-1-5,
respectively.

Maybe you could take a look at the FIXME mentioned?  Also, we love to
see testsuite output.. ;-)

Cheers,
Ralf

CVS HEAD:
2005-10-09  Christian Biesinger  <address@hidden>

        * libltdl/m4/libtool.m4 (_LT_LANG_CXX_CONFIG) [ beos ]:
        Initial shared library support for C++.

Index: libltdl/m4/libtool.m4
===================================================================
RCS file: /cvsroot/libtool/libtool/libltdl/m4/libtool.m4,v
retrieving revision 1.25
diff -u -r1.25 libtool.m4
--- libltdl/m4/libtool.m4       5 Oct 2005 15:57:05 -0000       1.25
+++ libltdl/m4/libtool.m4       9 Oct 2005 06:22:50 -0000
@@ -5172,6 +5172,18 @@
           fi
         fi
         ;;
+
+      beos*)
+       if $LD --help 2>&1 | $GREP ': supported targets:.* elf' > /dev/null; 
then
+         _LT_TAGVAR(allow_undefined_flag, $1)=unsupported
+         # Joseph Beckenbach <address@hidden> says some releases of gcc
+         # support --undefined.  This deserves some investigation.  FIXME
+         _LT_TAGVAR(archive_cmds, $1)='$CC -nostart $libobjs $deplibs 
$compiler_flags ${wl}-soname $wl$soname -o $lib'
+       else
+         _LT_TAGVAR(ld_shlibs, $1)=no
+       fi
+       ;;
+
       chorus*)
         case $cc_basename in
           *)


branch-1-5:
2005-10-09  Christian Biesinger  <address@hidden>

        * libtool.m4 (AC_LIBTOOL_LANG_CXX_CONFIG) [ beos ]:
        Initial shared library support for C++.

Index: libtool.m4
===================================================================
RCS file: /cvsroot/libtool/libtool/Attic/libtool.m4,v
retrieving revision 1.314.2.114
diff -u -r1.314.2.114 libtool.m4
--- libtool.m4  5 Oct 2005 15:57:28 -0000       1.314.2.114
+++ libtool.m4  9 Oct 2005 06:23:35 -0000
@@ -2940,6 +2940,18 @@
       fi
     fi
     ;;
+
+  beos*)
+    if $LD --help 2>&1 | grep ': supported targets:.* elf' > /dev/null; then
+      _LT_AC_TAGVAR(allow_undefined_flag, $1)=unsupported
+      # Joseph Beckenbach <address@hidden> says some releases of gcc
+      # support --undefined.  This deserves some investigation.  FIXME
+      _LT_AC_TAGVAR(archive_cmds, $1)='$CC -nostart $libobjs $deplibs 
$compiler_flags ${wl}-soname $wl$soname -o $lib'
+    else
+      _LT_AC_TAGVAR(ld_shlibs, $1)=no
+    fi
+    ;;
+
   chorus*)
     case $cc_basename in
       *)
@@ -2948,7 +2960,6 @@
        ;;
     esac
     ;;
-
 
   cygwin* | mingw* | pw32*)
     # _LT_AC_TAGVAR(hardcode_libdir_flag_spec, $1) is actually meaningless,