Re: Library creation command

[Matthias Dietrich <Matthias dot Dietrich at st dot com>]

bkorb@pacbell.net wrote:
> Matthias Dietrich wrote:
>
>
> > Unfortunately we run into a big problem. Automake assumes
> > that a library is built by calling "ar cru" and at least
> > one of our machine has a toolset where "ar" is not
> > available. We have another tool to build a library, it's not
> > called "ar" and it doesn't take "cru" as arguments.
> >
> > Just to give you a little more information: this machine is
> > an embedded system on which we cannot run the compiler,
> > linker, etc. We need to cross compile from another workstation.
> > On this workstation a local "ar" is available but it breaks
> > the object files for our embedded system. So I really need to
> > use the platform-specific tool to build libraries.
> >
> > I found that replacing "ar" is possible by inserting
> > AC_SUBST(AR) into the configure.in file and then setting
> > AR to my tool. But the "cru" parameters seem to be hardcoded
> > into automake.
>
> May I recommend a shell script that takes the "cru" argument
> and invokes the appropriate tool with the appropriate args?
Thanks for your suggestion. I will look into it and see if it
fits.

But anyway I am quite surprised about the "ar" command. It
seems almost every possible tool involved in a build process
can be defined (CC,LD,CPP,CXX, etc.) but not AR. It is even
possible to redefine AR on a per-library basis using the
_AR variables, but why not having the ability to redefine AR
globally with the appropriate arguments ?


Thanks anyway,

Regards,

Matthias

--
____________________________________________________________
Matthias Dietrich          E-mail : Matthias.Dietrich@st.com

ST Microelectronics        Phone  : +33 4 76 58 67 61
AST Grenoble Lab           Fax    : +33 4 76 58 56 60

12, Rue Jules Horowitz     BP 217   F-38019 GRENOBLE Cedex
____________________________________________________________