Skip to content

ElixirKit relies on non-umbrella /deps path #5

Description

@christhekeele

Problem

Hey all! Just trying out elixirkit in an existing umbrella application. It appears as if this use-case is not supported, as ElixirKit is doing something during release with a hard-coded /deps path expecting a non-umbrella project. Following the guide:

  • my beforeBuildCommand is: MIX_ENV=dev mix do compile + assets.deploy + release --overwrite --path tauri/target/rel
  • this works on its own
  • on cargo tauri build I get an error
Error
error: failed to get `elixirkit` as a dependency of package `example v0.1.0 ($HOME/code/umbrella_project/app/app_name/app)`

Caused by:
  failed to load source for dependency `elixirkit`

Caused by:
  unable to update $HOME/code/umbrella_project/app/app_name/deps/elixirkit/elixirkit_rs

Caused by:
  failed to read `$HOME/code/umbrella_project/app/app_name/deps/elixirkit/elixirkit_rs/Cargo.toml`

Caused by:
  No such file or directory (os error 2)
       Error failed to build app: failed to build app

Questions:

  1. Can this be made mix-project aware?
  2. If not, can the expected location of this directory be configured?

Usecase:

I'm trying to make a desktop app that communicates with a server; I want the two to share code and was trying to implement the shared code as an umbrella dependency.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions