summaryrefslogtreecommitdiff
path: root/.appveyor.yml
Commit message (Collapse)AuthorAgeFilesLines
* appveyor: add VS 2019 tests.Guy Harris2020-06-051-1/+18
| | | | | | 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.
* AppVeyor CI: Update path for extracting npcap-sdk-1.05Francois-Xavier Le Bail2020-04-181-1/+1
| | | | | | The base directory is missing from the archive. [skip ci]
* Update Npcap SDK to 1.05.Guy Harris2020-04-161-6/+6
| | | | [skip ci]
* Don't try doing checks on Windows.Guy Harris2020-02-051-1/+0
| | | | | The runtest() Perl function runs UN*X commands, so it doesn't work on Windows.
* Don't do "make check" using a solution file.Guy Harris2020-02-051-1/+1
| | | | | | | 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.
* Try doing "make check" on Windows.Guy Harris2020-02-041-0/+1
| | | | | 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.
* Use PCAP_ROOT to tell CMake where to find Npcap or WinPcap.Guy Harris2019-10-291-1/+1
|
* Use more HTTPS in URLsFrancois-Xavier Le Bail2019-08-191-1/+1
| | | | [skip ci]
* OK, does this do it?Guy Harris2019-08-101-24/+24
|
* No, it's not.Guy Harris2019-08-101-16/+16
|
* OK, is *this* how you run different builds with a different image?Guy Harris2019-08-101-0/+8
| | | | | (https://www.appveyor.com/docs/appveyor-yml/ is not exactly a reference manual....)
* Add VS 2017 to the build matrix.Guy Harris2019-08-101-0/+8
| | | | | | 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).
* Do AppVeyor builds on all branches.Guy Harris2019-01-091-5/+0
|
* Build the tcpdump-4.9 branch as well.Guy Harris2019-01-091-0/+1
|
* Build with the Npcap SDK as well as the WinPcap SDK.Guy Harris2018-12-101-0/+6
|
* See if a newer MSVC will produce fewer warnings.Guy Harris2018-09-131-2/+2
| | | | | | | 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.
* Do parallel builds, run as a developer.Guy Harris2018-09-131-1/+5
| | | | | Tell msbuild to build in parallel. Use Windows syntax for command-line flags. Create the .devel file.
* Do both 32-bit and 64-bit builds.Guy Harris2018-09-131-1/+8
|
* That didn't work, either.Guy Harris2018-02-231-5/+3
|
* Try /S.Guy Harris2018-02-231-1/+1
| | | | | They claim the keys are case-insensitive, but the installer didn't seem to be doing anything.
* OK, try Npcap.Guy Harris2018-02-231-3/+5
|
* Nope, the WinPcap installer doesn't work (hung for over 6 minutes).Guy Harris2018-02-231-2/+0
|
* Try installing WinPcap.Guy Harris2018-02-231-0/+2
| | | | | 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.
* It's tcpdump, not pcap.Guy Harris2018-01-291-1/+1
|
* First cut at a YML file for AppVeyor.Guy Harris2018-01-291-0/+20