mirror of
https://git.wownero.com/wownero/wownero.git
synced 2024-12-23 00:48:55 +00:00
commit
e9d90de9e1
@ -1,7 +1,7 @@
|
|||||||
# Compiling, debugging and testing efficiently
|
# Compiling, debugging and testing efficiently
|
||||||
|
|
||||||
This document describes ways of compiling, debugging and testing efficiently for various use cases.
|
This document describes ways of compiling, debugging and testing efficiently for various use cases.
|
||||||
The intented audience are developers, who want to leverage newly added tricks to Monero via `CMake`. The document will lower the entry point for these developers.
|
The intended audience are developers, who want to leverage newly added tricks to Monero via `CMake`. The document will lower the entry point for these developers.
|
||||||
Before reading this document, please consult section "Build instructions" in the main README.md.
|
Before reading this document, please consult section "Build instructions" in the main README.md.
|
||||||
Some information from README.md will be repeated here, but the aim is to go beyond it.
|
Some information from README.md will be repeated here, but the aim is to go beyond it.
|
||||||
|
|
||||||
|
@ -20,7 +20,7 @@ posted to #monero-dev on irc.libera.chat).
|
|||||||
Patches should be self contained. A good rule of thumb is to have
|
Patches should be self contained. A good rule of thumb is to have
|
||||||
one patch per separate issue, feature, or logical change. Also, no
|
one patch per separate issue, feature, or logical change. Also, no
|
||||||
other changes, such as random whitespace changes, reindentation,
|
other changes, such as random whitespace changes, reindentation,
|
||||||
or fixing typoes, spelling, or wording, unless user visible.
|
or fixing typos, spelling, or wording, unless user visible.
|
||||||
Following the code style of the particular chunk of code you're
|
Following the code style of the particular chunk of code you're
|
||||||
modifying is encouraged. Proper squashing should be done (eg, if
|
modifying is encouraged. Proper squashing should be done (eg, if
|
||||||
you're making a buggy patch, then a later patch to fix the bug,
|
you're making a buggy patch, then a later patch to fix the bug,
|
||||||
|
@ -75,7 +75,7 @@ An unsigned 32-bit little endian integer representing the Monero specific
|
|||||||
command being invoked.
|
command being invoked.
|
||||||
|
|
||||||
### Return Code
|
### Return Code
|
||||||
A signed 32-bit little integer integer representing the response from the peer
|
A signed 32-bit little endian integer representing the response from the peer
|
||||||
from the last command that was invoked. This is `0` for request messages.
|
from the last command that was invoked. This is `0` for request messages.
|
||||||
|
|
||||||
### Flags
|
### Flags
|
||||||
@ -131,7 +131,7 @@ be zero. The first fragment has the `B` bit set, neither `B` nor `E` is set for
|
|||||||
|
|
||||||
### Dummy
|
### Dummy
|
||||||
Dummy messages have the `B` and `E` bits set, the `Q` and `S` bits unset, and
|
Dummy messages have the `B` and `E` bits set, the `Q` and `S` bits unset, and
|
||||||
the `Expect Reponse` field zeroed. When a message of this type is received, the
|
the `Expect Response` field zeroed. When a message of this type is received, the
|
||||||
contents can be safely ignored.
|
contents can be safely ignored.
|
||||||
|
|
||||||
|
|
||||||
@ -149,7 +149,7 @@ contents can be safely ignored.
|
|||||||
#### (`1005` Request) Network State
|
#### (`1005` Request) Network State
|
||||||
#### (`1005` Response) Network State
|
#### (`1005` Response) Network State
|
||||||
#### (`1006` Request) Peer ID
|
#### (`1006` Request) Peer ID
|
||||||
#### (`1006` Reponse) Peer ID
|
#### (`1006` Response) Peer ID
|
||||||
#### (`1007` Request) Support Flags
|
#### (`1007` Request) Support Flags
|
||||||
#### (`1007` Response) Support Flags
|
#### (`1007` Response) Support Flags
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user