Jason Pyeron writes: > 2 Issues encountered and mitigated. > > 1. There are some significant changes in the functionality of 2.1.2 vs > 1.4.1. 2. The tool chain has evolved a bit since 2016, so the current > 1.4.1-1 release would not build anymore, so I have updated the cygport > as release 2. > > So I have built both 1.4.1 and 2.1.2 on Windows Server 2019 with all > updates installed.
Great. >> > check the patches for the major Linux distros (if any, Fedora does >> > not for instance) and make sure > > I started with pdfgrep's master branch, so when the next release is > made there should not be any surprises. But I did not yet review other > distro's patches. I can make master branch builds available as test > marked packages, but need guidance on version number and release > numbering first. Looks fine to me, any particular question? > I have not pushed my changes outside of my private repo, as I expect > that there will be some editorial change requests along with any > additional patching. Looks like pfsgrep doesn't need much or any patching, so I guess the only patch will be your fix for the build (which eventually should be upstreamed). >> > it works on both 32bit and 64bit architecture and show the result. > > How should I force cygport to run `make check`? In other words how do > I link the `cygport test` command to `make check` ? I read the cygport > docs, but README and html/manual/src_test_cygpart.html were not > helpful. It automatically does this (it tries to run 'make check' and if that doesn't work it tries to run 'make test'. If you need to do anything else, you would define a src-test() function in the cygport file and do whatever that is there. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds