How do you build a cargo-leptos project for the x86_64-unknown-linux-musl target?

[saikatdas0790]

I've tried the following things but they didn't work:

• Adding --target x86_64-unknown-linux-musl to the cargo-leptos build command
  • cargo-leptos doesn't recognize this
• Running a plain cargo build with a musl target doesn't work because cargo leptos adds additional build parameters
• Adding a .cargo/config.toml file and adding musl as a target also makes the cargo-leptos build fail

What am I missing? Any input is appreciated 🙂

[gbj]

I just merged a PR to cargo-leptos a few days ago that may be useful here, but haven't made a new release yet.

It adds support for two additional settings for cargo-leptos in your Cargo.toml

# Pass additional parameters to the cargo process compiling to WASM
# 
# Optional. No default
lib_cargo-args = ["--timings"]

# Pass additional parameters to the cargo process to build the server
# 
# Optional. No default
bin_cargo-args = ["--timings"]

So bin-cargo-args may be a useful place to put the target.

IIRC the command to install from git is

cargo install --git https://github.com/leptos-rs/cargo-leptos

[saikatdas0790]

Hi Greg. Big fan of your work with Leptos ever since I discovered this project from theprimeagen's Leptos stream.

I'm on NixOS so currently using the Nix package maintained by Ben for cargo-leptos and that conflicts with natively installing this binary using cargo install.

I see that v2.1 for cargo-leptos has been released. I'll try the updated version and come back in case of any additional difficulties

[saikatdas0790]

I upgraded to cargo-leptos v0.2.1 as shown below:

and added this to my Cargo.toml

But I don't think it's being passed to the server being built. This is what I see on the cargo-leptos build logs:

It doesn't look like the target argument is being passed.

This repo contains the reproduction if you want to try building it yourself.

https://github.com/go-bazzinga/hot-or-not-web-leptos-ssr/tree/setup-release-build

Thoughts on what I'm doing wrong?

[gbj]

@benwis Since this was your contribution, do you have any thoughts here? My first impression was that bin_cargo-args should maybe be bin-cargo-args (which is not what's in the README), but if I do bin-cargo-args = ["--target", "x86_64-unknown-linux-musl"] I get

    1: invalid type: sequence, expected a string

If I do bin-cargo-args = "--target x86_64-unknown-linux-musl" it seems not to get passed through anyway.

[benwis]

I would recommend not using cargo-args for this, as we have another flag for setting the target. Try setting bin-target in Cargo.toml or the LEPTOS_BIN_TARGET env var. I would expect your option to fail saying you can't use target twice, but I'm open to changing the behavior of cargo-args.

[saikatdas0790]

I tried adding this to the Cargo.toml removing the entry of bin_cargo-args but it gives me a different error

I do have the target added in my toolchain

The reproduction is available here:
https://github.com/go-bazzinga/hot-or-not-web-leptos-ssr/tree/setup-release-build

Thoughts on what I'm doing wrong or something I'm missing?

[benwis]

Did you add the target to rustup? ``rustup target add x86_64-unknown-linux-musl``

…

On Tue, Nov 7, 2023, at 8:21 PM, Saikat Das wrote: I tried adding this to the Cargo.toml removing the entry of `bin_cargo-args` but it gives me a different error image <https://user-images.githubusercontent.com/7412443/281259363-9166c617-6e5e-4fe1-8281-219c081ffd06.png> image <https://user-images.githubusercontent.com/7412443/281259396-a95c2055-b2fd-4c0a-b1a5-54405c3444cb.png> Thoughts on what I'm doing wrong or something I'm missing? — Reply to this email directly, view it on GitHub <#1963 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVBTCKYYMJ2MYX55J66NALYDMCDVAVCNFSM6AAAAAA6UWNSNSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TKMBVHEYTK>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[saikatdas0790]

If you check this, you'll see that I initially tried setting the target in bin_cargo-args but that did not work and the target parameter was not passed to the cargo build statement.

#1963 (reply in thread)

Now that I'm trying the bin-target configuration in the Cargo.toml, the build doesn't even execute successfully. Even with the -vv flag, the cargo command doesn't seem to get called at all. What I'm seeing when I add the bin-target like this:

is this error:

The build script is just this:

I have also tried setting the bin-target to the default value which is "x86_64-unknown-linux-gnu" and it seems that the build fails with the same error:

This tells me that this bin-target configuration value is the culprit here because removing this value makes the build pass:

Any thoughts on the above?

[benwis]

Apologies, you want bin_target_triple= "x86_64-unknown-linux-musl" not bin-target. I don't even know why we have that one

[saikatdas0790]

So, I changed the parameter from bin-target to bin_target_triple and set the value as you advised:

And I'm running the build command with -vv to check what cargo is running:

This is what I see:

It looks like the target parameter is NOT being passed to the cargo build command as can be seen here:

The Cargo.toml being used to build the Leptos project is here:
https://github.com/go-bazzinga/hot-or-not-web-leptos-ssr/blob/setup-release-build/Cargo.toml

Is there some other value that I should also be adjusting for the target parameter to take effect?

[benwis]

One more fix, you need dashes not underscores in bin-target-triple. I have confirmed that it works

[NicTanghe]

Hello i was just messing about with a dev container where i also want to compile for wasi-threads.
I was wondering if this is even a thing that makes sence having 2 compile targets?

I c the op hit a similar bump.

[benwis]

Hello i was just messing about with a dev container where i also want to compile for wasi-threads. I was wondering if this is even a thing that makes sence having 2 compile targets?

I c the op hit a similar bump.

I think you should create a new thread for this. I'm not quite sure what you're doing but we do compile the backend for wasip1 and wasip2