[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: KCC archiver

From: Ossama Othman
Subject: Re: KCC archiver
Date: Fri, 27 Oct 2000 10:38:09 -0700
User-agent: Mutt/1.2.5i

Hi Patrick,

On Fri, Oct 27, 2000 at 01:39:29PM +0200, Patrick Guio wrote:
> Actually when creating a library with KCC, the instruction should be
> KCC -o .libs/libmudfas3d.a libmudfas3d_la-init.o libmudfas3d_la-lop.o    
> libmudfas3d_la-mudfas.o libmudfas3d_la-prolon.o libmudfas3d_la-qnc.o 
> libmudfas3d_la-restrict.o libmudfas3d_la-restrict_ops.o 
> libmudfas3d_la-restrictphi.o libmudfas3d_la-smooth.o 
> libmudfas3d_la-smooth_ops.o
> For a shared library, use a similar command, but change the
> extension used in the library file name from .a to the appropriate
> extension for your system.
> I can hardcode the created libtool but it should be nice to have this
> included.

KCC is already supported in the multi-language branch libtool in the
CVS repository, and should do the right thing.  Specifically it uses
KCC to create static and shared libraries to pull in the appropriate
template instantiations from the template repository it creates for
each directory.  Right now it's only supported for a few platforms
(Linux being one), but it should be relatively easy to create a
generic configuration since the KCC flags are fairly consistent across
all platforms it is supported on.

Ossama Othman <address@hidden>
Distributed Object Computing Laboratory, Univ. of California at Irvine
1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068  70E6 5EB7 5E71 F7A3 94A8

reply via email to

[Prev in Thread] Current Thread [Next in Thread]