invalid file names on windows

[jrgissing]

certain file names, e.g. in v2.7.00, appear to use characters that are invalid on Windows machines

this can create issues for certain packages that are also compatible with, or simply wish to be synced to, a Windows machine

e.g. git pulls for the LAMMPS package currently fail on Windows when not excluding the kokkos lib

[crtrott]

Args. can you get output here which demonstrates that. Btw. we should get a windows server up and running this week. We are planning to add (if possible) full windows support with the next release (including for visual studio).

[jrgissing]

sure, please find that attached. in summary, looks like any file name with a colon is causing the issue

kokkos_lib_invalid_windows_file_names.txt

[mhoemmen]

@csiefer2 may be interested in the above news about Windows testing :)

[ibaned]

Looks like its basically just the use of colons (:) in the ETI files. The ETI system is up in the air anyways, but if it sticks around for the next release then we should probably just replace :: with _.

[crtrott]

Fix in #1677