From ea8c7c2ca6f36f83bf3c021d61a8fd123b5c205d Mon Sep 17 00:00:00 2001 From: Nasfame Date: Tue, 12 Mar 2024 07:04:37 +0530 Subject: [PATCH 1/3] make: add default --- Makefile | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Makefile b/Makefile index 0e069a076..ec8a8ebeb 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,14 @@ # Each major sub-repository in this monorepo has their own Makefiles; # instead of making an even more compilicated common one, let's delegate to them. +default: + cd ipc/contracts + make gen + cd .. + cargo build --release + ./target/release/ipc-cli --version + ./target/release/fendermint --version + SUBTREES := fendermint ipc ipld/resolver contracts test: $(patsubst %, test/%, $(SUBTREES)) From b02693060d6799d3d019dc3a4139c539e4b15890 Mon Sep 17 00:00:00 2001 From: Nasfame Date: Tue, 12 Mar 2024 07:05:24 +0530 Subject: [PATCH 2/3] doc: default --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 8614d76ca..e777843e9 100644 --- a/README.md +++ b/README.md @@ -17,6 +17,7 @@ On Linux (links and instructions for Ubuntu): - Install Foundry. See [instructions](https://book.getfoundry.sh/getting-started/installation). On MacOS: + - Install Xcode from App Store or terminal: xcode-select --install - Install Homebrew: https://brew.sh/ - Install dependencies: brew install jq @@ -24,7 +25,6 @@ On MacOS: - Install Cargo make: cargo install --force cargo-make - Install docker: https://docs.docker.com/desktop/install/mac-install/ - Install foundry: https://book.getfoundry.sh/getting-started/installation - ## Building @@ -37,10 +37,8 @@ sudo usermod -aG docker $USER && newgrp docker # clone this repo and build git clone https://github.com/consensus-shipyard/ipc.git -cd ipc/contracts -make gen -cd .. -cargo build --release +cd ipc +make # building will generate the following binaries ./target/release/ipc-cli --version @@ -68,11 +66,13 @@ make test **We've prepared a [quick start guide](https://docs.ipc.space/quickstarts/deploy-a-subnet) that will have you running and validating on your own subnet quickly, at the cost of detailed explanations.** For further documentation, see: + - [docs/contracts.md](./docs/ipc/contracts.md) for instructions on how to deploy FEVM actors on subnets. - [docs/usage.md](./docs/ipc/usage.md) for instructions on how to use the `ipc-cli` to interact with subnets (from managing your identities, to sending funds to a subnet). - [docs/deploying-hierarchy.md](./docs/ipc/deploying-hierarchy.md) for instructions on how to deploy your own instance of IPC on a network. If you are a developer, see: + - [docs/developers.md](./docs/ipc/developers.md) for useful tips and guides targeted for IPC developers. ## Connecting to a rootnet @@ -80,6 +80,7 @@ If you are a developer, see: You can deploy an IPC hierarchy from any compatible rootnet. The recommended option is to use Filecoin Calibration, but you can also deploy your own. ### Running a subnet in Calibration + Calibration is the primary testnet for Filecoin. It already hosts the IPC actors and can be used as a rootnet on which to deploy new subnets. In order to use the `ipc-cli` with Calibration we need to have access to a full node syncing with the network. The easiest way to achieve this is to use a [public RPC](https://docs.filecoin.io/networks/calibration/rpcs/). You also need the addresses of the deployed contracts. From 7e1e45e5069098e0e8da54451544ec4c01f41249 Mon Sep 17 00:00:00 2001 From: Nasfame Date: Tue, 12 Mar 2024 07:09:02 +0530 Subject: [PATCH 3/3] bugfixes: make --- Makefile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Makefile b/Makefile index ec8a8ebeb..43ecc8b06 100644 --- a/Makefile +++ b/Makefile @@ -2,9 +2,7 @@ # instead of making an even more compilicated common one, let's delegate to them. default: - cd ipc/contracts - make gen - cd .. + cd contracts && make gen cargo build --release ./target/release/ipc-cli --version ./target/release/fendermint --version