Re: [lmi-commits] [lmi] master 4e8d281 4/6: Relocate lmi's build directory

[Vadim Zeitlin]

On Wed, 24 Apr 2019 16:47:17 -0400 (EDT) Greg Chicares <address@hidden> wrote:

GC> branch: master
GC> commit 4e8d28122c253f6a0836e8921fc033d558872e60
GC> Author: Gregory W. Chicares <address@hidden>
GC> Commit: Gregory W. Chicares <address@hidden>
GC> 
GC>     Relocate lmi's build directory
GC>     
GC>     This is the first in a series of changes to the directory structure,
GC>     all of which may require rebuilding.
GC>     
GC>     Formerly, object files for a default build were written in
GC>       /opt/lmi/src/build/lmi/gcc/ship/
GC>     but now they're instead written in
GC>       /opt/lmi/gcc/build/ship/

 As long as we're changing things anyhow, wouldn't it make more sense to
use /opt/lmi/build/gcc/ship? I.e. the idea is that you could safely do "rm
-rf /opt/lmi/build" entirely and be sure not to lose anything important.

 Of course, this is a pretty minor difference, but it seems more logical to
have build/{gcc,clang} rather than {gcc,clang}/build. Unless you plan to
have any other subdirectories under "gcc"?

VZ

pgpHe8g14lNJV.pgp
Description: PGP signature