1
0
Commit Graph

22 Commits

Author SHA1 Message Date
SomberNight
3fbd8df7df bump libsecp256k1 version (0.4.1->0.5.0) 2024-05-29 14:49:32 +00:00
SomberNight
2ca180ddee bump libsecp256k1 version 2024-02-21 16:39:05 +00:00
SomberNight
e346d36851 bump libsecp256k1 version 2023-09-25 13:11:03 +00:00
SomberNight
c049b461bb bump libsecp256k1 version 2023-05-26 13:22:35 +00:00
SomberNight
2a2b683d23 bump libsecp256k1 version 2023-04-21 14:13:32 +00:00
SomberNight
c66411f47e contrib/make_libsecp256k1.sh: rm Makefile patch
unneeded since c0cd7de6d4
and in fact buggy since 0bd3e4243c

related https://github.com/spesmilo/electrum/pull/8185#issuecomment-1416171287
2023-02-03 17:36:46 +00:00
SomberNight
7d83335e34 bump libsecp256k1 version
now there are tags :O
2023-02-03 17:11:16 +00:00
SomberNight
65ae281180 build: don't hardcode num worker threads "make -j4" 2022-12-03 22:50:18 +00:00
SomberNight
6f311c8930 appimage build: better caching, both locally and on CI 2022-11-04 15:49:16 +00:00
TadeuBAS
39c3d0585d build scripts: add quotes around some paths (#7949)
* Update make_libsecp256k1.sh

Avoid error when parent folder has spaces `./make_libsecp256k1.sh: line 31: cd: too many arguments`

* Avoid error when parent folder has spaces, fix for make_libsecp256k1.sh, make_zbar.sh and make_libusb.sh

Co-authored-by: ghost43 <somber.night@protonmail.com>
2022-08-24 14:18:39 +00:00
SomberNight
5cf5c03f50 bump libsecp256k1 version 2022-02-22 17:35:14 +01:00
SomberNight
f1f584c4c4 windows build: separate 32/64 bit build caches
specify which architecture to target by setting WIN_ARCH env var
2021-03-07 20:02:38 +01:00
SomberNight
21e46fb147 contrib: add instructions re cross-compiling libsecp to Linux x86
related: #6669

(note that instructions assume this commit as otherwise AUTOCONF_FLAGS is overwritten!)

based on https://stackoverflow.com/a/17748092
2020-10-21 03:27:42 +02:00
ghost43
fc89c8ffa9 win binary: build zbar ourselves (#6593)
This allows bundling much newer zbar that includes many fixes.
related: #6018

This is largely based on
https://github.com/Electron-Cash/Electron-Cash/pull/1362
https://github.com/Electron-Cash/Electron-Cash/pull/1363
https://github.com/Electron-Cash/Electron-Cash/pull/1365
eda015908e
2020-09-15 15:35:57 +00:00
fanquake
3cebbda5b1 contrib: disable building secp256k1 exhaustive tests 2020-06-21 09:08:52 +08:00
fanquake
9f8cb568b9 contrib: disable building secp256k1 benchmarks 2020-06-21 09:08:16 +08:00
fanquake
fec75fba41 contrib: secp256k1 no longer has a --disable-jni option
It was removed in https://github.com/bitcoin-core/secp256k1/pull/682
2020-06-21 09:03:48 +08:00
SomberNight
f5f3394552 git sanity: enforce "git checkout commithash" actually pulls commit
If there is a collision between a branch name and a commit hash, git
will choose the branch, even if the full 40-hex-long commit hash is
given. GitHub disallows branches/tags with such a name but git itself
does not. By adding the `^{commit}` syntax sugar after a ref name,
we can tell git that we want the commit hash to be preferred,
and hence we don't need to trust GitHub (only git).

see https://security.stackexchange.com/questions/225411/
2020-06-16 19:55:17 +02:00
SomberNight
83cabccdb5 bump libsecp256k1 version 2020-06-15 16:56:36 +02:00
SomberNight
875e6b31b1 make_libsecp256k1.sh: add comment how to cross-compile to Windows
related: #5976, #6054
2020-03-29 07:51:48 +02:00
SomberNight
5b84e714f2 build: workaround for 'realpath' missing on macOS 2020-02-11 16:48:28 +01:00
SomberNight
4cec098d2d build: create a standalone build script for libsecp256k1
heavily based on Electron-Cash/Electron-Cash@eda015908e
2020-02-11 16:48:24 +01:00