shared libobjc & multilibs ?

shared libobjc & multilibs ?

[Helge Hess]

Hi there,

what would be the best approach to make egcs support building a shared
libobjc ? I can see that libstdc++ can be build shared and static, so
this should be possible.

Does libstdc++ use this 'multilib' feature or does it use a custom
Makefile ? If so, where can I read more about 'multilibs', the configure
documentation on this topic isn't very extensive ? Is there any less
complicated example of multilibs than libstdc++ ?

Thanks
  Helge Hess
-- 
MDlink online service center
http://www.mdlink.de/

Re: shared libobjc & multilibs ?

[Jeffrey A Law]

  In message < 37526033.6B800C06@mdlink.de >you write:
  > Hi there,
  > 
  > what would be the best approach to make egcs support building a shared
  > libobjc ? I can see that libstdc++ can be build shared and static, so
  > this should be possible.
  > 
  > Does libstdc++ use this 'multilib' feature or does it use a custom
  > Makefile ? If so, where can I read more about 'multilibs', the configure
  > documentation on this topic isn't very extensive ? Is there any less
  > complicated example of multilibs than libstdc++ ?
See the libiberty makefiles and configure fragments.
jeff

Re: shared libobjc & multilibs ?

[Marcus G. Daniels]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

HH> what would be the best approach to make egcs support building a shared
HH> libobjc ? 

JL> See the libiberty makefiles and configure fragments.

I've got a automake/libtool-ified version of libobjc with added
header files for *most* of the required compiler info.¹ It also includes
a heavily-modified version of mframe (from GNUstep), and support for
building Windows DLLs.  Let me know if you want it.

¹ I don't think it will work on AIX yet because some of the GCC macros
are difficult to duplicate in a standalone way.

Re: shared libobjc & multilibs ?

[Jeffrey A Law]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

  In message < 199905311921.NAA12085@pojoaque.santafe.edu >you write:
  > 
  > HH> what would be the best approach to make egcs support building a shared
  > HH> libobjc ? 
  > 
  > JL> See the libiberty makefiles and configure fragments.
  > 
  > I've got a automake/libtool-ified version of libobjc with added
  > header files for *most* of the required compiler info.¹ It also includes
  > a heavily-modified version of mframe (from GNUstep), and support for
  > building Windows DLLs.  Let me know if you want it.
  > 
  > ¹ I don't think it will work on AIX yet because some of the GCC macros
  > are difficult to duplicate in a standalone way.
The person to get in touch with for this stuff would be Ovidiu Predescu
(ovidiu@cup.hp.com) who takes care of most of our ObjC issues.

Note that you'll probably need to get a copyright assignment on file before
we can accept the changes.

jeff

shared libobjc & multilibs ?

[Helge Hess]

Hi there,

what would be the best approach to make egcs support building a shared
libobjc ? I can see that libstdc++ can be build shared and static, so
this should be possible.

Does libstdc++ use this 'multilib' feature or does it use a custom
Makefile ? If so, where can I read more about 'multilibs', the configure
documentation on this topic isn't very extensive ? Is there any less
complicated example of multilibs than libstdc++ ?

Thanks
  Helge Hess
-- 
MDlink online service center
http://www.mdlink.de/

Re: shared libobjc & multilibs ?

[Marcus G. Daniels]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

HH> what would be the best approach to make egcs support building a shared
HH> libobjc ? 

JL> See the libiberty makefiles and configure fragments.

I've got a automake/libtool-ified version of libobjc with added
header files for *most* of the required compiler info.¹ It also includes
a heavily-modified version of mframe (from GNUstep), and support for
building Windows DLLs.  Let me know if you want it.

¹ I don't think it will work on AIX yet because some of the GCC macros
are difficult to duplicate in a standalone way.

Re: shared libobjc & multilibs ?

[Jeffrey A Law]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

  In message < 199905311921.NAA12085@pojoaque.santafe.edu >you write:
  > 
  > HH> what would be the best approach to make egcs support building a shared
  > HH> libobjc ? 
  > 
  > JL> See the libiberty makefiles and configure fragments.
  > 
  > I've got a automake/libtool-ified version of libobjc with added
  > header files for *most* of the required compiler info.¹ It also includes
  > a heavily-modified version of mframe (from GNUstep), and support for
  > building Windows DLLs.  Let me know if you want it.
  > 
  > ¹ I don't think it will work on AIX yet because some of the GCC macros
  > are difficult to duplicate in a standalone way.
The person to get in touch with for this stuff would be Ovidiu Predescu
(ovidiu@cup.hp.com) who takes care of most of our ObjC issues.

Note that you'll probably need to get a copyright assignment on file before
we can accept the changes.

jeff

Re: shared libobjc & multilibs ?

[Jeffrey A Law]

  In message < 37526033.6B800C06@mdlink.de >you write:
  > Hi there,
  > 
  > what would be the best approach to make egcs support building a shared
  > libobjc ? I can see that libstdc++ can be build shared and static, so
  > this should be possible.
  > 
  > Does libstdc++ use this 'multilib' feature or does it use a custom
  > Makefile ? If so, where can I read more about 'multilibs', the configure
  > documentation on this topic isn't very extensive ? Is there any less
  > complicated example of multilibs than libstdc++ ?
See the libiberty makefiles and configure fragments.
jeff

Re: shared libobjc & multilibs ?

[Helge Hess]

Jeffrey A Law wrote:
>   In message <37526033.6B800C06@mdlink.de>you write:
>   > Hi there,
>   >
>   > what would be the best approach to make egcs support building a shared
>   > libobjc ? I can see that libstdc++ can be build shared and static, so
>   > this should be possible.
>   >
>   > Does libstdc++ use this 'multilib' feature or does it use a custom
>   > Makefile ? If so, where can I read more about 'multilibs', the configure
>   > documentation on this topic isn't very extensive ? Is there any less
>   > complicated example of multilibs than libstdc++ ?
> See the libiberty makefiles and configure fragments.

libiberty isn't built as a shared library (at least not, when specifying
--enable-shared). I had a look at some makefiles in gcc and it seems to
me that multilibs aren't the right thing to build static and shared
library-versions. I have the impression (I don't fully understand the
gcc makefiles) that shared compilation needs to be supported 'by-hand'
in the appropriate Makefile.in's.

libstdc++ is the only library which is also build shared on my system,
so it seems I'll need to have a look at this.

Helge
-- 
MDlink online service center
http://www.mdlink.de/

Re: shared libobjc & multilibs ?

[Jeffrey A Law]

  In message < 3753E1F2.6C5CBF0B@mdlink.de >you write:
  > libiberty isn't built as a shared library (at least not, when specifying
  > --enable-shared).
But most of the hooks one needs to build a shared library can be found in
libiberty.  In particular the code to set up and build both static and sharable
versions of each .o file for each multilib.

  > I had a look at some makefiles in gcc and it seems to
  > me that multilibs aren't the right thing to build static and shared
  > library-versions.
You are correct.  multilibs are for dealing with processor variants.  If you
want to build shared libraries, you would basically need to build one for each
already existing multilib. 

  > I have the impression (I don't fully understand the
  > gcc makefiles) that shared compilation needs to be supported 'by-hand'
  > in the appropriate Makefile.in's.
It's going to need a little work -- it's not going to "just work".

  > libstdc++ is the only library which is also build shared on my system,
  > so it seems I'll need to have a look at this.
You'll have to look at it for some of the changes, but I strongly recommend 
also
reviewing libiberty. 

jeff

Re: shared libobjc & multilibs ?

[Helge Hess]

Jeffrey A Law wrote:
>   In message <37526033.6B800C06@mdlink.de>you write:
>   > Hi there,
>   >
>   > what would be the best approach to make egcs support building a shared
>   > libobjc ? I can see that libstdc++ can be build shared and static, so
>   > this should be possible.
>   >
>   > Does libstdc++ use this 'multilib' feature or does it use a custom
>   > Makefile ? If so, where can I read more about 'multilibs', the configure
>   > documentation on this topic isn't very extensive ? Is there any less
>   > complicated example of multilibs than libstdc++ ?
> See the libiberty makefiles and configure fragments.

libiberty isn't built as a shared library (at least not, when specifying
--enable-shared). I had a look at some makefiles in gcc and it seems to
me that multilibs aren't the right thing to build static and shared
library-versions. I have the impression (I don't fully understand the
gcc makefiles) that shared compilation needs to be supported 'by-hand'
in the appropriate Makefile.in's.

libstdc++ is the only library which is also build shared on my system,
so it seems I'll need to have a look at this.

Helge
-- 
MDlink online service center
http://www.mdlink.de/

Re: shared libobjc & multilibs ?

[Jeffrey A Law]

  In message < 3753E1F2.6C5CBF0B@mdlink.de >you write:
  > libiberty isn't built as a shared library (at least not, when specifying
  > --enable-shared).
But most of the hooks one needs to build a shared library can be found in
libiberty.  In particular the code to set up and build both static and sharable
versions of each .o file for each multilib.

  > I had a look at some makefiles in gcc and it seems to
  > me that multilibs aren't the right thing to build static and shared
  > library-versions.
You are correct.  multilibs are for dealing with processor variants.  If you
want to build shared libraries, you would basically need to build one for each
already existing multilib. 

  > I have the impression (I don't fully understand the
  > gcc makefiles) that shared compilation needs to be supported 'by-hand'
  > in the appropriate Makefile.in's.
It's going to need a little work -- it's not going to "just work".

  > libstdc++ is the only library which is also build shared on my system,
  > so it seems I'll need to have a look at this.
You'll have to look at it for some of the changes, but I strongly recommend 
also
reviewing libiberty. 

jeff