search

gsliepen / tinc

a VPN daemon
http://tinc-vpn.org/
Other
1.87k stars 280 forks source link

Add compatibility checks to CI (old tinc & muon) #400

Closed hg closed 2 years ago

hg commented 2 years ago

old tinc

re #397

Any idea what other useful checks can be added that do not require reimplementing a second test suite?

muon

Ensures we have some level of compatibility with muon to have tinc buildable on systems with only a C compiler.

Unit tests won't run since it doesn't consider SIGABRT to be a 'proper' way of terminating a must_fail test.

Integration tests don't work for obvious reasons.

gsliepen commented 2 years ago

For me it fails to build with muon

Ah, I did not have libpkgconf-dev installed when building muon. With that in place, it works fine.

hg commented 2 years ago

Ah, I did not have libpkgconf-dev installed when building muon. With that in place, it works fine.

I guess wrapped lzo will not be available until type_name() is implemented in muon.

It was actually the reason for that clause about "optional features" not working.

IIRC cc.has_header() doesn't look up headers in subprojects, so a call to type_name cannot be removed if we want to have best experience for meson users.

samurai embedding seems buggy. The .so is not installed automatically, you have to copy it and then do some ld configuration, and even after that it failed on my machine with weird errors.

It also requires ninja or samurai to be available, which kind of defeats the point.

So we build samurai from source, too.