Skip to content

Chore/release packaging - #347

Open
0x-r4bbit wants to merge 2 commits into
mainfrom
chore/release-packaging
Open

Chore/release packaging#347
0x-r4bbit wants to merge 2 commits into
mainfrom
chore/release-packaging

Conversation

@0x-r4bbit

Copy link
Copy Markdown
Collaborator

No description provided.

The core-module alias blocks only surfaced the dev `lgx` / `install` outputs, so
`nix build .#amm-module-lgx-portable` (the variant you distribute) didn't resolve.
Add the `-portable` aliases for both amm_module and token_module, mirroring the UI
package aliases. mkLogosModule already produces the portable variants; these just
make them addressable.
The per-module flakes couldn't build standalone, so a release repo couldn't build
them as separate modules (its CI runs `nix build .#lgx-portable` per module_path):

- modules/amm links amm_ffi, a Cargo workspace member (it path-depends on
  amm_core / token_core / twap_oracle_core), so it can only be built with the
  whole workspace as source.
- apps/amm depends on the amm_module core module, which only the root flake
  injected.

Wire them up: modules/amm pulls amm_ffi from the repo-root flake (path:../..) via
externalLibInputs; apps/amm pulls amm_module from the sibling flake
(path:../../modules/amm) with inputs.lez_core.follows so the UI and core share one
wallet, and adopts the root flake's Basecamp-safe Logos.Wallet staging (the qmldir
directive stripping the standalone postInstall was missing). Both now build
`.#lgx-portable` on their own — verified end to end.

The repo-root flake is unaffected: it builds src = ./modules/amm / ./apps/amm with
its own inputs and ignores these subdir flakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant