[llvm-dev] Building llvm so it can be installed by other users
Tyler Hardin via llvm-dev
llvm-dev at lists.llvm.org
Thu Oct 22 23:00:29 PDT 2015
You could just tar up the files that will be installed and write a script
to put them in their respective subdirs in /usr/local. (You could probably
even steal their install script from the "install" target in their
makefile.) If you look in the build directory (or it might be some subdir
thereof*), there's usually a 1-1 correspondence between the folder names
and the names of the folders where the files go in /usr or /usr/local. (Of
course, you should check for conflicts/overwrites.)
*: It's been a while since I've compiled LLVM. I just follow the list out
of interest in their progress.
On Tue, Oct 20, 2015 at 4:26 PM, David Lobron via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hey All,
> I'm working on packaging the current version of llvm for use by other
> people at my company. As part of this, I'd like to make a tarball of my
> build, so that other users do not have to rebuild from source in order to
> use llvm for their builds. Ideally, I'd like my makefile to un-tar my
> build output, and then do a "make install" to install anything that has
> been updated - we have a standard install root called "common" that lives
> one directory up from the build directory on our build machines.
> The tricky thing I'm running into is that all of the makefiles generated
> by cmake contain absolute paths, e.g.,
> I was wondering if it's possible to build llvm in such a way that all of
> these files contain relative paths. It would be perfect for me if the
> above line, and all other generated makefile paths, would read like this:
> I tried setting -DCMAKE_INSTALL_PREFIX, but it picked up the full path- I
> wasn't sure how to tell it to keep the path relative.
> Thanks for any help you can give!
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev