Proper support for passing --features
#32
Comments
|
+1 from our side. It seems that we're not able to compile a WASM that has the |
ntn-x2
added a commit
to KILTprotocol/kilt-node
that referenced
this issue
Apr 12, 2024
Fixes KILTprotocol/ticket#3300. Currently srtool does not really support features (chevdor/srtool-cli#32), so we need a workaround until features are supported in srtool. Since this is what we do anyway now, I decided to go with using the same build infrastructure we use for tests.
Ad96el
pushed a commit
to KILTprotocol/kilt-node
that referenced
this issue
Aug 20, 2024
Fixes KILTprotocol/ticket#3300. Currently srtool does not really support features (chevdor/srtool-cli#32), so we need a workaround until features are supported in srtool. Since this is what we do anyway now, I decided to go with using the same build infrastructure we use for tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This
--default-featuresCLI flag is not really working or at least not for me. Also looking into the docker image it is still doing some kind of processing, which is weird. I just want to pass feature flags, srtool should not care at all what or why I'm doing this and just forward these features.The text was updated successfully, but these errors were encountered: