You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, the behavior of make should be identical to make install but the binary installation path.
This allows users not using cosmovisor or building in another environment to examine the generated binary file BEFORE actually copying to target folder.
I would expect 'make' to build the binary correctly (currently it complains):
# github.com/comdex-official/comdex/testutil/network
testutil/network/network.go:60:23: cannot use baseapp.SetPruning("github.com/cosmos/cosmos-sdk/store/types".NewPruningOptionsFromString(val.AppConfig.BaseConfig.Pruning)) (type func(*baseapp.BaseApp)) as type []"github.com/CosmWasm/wasmd/x/wasm/keeper".Option in argument to app.New
# github.com/comdex-official/comdex/testutil/simapp
testutil/simapp/simapp.go:24:17: not enough arguments in call to app.New
have ("github.com/tendermint/tendermint/libs/log".Logger, *db.MemDB, nil, bool, map[int64]bool, string, number, app.EncodingConfig, simapp.EmptyAppOptions)
want ("github.com/tendermint/tendermint/libs/log".Logger, db.DB, io.Writer, bool, map[int64]bool, string, uint, app.EncodingConfig, "github.com/cosmos/cosmos-sdk/server/types".AppOptions, []"github.com/CosmWasm/wasmd/x/wasm/keeper".Option, ...func(*baseapp.BaseApp))
# github.com/comdex-official/comdex/x/oracle/keeper
x/oracle/keeper/query_server.go:77:15: Errorf format %d has arg req.Symbol of wrong type string
make: *** [Makefile:21: benchmark] Error 2
However... make install downloads additional modules and compilation succeeds and binary is copied to the GOPATH folder.
The text was updated successfully, but these errors were encountered:
Currently, according to mainnet upgrade https://github.com/comdex-official/networks/blob/main/mainnet/01-upgrade-comdex-1.md should run
make install
Usually, the behavior of
make
should be identical tomake install
but the binary installation path.This allows users not using cosmovisor or building in another environment to examine the generated binary file BEFORE actually copying to target folder.
I would expect 'make' to build the binary correctly (currently it complains):
However...
make install
downloads additional modules and compilation succeeds and binary is copied to the GOPATH folder.The text was updated successfully, but these errors were encountered: