Mercurial

comparison README.md @ 168:f3084bca7317

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[Misc] Fixed all errors and all tests should pass now.
author MrJuneJune <me@mrjunejune.com>
date Mon, 19 Jan 2026 16:29:02 -0800
parents 043018c0f2f8
children
comparison
equal deleted inserted replaced
167:589bab390fb4 168:f3084bca7317
1 # Zenbu 1 # Zenbu
2 2
3 This is a mono repo where I will share all my codes and utilize them using bazel. I decied to do this since I re-use codes often and I don't want to deal with making make and cmake every time and this eliminates the problem that exists within C or C++ where using library is harder as we need to add gzillian stuff into it lmao. 3 This is a mono repo where I will share all my codes and utilize them using bazel. I decied to do this since I re-use codes often and I don't want to deal with making make and cmake every time and this eliminates the problem that exists within C or C++ where using library is harder as we need to add gzillian stuff into it lmao.
4 4
5 ## Dependency...
6
7 ```
8 clang
9 ffmpeg
10 ```
5 11
6 ## Install 12 ## Install
7 13
8 I decide to use mercurial because I got used to this over git and I frankly don't need different branches for each feature to be merged in. 14 I decide to use mercurial because I got used to this over git and I frankly don't need different branches for each feature to be merged in.
9 I also decied to use the bazel for code sharing as I mentioned above. 15 I also decied to use the bazel for code sharing as I mentioned above.
17 23
18 # mac 24 # mac
19 brew install bazel 25 brew install bazel
20 ``` 26 ```
21 27
22 I might move these binary into the repo so that it has full history of it 28 I might move these binary into the repo so that it has full history of it. I assume mercurial is installed as well.
23
24 I assume mercurial is installed as well.
25 29
26 ## Debugging Command 30 ## Debugging Command
27 31
28 ```bash 32 ```bash
29 bazel build target -c dbg 33 bazel build target -c dbg
30 i.e) bazel build //mrjunejune:mrjunejune_server -c dbg 34 i.e) bazel build //mrjunejune:mrjunejune_server -c dbg
31 ``` 35 ```
32 36
33 And run whatever your favoriate debugging tools 37 And run whatever your favoriate debugging tools
34 38
39 ## MacOS Memory checks
40
35 ```bash 41 ```bash
36 bazel run //dowa:dowa_test --run_under="valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes" 42 bazel run //dowa:dowa_test --run_under="valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes"
37 ``` 43 ```
38
39
40 ## This is for memory leak cheak in MacOS
41
42 brew install valgrind 44 brew install valgrind
43 # or use the unofficial ARM build: 45 # or use the unofficial ARM build:
44 arch -x86_64 brew install valgrind 46 arch -x86_64 brew install valgrind
45 arch -x86_64 valgrind ./test 47 arch -x86_64 valgrind ./test
46
47 ## TODO For me
48
49 - re-write markdown_to_html file in c and ffi into js
50 - launch hg-web
51 - fix warnings in dowa