Whoops, I forgot to cc the list. Sorry.
----- Forwarded message from "Brian R. Gaeke" <gaeke at
uiuc.edu> -----
Date: Thu, 13 Nov 2003 15:35:34 -0600
From: "Brian R. Gaeke" <gaeke at uiuc.edu>
To: Reid Spencer <reid at x10sys.com>
Subject: Re: [LLVMdev] Headers & Libraries
Hi Reid,
Sorry I can't go into as much detail as your question did right now, but
basically:
1) We don't have an "install" target because we haven't yet
needed one.
There's nothing wrong with writing one up.
2) Moving all our header files into the include/llvm/ directory, and merging
include/Support and include/llvm/Support, are both good ideas as well,
though it will take careful work to make sure that nothing breaks.
3) The .o files are used when we want to link all objects from a particular
library in to a tool, e.g., opt, which needs to link in all optimizations,
even those which it does not explicitly reference. There's nothing
wrong with building .a versions of all libraries, we just don't do that
right now. Check out the Makefile.rules BUILD_ARCHIVE option.
4) The GNU linker is very, very slow, mostly because it has not been tuned
for performance by its developers. Some improvements may be forthcoming
in the current CVS version of binutils; you may want to try it out.
-Brian
--
gaeke at uiuc.edu
----- End forwarded message -----
--
gaeke at uiuc.edu
