1. 15 Apr, 2020 1 commit
  2. 25 Feb, 2020 3 commits
  3. 24 Feb, 2020 1 commit
  4. 23 Feb, 2020 2 commits
  5. 12 Feb, 2020 2 commits
  6. 05 Feb, 2020 1 commit
  7. 29 Jan, 2020 2 commits
  8. 25 Jan, 2020 5 commits
    • sekreta's avatar
      gitlab-ci: build SWIG from source · 030125ee
      sekreta authored
      At this time of writing, every recent Ubuntu version (up the the latest 19.10)
      packages the 3.0 series of SWIG (we require 4.0). Rather than change the CI's
      image to another distro, we simply build SWIG ourselves (we can stand to benefit
      from the option anyway).
      030125ee
    • sekreta's avatar
      build: add ability to build SWIG from source + bump min req · 82eef743
      sekreta authored
      Needed for latest SWIG features + CI.
      82eef743
    • sekreta's avatar
      SWIG: impl_helper: consume header + preprocessor check · dfb798a2
      sekreta authored
      - SWIG's C++ class modifier support is a WIP. Work-around with the preprocessor.
      
      - Removes the need to declare within the interface file by consuming the entire
        header (this can, fortunately, be done).
      dfb798a2
    • sekreta's avatar
      SWIG: generic: consume header + related fixes · 69bec5d0
      sekreta authored
      - SWIG doesn't play well with every modern C++ feature. No `auto` is ok here,
        but the macro should be consumable with some interface work.
      
      - Removes the need to declare within the interface file by consuming the entire
        header (this can, fortunately, be done).
      69bec5d0
    • sekreta's avatar
      SWIG: error: consume header + preprocessor check · 9df84037
      sekreta authored
      - SWIG's C++ class modifier support is a WIP. Work-around with the preprocessor.
      
      - Removes the need to declare within the interface file by consuming the entire
        header (this can, fortunately, be done).
      9df84037
  9. 21 Jan, 2020 3 commits
  10. 18 Jan, 2020 2 commits
  11. 17 Jan, 2020 4 commits
  12. 11 Jan, 2020 2 commits
  13. 10 Jan, 2020 4 commits
  14. 31 Dec, 2019 3 commits
    • sekreta's avatar
      Sekreta: move author to AUTHORS.md · 8ab1f4e4
      sekreta authored
      8ab1f4e4
    • sekreta's avatar
      PGP: add anonimal.asc · eab99dc9
      sekreta authored
      eab99dc9
    • sekreta's avatar
      Sekreta: implement 1.0.0's first release candidate · 82625424
      sekreta authored
      When cherry-picking/rebasing this-many commits, the git-log (summarized) is as
      follows:
      
      - Architect and engineer a definitive Sekreta framework.
      
        When building a house; the walls, plumbing, wiring, interior decorating, etc.,
        all come *after* the plans have been made and the foundation has been laid.
      
        With that said, here, in Sekreta, some important aspects of the foundation
        have been laid and some of the walls have been built (API), but the plumbing
        (ASIO hooks/networking), wiring (Sekretari and crypto-related), and interior
        decorating (all other fun stuff), are not included in this candidate release.
      
        To make my point clearer: any unfinished / under-researched work has been
        stashed but, surely, when more components are completed and more anonymity
        systems are supported, the logic and design of the framework will
        eventually be strengthened by the sum of its parts. In the meantime, a series
        of candidates will most likely precede the actual v1.0.0 release.
      
      - Create a robust & reliable cross-platform / cross-processor build with code-
        coverage, continuous integration, and extensive documentation that ensures a
        developer-friendly environment.
      
      - Design and implement the framework via test-driven, benchmark-driven, and
        profile-driven development.
      
      - Integrate the first supported anonymity system (Kovri) and provide integration
        support for Sekreta's first formal superproject (Monero).
      
      - Make all the bugs and (hopefully) fix all those bugs during the process.
      
      - Repo documentation work and cleanup.
      
      Note: aside from all the research required to implement the components and
      underlying systems, the inline Doxygen documentation should cover most (if not
      all) of the remaining development history and future.
      82625424
  15. 26 Feb, 2019 1 commit
  16. 27 Jan, 2019 3 commits
  17. 10 Jan, 2019 1 commit