| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
VS 2019 is different from earlier versions of VS in the way it handles
the target platform; handle that in the fashion that much bashing on
libpcap's .appveyor.yml got to work.
|
|
|
|
|
|
| |
The base directory is missing from the archive.
[skip ci]
|
|
|
|
| |
[skip ci]
|
|
|
|
|
| |
The runtest() Perl function runs UN*X commands, so it doesn't work on
Windows.
|
|
|
|
|
|
|
| |
If you're not part of the solution, you're part of the problem. To do a
test, just build with check.vcxproj; the precise way to sacrifice a goat
over msbuild to get it to do the equivalent of "{make,ninja} check" when
building with tcpdump.sln is not exactly obvious.
|
|
|
|
|
| |
It's all Perl; no UN*X-style shell or commands should be needed any
more, and we should no longer depend on there being a Makefile.
|
| |
|
|
|
|
| |
[skip ci]
|
| |
|
| |
|
|
|
|
|
| |
(https://www.appveyor.com/docs/appveyor-yml/ is not exactly a reference
manual....)
|
|
|
|
|
|
| |
That way, we 1) make sure it builds with VS 2015 and doesn't depend on
any VS 2017-isms and 2) possibly get additional warnings from VS 2017
(and make sure it builds on VS 2017).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Some of the narrowing warnings are false positives; newer versions of
Clang do a better job than older ones of determining the range of values
of expressions, and don't warn if the range is such that it can be
safely narrowed, so maybe the same is true of MSVC.
|
|
|
|
|
| |
Tell msbuild to build in parallel. Use Windows syntax for command-line
flags. Create the .devel file.
|
| |
|
| |
|
|
|
|
|
| |
They claim the keys are case-insensitive, but the installer didn't seem
to be doing anything.
|
| |
|
| |
|
|
|
|
|
| |
This might not work, given that it is not, as far as I know, a "silent"
installer, and thus might not work in an automated environment.
|
| |
|
|
|