Skip to content
This repository has been archived by the owner on Oct 13, 2023. It is now read-only.

How do I find the build artefacts? #218

Open
eggbean opened this issue Oct 17, 2022 · 8 comments
Open

How do I find the build artefacts? #218

eggbean opened this issue Oct 17, 2022 · 8 comments

Comments

@eggbean
Copy link

eggbean commented Oct 17, 2022

My workflow seems to successfully build but I do not know where the build artefacts are. I tried doing a find \ but it didn't find anything.

How do I determine the location of the compiled binary and man files?

jobs:
  armv7l:
    name: armv7l build
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          repository: ogham/exa
      - uses: actions-rs/toolchain@v1
        with:
          toolchain: stable
          target: armv7-unknown-linux-gnueabihf
          override: true
      - uses: actions-rs/cargo@v1
        with:
          use-cross: true
          command: build
@devdailytester
Copy link

+1,i also want to get the output binary
seems related to #44

@eggbean
Copy link
Author

eggbean commented Nov 19, 2022

Could you tell me if you figure it out? I have had this project on hold for a month now, as I still cannot find it.

@devdailytester
Copy link

i know where is the build artifact but i dont know how to move to release or do stuff with it.looking at other actions

@eggbean
Copy link
Author

eggbean commented Nov 20, 2022

You know where it is? What is the location? I can't understand why you can't upload it if you know where it is.

@devdailytester
Copy link

i dont know how to upload i tried use other,release action.
The location is like release\build
just like common cargo build.you can try build locally and get the full view its the same,

@eggbean
Copy link
Author

eggbean commented Nov 21, 2022

I don't know what you mean by release\build. Why is there a backslash? Is that the full path? I cannot find that directory.

If you know where the build artefacts are you can upload them using actions/upload-artifact@v2.

@devdailytester
Copy link

that is of course not the full path lol.
you can try compile in your local machine and see the directory,each platform has its own tweakrs(different output path).
thanks will try out that upload action.

@cheolgyu
Copy link

https://doc.rust-lang.org/cargo/commands/cargo-build.html#output-options

    - uses: actions-rs/cargo@v1
      with:
        command: build
        args: --release --verbose --package batch --bin kr_timer  --target-dir ./build
    - name: tar
      run: tar cvf kr_timer.tar.gz ./build/release/kr_timer* ./.env.prod

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants