mtrojnar/osslsigncode

proxy

patatetom opened this issue · 0 comments

hi,
a local python server is used during construction and testing : the use of "noproxy" should be added "somewhere" to avoid the use of a proxy defined elsewhere ;-)
regards, lacsaP.

$ # for some reason...
$ export http_proxy=http://127.0.0.1:8123

...

$ curl -L https://github.com/mtrojnar/osslsigncode/archive/refs/tags/2.7.tar.gz > 2.7.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  711k    0  711k    0     0   128k      0 --:--:--  0:00:05 --:--:--  182k

$ tar xvf 2.7.tar.gz
osslsigncode-2.7/
...
osslsigncode-2.7/vcpkg.json

$ cd osslsigncode-2.7/

$ cmake -B build -S . -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
-- The C compiler identification is GNU 13.2.1
...
-- Build files have been written to: /tmp/osslsigncode-2.7/build

$ cmake --build build
[ 12%] Building C object CMakeFiles/osslsigncode.dir/osslsigncode.c.o
...
[100%] Built target osslsigncode

$ ctest Release
Test project /tmp/osslsigncode-2.7/build
...
❌ Errors while running CTest
Output from these tests are in: /tmp/osslsigncode-2.7/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
$ unset http_proxy

$ cmake -B . -S .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
-- Using bash completions dir /usr/share/bash-completion/completions
...
-- Build files have been written to: /tmp/osslsigncode-2.7/build

$ ctest Release
Test project /tmp/osslsigncode-2.7/build
...
✅ 100% tests passed, 0 tests failed out of 174
Total Test time (real) =   2.20 sec