release: Prepare for 0.3.2 #1312

pull real-or-random wants to merge 1 commits into bitcoin-core:master from real-or-random:master changing 2 files +8 −3
  1. real-or-random commented at 3:28 pm on May 12, 2023: contributor
  2. in CHANGELOG.md:9 in d653e32007 outdated
     4@@ -5,7 +5,8 @@ All notable changes to this project will be documented in this file.
     5 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
     6 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
     7 
     8-## [Unreleased]
     9+## [0.3.2] - 2023-05-12
    10+We strongly recommend updating to 0.3.2 if you use or plan to use GCC >=13 to compile libsecp256k1. When in doubt, check the Clang version using `clang -v`.
    


    jonasnick commented at 3:29 pm on May 12, 2023:
    check the version with gcc -v
  3. real-or-random force-pushed on May 12, 2023
  4. jonasnick commented at 3:31 pm on May 12, 2023: contributor
    ACK 074e83cb8ea230f785fcb2a84e95a95f5fc236ad
  5. release: Prepare for 0.3.2 d490ca2046
  6. real-or-random force-pushed on May 12, 2023
  7. real-or-random commented at 8:59 pm on May 12, 2023: contributor

    Applied the following diff to mention ABI compatibility with 0.3.0 and update the date to tomorrow.

     0diff --git a/CHANGELOG.md b/CHANGELOG.md
     1index 649132b0..6c5dbb84 100644
     2--- a/CHANGELOG.md
     3+++ b/CHANGELOG.md
     4@@ -5,7 +5,7 @@ All notable changes to this project will be documented in this file.
     5 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
     6 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
     7 
     8-## [0.3.2] - 2023-05-12
     9+## [0.3.2] - 2023-05-13
    10 We strongly recommend updating to 0.3.2 if you use or plan to use GCC >=13 to compile libsecp256k1. When in doubt, check the GCC version using `gcc -v`.
    11 
    12 #### Security
    13@@ -22,7 +22,7 @@ We strongly recommend updating to 0.3.2 if you use or plan to use GCC >=13 to co
    14  - Renamed asm build option `arm` to `arm32`. Use `--with-asm=arm32` instead of `--with-asm=arm` (GNU Autotools), and `-DSECP256K1_ASM=arm32` instead of `-DSECP256K1_ASM=arm` (CMake).
    15 
    16 #### ABI Compatibility
    17-The ABI is compatible with version 0.3.1.
    18+The ABI is compatible with versions 0.3.0 and 0.3.1.
    19 
    20 ## [0.3.1] - 2023-04-10
    21 We strongly recommend updating to 0.3.1 if you use or plan to use Clang >=14 to compile libsecp256k1, e.g., Xcode >=14 on macOS has Clang >=14. When in doubt, check the Clang version using `clang -v`.
    
  8. hebasto commented at 10:10 pm on May 12, 2023: member

    I’ve made check installations:

    • Autotools:
     0$ tree $dir
     1/tmp/tmp.vsAYM7Fe9E
     2├── include
     3│   ├── secp256k1_ecdh.h
     4│   ├── secp256k1_extrakeys.h
     5│   ├── secp256k1.h
     6│   ├── secp256k1_preallocated.h
     7│   └── secp256k1_schnorrsig.h
     8└── lib
     9    ├── libsecp256k1.a
    10    ├── libsecp256k1.la
    11    ├── libsecp256k1.so -> libsecp256k1.so.2.0.2
    12    ├── libsecp256k1.so.2 -> libsecp256k1.so.2.0.2
    13    ├── libsecp256k1.so.2.0.2
    14    └── pkgconfig
    15        └── libsecp256k1.pc
    16
    173 directories, 11 files
    
    • CMake:
     0$ tree $dir
     1/tmp/tmp.C1t6Ydgg1q
     2├── include
     3│   ├── secp256k1_ecdh.h
     4│   ├── secp256k1_extrakeys.h
     5│   ├── secp256k1.h
     6│   ├── secp256k1_preallocated.h
     7│   └── secp256k1_schnorrsig.h
     8└── lib
     9    ├── cmake
    10    │   └── libsecp256k1
    11    │       ├── libsecp256k1-config.cmake
    12    │       ├── libsecp256k1-config-version.cmake
    13    │       ├── libsecp256k1-targets.cmake
    14    │       └── libsecp256k1-targets-relwithdebinfo.cmake
    15    ├── libsecp256k1.so -> libsecp256k1.so.2
    16    ├── libsecp256k1.so.2 -> libsecp256k1.so.2.0.2
    17    └── libsecp256k1.so.2.0.2
    18
    194 directories, 12 files
    
  9. hebasto commented at 10:57 am on May 13, 2023: member

    I’ve updated a CMake’s example of integration secp256k1 into a top project as its source subtree, which is the way how it will be used in Bitcoin Core.

     0cmake_minimum_required(VERSION 3.13)
     1
     2project(secp256k1-example LANGUAGES C)
     3
     4set(SECP256K1_DISABLE_SHARED ON)
     5set(SECP256K1_ENABLE_MODULE_RECOVERY ON)
     6set(SECP256K1_BUILD_BENCHMARK OFF)
     7add_subdirectory(src/secp256k1)
     8
     9add_executable(${PROJECT_NAME} src/ecdsa.c)
    10target_link_libraries(${PROJECT_NAME}
    11  secp256k1
    12  $<$<PLATFORM_ID:Windows>:bcrypt>
    13)
    14
    15include(GNUInstallDirs)
    16install(TARGETS ${PROJECT_NAME}
    17  RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
    18)
    

    It looks much cleaner than it was before.

    cc @theuni

  10. hebasto approved
  11. hebasto commented at 3:31 pm on May 13, 2023: member
    ACK d490ca2046be118258c6a0617c3461c913d1f208
  12. jonasnick commented at 4:43 pm on May 13, 2023: contributor
    ACK d490ca2046be118258c6a0617c3461c913d1f208
  13. sipa commented at 5:28 pm on May 13, 2023: contributor
    ACK d490ca2046be118258c6a0617c3461c913d1f208
  14. real-or-random merged this on May 13, 2023
  15. real-or-random closed this on May 13, 2023

  16. hebasto referenced this in commit 8a43918225 on May 13, 2023
  17. scottwad approved
  18. vmta referenced this in commit e1120c94a1 on Jun 4, 2023
  19. sipa referenced this in commit 901336eee7 on Jun 21, 2023
  20. vmta referenced this in commit 8f03457eed on Jul 1, 2023

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin-core/secp256k1. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-10-30 05:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me