llvm-6502/lib/Support/Unix
Rafael Espindola 8acff70de1 Cleanup the interface for creating soft or hard links.
Before this patch the unix code for creating hardlinks was unused. The code
for creating symbolic links was implemented in lib/Support/LockFileManager.cpp
and the code for creating hard links in lib/Support/*/Path.inc.

The only use we have for these is in LockFileManager.cpp and it can use both
soft and hard links. Just have a create_link function that creates one or the
other depending on the platform.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@203596 91177308-0d34-0410-b5e6-96231b3b80d8
2014-03-11 18:40:24 +00:00
..
Host.inc
Memory.inc
Mutex.inc
Path.inc Cleanup the interface for creating soft or hard links. 2014-03-11 18:40:24 +00:00
Process.inc [C++11] Replace llvm::tie with std::tie. 2014-03-02 13:30:33 +00:00
Program.inc Delete dead code. 2014-02-24 01:07:38 +00:00
README.txt
RWMutex.inc Fix RWMutex to be thread-safe when pthread_rwlock is not available 2014-03-01 04:30:32 +00:00
Signals.inc
system_error.inc
ThreadLocal.inc
TimeValue.inc
Unix.h
Watchdog.inc

llvm/lib/Support/Unix README
===========================

This directory provides implementations of the lib/System classes that
are common to two or more variants of UNIX. For example, the directory
structure underneath this directory could look like this:

Unix           - only code that is truly generic to all UNIX platforms
  Posix        - code that is specific to Posix variants of UNIX
  SUS          - code that is specific to the Single Unix Specification
  SysV         - code that is specific to System V variants of UNIX

As a rule, only those directories actually needing to be created should be
created. Also, further subdirectories could be created to reflect versions of
the various standards. For example, under SUS there could be v1, v2, and v3
subdirectories to reflect the three major versions of SUS.