$ ldd ./build/linux/x86_64/release/test 
	linux-vdso.so.1 =>  (0x00007ffd53bfe000)
	libtestlib.so.0 => not found

   Dynamic string tokens
       In several places, the dynamic linker expands dynamic string tokens:

       o  In the environment variables LD_LIBRARY_PATH, LD_PRELOAD, and
          LD_AUDIT,

       o  inside the values of the dynamic section tags DT_NEEDED, DT_RPATH,
          DT_RUNPATH, DT_AUDIT, and DT_DEPAUDIT of ELF binaries,

       o  in the arguments to the ld.so command line options --audit,
          --library-path, and --preload (see below), and

       o  in the filename arguments to the dlopen(3) and dlmopen(3)
          functions.

       The substituted tokens are as follows:
       $ORIGIN (or equivalently ${ORIGIN})
              This expands to the directory containing the program or shared
              object.  Thus, an application located in somedir/app could be
              compiled with
                  gcc -Wl,-rpath,'$ORIGIN/../lib'
              so that it finds an associated shared object in somedir/lib no
              matter where somedir is located in the directory hierarchy.
              This facilitates the creation of "turn-key" applications that
              do not need to be installed into special directories, but can
              instead be unpacked into any directory and still find their
              own shared objects.
       $LIB (or equivalently ${LIB})
              This expands to lib or lib64 depending on the architecture
              (e.g., on x86-64, it expands to lib64 and on x86-32, it
              expands to lib).
       $PLATFORM (or equivalently ${PLATFORM})
              This expands to a string corresponding to the processor type
              of the host system (e.g., "x86_64").  On some architectures,
              the Linux kernel doesn't provide a platform string to the
              dynamic linker.  The value of this string is taken from the
              AT_PLATFORM value in the auxiliary vector (see getauxval(3)).