Only export library targets that are really cmake libraries (Trilinos #6168)

The IMPORTEDLIBS <lib0> <lib1> ... argument currently addes the <lib0> <lib1>
etc. to the package's ${PACAKGE_NAME}_LIBRARIES variable.  This is bad because
this list of libraries was being passed to EXPORT(TARGETS ...) and was causing
a configure-time failure when "IMPORTEDLIBS m" was used (see Trilinos #6068,
comment 37).

Really we should *not* be adding IMPORTEDLIBS to ${PACAKGE_NAME}_LIBRARIES.
They are already being linked into CMake-built libraries that CMake knows
about.  However, it seems that the Trilinos package TriKota is currently
pulling in Dakota-built libraries using IMPORTEDLIBS so I think we may break
the export files if we remove IMPORTEDLIBS from ${PACAKGE_NAME}_LIBRARIES.

The temporary solution I came up with was to filter the set fo libraries in
${PACAKGE_NAME}_LIBRARIES with IF (TARGET <libName>) and only pass those
libraries to EXPORT(TARGETS ...).  That seems to do the trick.  Now we can
pass in "IMPORTEDLIBS m" and "m" will not be passed to EXPORT(TARGETS ...) but
any IMPORTEDLIBS that are actually CMake targets will get passed to
EXPORT(TARGETS ...).  In manually verified this with the Trilinos package
Zoltan.

There is currently no automated testing for any of this export file stuff.
That is a situation that needs to change pretty darn soon.
Don't assume TriBITS is in dir "tribits/" (PHI Kanban #3454)

The new setup of VERA calls the TriBITS directory "TriBITS", not "tribits".
This is not a limitation of the software, just the tests making assumptions.

Build/Test Cases Summary
Enabled Packages: TriBITS, CTeuchos, ForTeuchos, DataTransferKit, MPACT_libs, MPACT_Drivers, Insilico, COBRA_TF, CASL_MOOSE, VRIPSS
Enabled all Forward Packages
0) MPI_DEBUG => passed: passed=637,notpassed=0 (16.61 min)
1) SERIAL_RELEASE => passed: passed=546,notpassed=0 (1.49 min)
Other local commits for this build/test group: 43abe6b, 5aa669a, 5c4038e, 50aa5fd
Merge remote branch 'casl-dev/master'
Allow for usage of the checkin-test.py script for TriBITS itself.

This just uses two builds, MPI_DEBUG and SERIAL_RELEASE.  The DEBUG and
RELEASE parts are not very significant but it is important to test with MPI
enabled and disabled.
Simple checkin-test.py wrapper script for Trilinos development.

Some machines might need to set up the locations of the compilers and
therefore might need a machine-specific checkin-test.py wrapper script.

Build/Test Cases Summary
Enabled Packages: TriBITS
Enabled all Forward Packages
0) MPI_DEBUG => passed: passed=135,notpassed=0 (0.57 min)
1) SERIAL_RELEASE => passed: passed=135,notpassed=0 (0.54 min)
Other local commits for this build/test group: 5c2aa1d
Adding a documentation index.html file

This will be linked to from various sources.
Put in links to version controlled documentation

This should allow people to get to the version controlled documentation right
from the README.md file rendered on github.
Removing generation of TriBITS overview and lifecycle PDFs for now

Not sure it makes sense to generate these PDFs for now as part of this script.
Anyway, github will not render PDF documents, only html documents.
Adding a do-configure script for TriBIT dev under Trilinos
Fixing TRIBITS_ADD_ADVANCED_TEST() handling of STDERR with OUTPUT_FILE (Trilinos #6181)

It turns out that EXECUTE_PROCESS() does not allow OUTPUT_FILE and ERROR_FILE
to point to the same files.  On Unix and Linux, stderr overwrites stdout all
together.  On MS Windows, you get an error if both point to the same file.
See some of the later comments in Trilinos bug #6181 that describe the
problem.

The way that I fixed this problem is to actually just always use
OUTPUT_VARIABLE and ERROR_VARIABLE to capture console output into the same
variable and then write the file specified by the OUTPUT_FILE argument
afterward.  This captures both STDOUT and STDERR.  However, it does not
capture them in the correct order.  However, contrary to documentation
provided by CMake, STDOUT and STDERR may not be interleaved correctly,
especially if MPI is used.  In fact, it may not even output in the correct
order in serial if the machine is loaded.  See the test:

    TriBITS_CTestScripts_cmnd_3_args_1_overall_working_directory

for more details.

I also also put in a warning in the documentation for
TRIBITS_ADD_ADVANCED_TEST() about the usage of OUTPUT_FILE and the strange
behavior of STDOUT and STDERR.

Build/Test Cases Summary
Enabled Packages: TriBITS
Enabled all Forward Packages
0) MPI_DEBUG => passed: passed=135,notpassed=0 (0.56 min)
1) SERIAL_RELEASE => passed: passed=135,notpassed=0 (0.53 min)
Other local commits for this build/test group: a6988b3
Fixing usage of cmake -E compare_files instead of diff on Windows

For some reason if (WIN32 AND NOT CYGWIN) does not work anymore.

Now all TriBITS tests pass on Windows!

Build/Test Cases Summary
Enabled Packages: TriBITS
Enabled all Forward Packages
0) MPI_DEBUG => passed: passed=135,notpassed=0 (0.56 min)
1) SERIAL_RELEASE => passed: passed=135,notpassed=0 (0.53 min)
Adding links to PDF forms of documents too
Need to name this script do-configure-mpi-debug not just do-configure
Converting documentation index to simple index.html file

It is silly to use DocUtils to generate a simple index.thml file.  Also,
DocUtils does not allow you to create multiple <a href="<link1>" PDF</a>, <a
href="<link2>" PDF</a>, etc. in the document.  This is stupid.

Just get rid of the fluff and have a simple index.thml file.
Removing assumption of a 'tribits/' base dir (Trilinos #6218)

Once I allow TriBITS to be specified as a package as <projectDir>/TriBITS, you
have to make this change for the tests to pass.
Allowing for abs pakage directories under project source dir (Trilinos #6218)

These changes were done in order to support Trilinos or other projects pulling
in TriBITS as a package from the absolute variable ${PROJECT_NAME}_TRIBITS_DIR
variable.

I added a pretty good unit test and updated the documentation.
Print out <Project>_TRIBITS_DIR

This is good info to print in the basic configure output.
Adding --no-rebase --no-append-test-results
Mention where to find egdist in TriBITS source tree
Fixing a few simple typos