| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Every CPack generator sets default CPACK_PACKAGING_INSTALL_PREFIX
variable value differently so test framework should support
that correctly - previous version expected RPM/Deb /usr default and
removed it for Archive packagers as the default there is /.
|
| |
|
|
|
|
|
|
|
| |
CPack tests can now define one or more
packaging types and that test will be
executed once per generator per packaging
type. This also enables us to set default
values per packaging type for each generator
which makes tests shorter.
|
| |
|
|
|
|
|
|
| |
Content list for a certain test
should be the same between different
generators so whenever possible use
a single expected files list per
file for all generators.
|
| |
|
|
|
|
|
|
|
|
|
| |
Each generator generates its own file
format with different extensions but
they all create those file names by
a certain pattern and all of them
require the same pieces for that pattern
to work. Now we can only provide pieces
once and and each generator will use those
pieces to generate an expected file name.
|
| |
|
|
|
| |
Merge test generator specifics into
test itself.
|
| |
|
|
|
| |
Merge per generator ExpectedFiles scripts
into one per test and move it to test dir.
|
|
|
For greater transparency tests
are moved to a subfolder with
each test having its own dir.
|
