Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wasm and callbacks binaries should be generated from main simapp #7231

Open
colin-axner opened this issue Aug 29, 2024 · 1 comment · May be fixed by #7445
Open

wasm and callbacks binaries should be generated from main simapp #7231

colin-axner opened this issue Aug 29, 2024 · 1 comment · May be fixed by #7445
Labels
type: productivity Increase dev productivity and throughput by improving developer tooling, infrastructure, automation

Comments

@colin-axner
Copy link
Contributor

The 08-wasm and callback modules should have binaries which are generated using the main simapp, rather than containing duplicate logic to create a binary. The main simapp is used for e2e's and is not imported by the ibc-go module

Originally posted by @colin-axner in #6710 (comment)

@crodriguezvega crodriguezvega added the type: productivity Increase dev productivity and throughput by improving developer tooling, infrastructure, automation label Sep 1, 2024
@colin-axner colin-axner moved this to Backlog 🕐 in ibc-go Sep 5, 2024
@colin-axner
Copy link
Contributor Author

colin-axner commented Oct 15, 2024

I will split this work up, for each wasm and callbacks:

  • add them into top level simapp
  • remove duplicated workflows and use workflows against top level simapp
  • remove duplicated simd + Dockerfiles

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: productivity Increase dev productivity and throughput by improving developer tooling, infrastructure, automation
Projects
Status: Backlog 🕐
Development

Successfully merging a pull request may close this issue.

2 participants