Statically linking a shared library to another library to be statically linked

Statically linking a shared library to another library to be statically linked

[Mohit Kumar]

Hi All,

First of all, apologies for such a cryptic subject, even I took some
time to figure out how should I frame the subject but could not think
of any better way.

I am stuck with the following scenario:

Suppose I have three files: libone.a, libtwo.a and libmain.so, and I
want to implement the followinf hierarchy:
    libmain.so
        |-----libtwo.a
                   |-----libone.a

As far as linking libtwo.a to libmain.so is concerned I am aware I
need to use '-l' flag at link time.
But is there a way I can link a .a file to another .a file?

I am aware I can do the following:
ar x libone.a ----> generates all the .o's
ar q libtwo.o *.o's 

However I am looking for a cleaner way.

Any help in this regard would be highly appreciable.

Thanks,
Mohit

Fwd: Statically linking a shared library to another library to be statically linked

[Mohit Kumar]

Resending due to no response ....

---------- Forwarded message ----------
From: Mohit Kumar <mohit.kumar@gmail.com>
Date: Mon, 30 May 2005 17:52:37 +0530
Subject: Statically linking a shared library to another library to be
statically linked
To: gcc-help@gcc.gnu.org

Hi All,

First of all, apologies for such a cryptic subject, even I took some
time to figure out how should I frame the subject but could not think
of any better way.

I am stuck with the following scenario:

Suppose I have three files: libone.a, libtwo.a and libmain.so, and I
want to implement the followinf hierarchy:
    libmain.so
        |-----libtwo.a
                   |-----libone.a

As far as linking libtwo.a to libmain.so is concerned I am aware I
need to use '-l' flag at link time.
But is there a way I can link a .a file to another .a file?

I am aware I can do the following:
ar x libone.a ----> generates all the .o's
ar q libtwo.o *.o's 

However I am looking for a cleaner way.

Any help in this regard would be highly appreciable.

Thanks,
Mohit

Re: Statically linking a shared library to another library to be statically linked

[corey taylor]

Mohit,

  What is the result that you are looking for?  Do you not want to
specify libone.a if you link libtwo.a or something else?

corey

On 5/30/05, Mohit Kumar <mohit.kumar@gmail.com> wrote:
> Hi All,
> 
> First of all, apologies for such a cryptic subject, even I took some
> time to figure out how should I frame the subject but could not think
> of any better way.
> 
> I am stuck with the following scenario:
> 
> Suppose I have three files: libone.a, libtwo.a and libmain.so, and I
> want to implement the followinf hierarchy:
>     libmain.so
>         |-----libtwo.a
>                    |-----libone.a
> 
> As far as linking libtwo.a to libmain.so is concerned I am aware I
> need to use '-l' flag at link time.
> But is there a way I can link a .a file to another .a file?
> 
> I am aware I can do the following:
> ar x libone.a ----> generates all the .o's
> ar q libtwo.o *.o's
> 
> However I am looking for a cleaner way.
> 
> Any help in this regard would be highly appreciable.
> 
> Thanks,
> Mohit
>

Re: Statically linking a shared library to another library to be statically linked

[Mohit Kumar]

Hey Corey,

Exaclty, I want to be able to specify it to link libone.a directly
when it is linking libtwo.a. This is just for clarity of code and the
flow.

Thanks,
Mohit

On 6/1/05, corey taylor <corey.taylor@gmail.com> wrote:
> Mohit,
> 
>   What is the result that you are looking for?  Do you not want to
> specify libone.a if you link libtwo.a or something else?
> 
> corey
> 
> On 5/30/05, Mohit Kumar <mohit.kumar@gmail.com> wrote:
> > Hi All,
> > 
> > First of all, apologies for such a cryptic subject, even I took some
> > time to figure out how should I frame the subject but could not think
> > of any better way.
> > 
> > I am stuck with the following scenario:
> > 
> > Suppose I have three files: libone.a, libtwo.a and libmain.so, and I
> > want to implement the followinf hierarchy:
> >     libmain.so
> >         |-----libtwo.a
> >                    |-----libone.a
> > 
> > As far as linking libtwo.a to libmain.so is concerned I am aware I
> > need to use '-l' flag at link time.
> > But is there a way I can link a .a file to another .a file?
> > 
> > I am aware I can do the following:
> > ar x libone.a ----> generates all the .o's
> > ar q libtwo.o *.o's
> > 
> > However I am looking for a cleaner way.
> > 
> > Any help in this regard would be highly appreciable.
> > 
> > Thanks,
> > Mohit
> >
>

Re: Fwd: Statically linking a shared library to another library to be statically linked

[Ian Lance Taylor]

Mohit Kumar <mohit.kumar@gmail.com> writes:

> Suppose I have three files: libone.a, libtwo.a and libmain.so, and I
> want to implement the followinf hierarchy:
>     libmain.so
>         |-----libtwo.a
>                    |-----libone.a
> 
> As far as linking libtwo.a to libmain.so is concerned I am aware I
> need to use '-l' flag at link time.
> But is there a way I can link a .a file to another .a file?

This is not a gcc question.  It is a binutils question.  Or a Unix
programming question.

The answer is no.  An archive is simply a collection of object files.
There is no meaningful way to link one archive to another archive.

If you will be using only the GNU linker, you could play some tricky
games with linker scripts.  For example, look at /usr/lib/libc.so on a
typical GNU/Linux system.  But I wouldn't describe that as a clean
approach.

Ian

Re: Statically linking a shared library to another library to be statically linked

[Ishwar Rattan]

On Wed, 1 Jun 2005, Mohit Kumar wrote:

> Hey Corey,
>
> Exaclty, I want to be able to specify it to link libone.a directly
> when it is linking libtwo.a. This is just for clarity of code and the
> flow.
How does that provide clarity of code? If that is what you want,
merge libone.a libtwo.a (see ar) into a single archive and use it..

-ishwar