#mobile build not works

301 messages · Page 1 of 1 (latest)

rustic dagger
#
       Error failed to get project out directory: failed to get cargo metadata: cargo metadata command exited with a non zero exit code: error: failed to parse manifest at `/home/runner/work/Plan2Go/Plan2Go/src-tauri/Cargo.toml`

Caused by:
  can't find library `app`, rename file to `src/lib.rs` or specify lib.path

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
#

I did follow every step in the guide!

grim temple
rustic dagger
#

I have that file!

#

Oh wait, git didn't add the files

#

Let me verify if this works now!

rustic dagger
grim temple
#

yarn build for whatever reason runs tauri build which compiles the app for the current host, meaning linux for which you're missing the system deps (gtk, webkitgtk etc)

rustic dagger
#

Oh wait it install dependcies not because if: matrix.platform == 'ubuntu-22.04' and it not runs in matrix

rustic dagger
#

Btw is there maybe a 'correct' workflow for mobile builds?

rustic dagger
# grim temple `yarn build` for whatever reason runs `tauri build` which compiles the app for t...

error[E0599]: no method named `into_i32` found for enum `timeout::Timeout` in the current scope
  --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/xdg/zbus_rs.rs:72:38
   |
72 |                 notification.timeout.into_i32(),
   |                                      ^^^^^^^^ method not found in `timeout::Timeout`
   |
  ::: /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/timeout.rs:3:1
   |
3  | pub enum Timeout {
   | ---------------- method `into_i32` not found for this enum

For more information about this error, try `rustc --explain E0599`.
error: could not compile `notify-rust` due to previous error
warning: build failed, waiting for other jobs to finish...
       Error failed to build app: failed to build app
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
grim temple
#

afaik notify-rust does not work on android (and ios?) so i think you won't get around removing that dep on mobile targets

rustic dagger
#

But how?

grim temple
#

for example by specifying the dep like this ```rs
[target.'cfg(any(target_os = "windows", target_os = "linux", target_os = "macos"))'.dependencies]
notify-rust = {}

and then use the same config in your code on the dep imports/usages ```rs
#[cfg(any(...))]
{
  // desktop only
}
rustic dagger
grim temple
#

either PWA or other crates. notifications on mobile work quite differently. you could also modify the android studio and xcode projects to do it directly in kotlin and swift(?) if there's no other crate out there

rustic dagger
#
       Error failed to get project out directory: failed to get cargo metadata: cargo metadata command exited with a non zero exit code: error: failed to parse manifest at `/home/runner/work/Plan2Go/Plan2Go/src-tauri/Cargo.toml`
Caused by:
  failed to parse `cfg{any(target_os = "windows", target_os = "linux", target_os = "macos")}` as a cfg expression: invalid target specifier: unexpected `(` character, cfg expressions must start with `cfg(`
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
grim temple
#

whoops lemme edit the example

#

[] instead of {}

#

or ()

#

one of them was it x)

#

okay yeah, it was () if i can trust my own file

rustic dagger
#

Uhmm it still says:


error[E0599]: no method named `into_i32` found for enum `timeout::Timeout` in the current scope
  --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/xdg/zbus_rs.rs:72:38
   |
72 |                 notification.timeout.into_i32(),
   |                                      ^^^^^^^^ method not found in `timeout::Timeout`
   |
  ::: /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/timeout.rs:3:1
   |
3  | pub enum Timeout {
   | ---------------- method `into_i32` not found for this enum

For more information about this error, try `rustc --explain E0599`.
error: could not compile `notify-rust` due to previous error
warning: build failed, waiting for other jobs to finish...
       Error failed to build app: failed to build app
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
``` ...
rustic dagger
grim temple
#

nope, i don't build for mobile and i don't know of any repo/workflow doing it either

#

actually another cause could be the missing android target for the toolchain

rustic dagger
grim temple
#

it must be inside the action because it must be installed on the runner

#

but yarn build prevents the runner from ever reaching that line

#

to be clear: remove yarn build from the Install app dependencies step. you're only wasting build time there.
or alternatively, remove tauri build from your package.json build script, the intention of this step is only to build your frontend not the whole tauri app (which is also unnecessary if you configured beforeBuildCommand to build your frontend), buuuut i'm just repeating myself here lol

rustic dagger
#

UHmmmm

#

Uhmm please edit the file so it works

#

if the latest run (now running) not works

rustic dagger
rustic dagger
# grim temple to be clear: remove `yarn build` from the `Install app dependencies` step. you'r...

error: failed to run custom build command for `wry v0.22.0`

Caused by:
  process didn't exit successfully: `/home/runner/work/Plan2Go/Plan2Go/src-tauri/target/debug/build/wry-8477385d03914511/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=WRY_ANDROID_REVERSED_DOMAIN
  cargo:rerun-if-env-changed=WRY_ANDROID_APP_NAME_SNAKE_CASE
  cargo:rerun-if-env-changed=WRY_ANDROID_KOTLIN_FILES_OUT_DIR

  --- stderr
  thread 'main' panicked at '`WRY_ANDROID_REVERSED_DOMAIN` is not set, which is needed to generate the kotlin files for android.', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wry-0.22.0/build.rs:19:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
       Error `Failed to run `cargo build`: Command "cargo build --package app --manifest-path /home/runner/work/Plan2Go/Plan2Go/src-tauri/Cargo.toml --target aarch64-linux-android --color always" didn't complete successfully, exiting with code 101.
Error: Process completed with exit code 1.
grim temple
rustic dagger
grim temple
#

Yeah I've seen the workflow, but the issue is that the project itself uses Tauri 1.2

#

As in, the Cargo.toml file lists 1.2 instead of the 2.0 alpha

rustic dagger
#

Oke...

rustic dagger
#

Oh wait, it was generated in the first place

grim temple
rustic dagger
#

Check

#

let me test the desktop building first

#

Mobile build:

error[E0432]: unresolved imports `tauri::SystemTray`, `tauri::SystemTrayMenu`, `tauri::SystemTrayMenuItem`, `tauri::SystemTrayEvent`, `tauri::api::dialog`
 --> src/main.rs:6:13
  |
6 | use tauri::{SystemTray, SystemTrayMenu, SystemTrayMenuItem, SystemTrayEvent, CustomMenuItem, Manager, api::dialog::ask, RunEvent, WindowE...
  |             ^^^^^^^^^^  ^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^                                ^^^^^^ could not find `dialog` in `api`
  |             |           |               |                   |
  |             |           |               |                   no `SystemTrayEvent` in the root
  |             |           |               no `SystemTrayMenuItem` in the root
  |             |           no `SystemTrayMenu` in the root
  |             no `SystemTray` in the root

error[E0599]: no method named `system_tray` found for struct `tauri::Builder` in the current scope
  --> src/main.rs:16:6
   |
16 |     .system_tray(SystemTray::new().with_menu(tray_menu))
   |      ^^^^^^^^^^^ method not found in `tauri::Builder<tauri_runtime_wry::Wry<EventLoopMessage>>`

warning: unused import: `Manager`
 --> src/main.rs:6:94
  |
6 | use tauri::{SystemTray, SystemTrayMenu, SystemTrayMenuItem, SystemTrayEvent, CustomMenuItem, Manager, api::dialog::ask, RunEvent, WindowE...
  |                                                                                              ^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
#

AL right

#

so it doesn't allow systemtray

#

which is logic

#

but shouldn't it skip it because:

#![cfg_attr(
  all(not(debug_assertions), target_os = "windows"),
  windows_subsystem = "windows"
)]
```?
rustic dagger
#

Do you have any recommendations on how to cache the tauri next branch thingy?

Cause I don't want to have to wait like 5 minutes for that thing to be build so I can then see that MY CODE still not works

grim temple
#

Do you have any recommendations on how to cache the tauri next branch thingy?
you could use a prebuilt binary from tauri's gh release, it was recently released so there shouldn't be too many changes you'd be missing

#

or try switching these 2 steps idk

rustic dagger
grim temple
rustic dagger
#

Btw this is now just for Android, not yet IOS

#

Oh shit it failed

#

I forgot to remove the checker thingy

#[cfg(desktop)]
fn main() {
grim temple
#

actually

#

if you remove that i think it will fail again because of missing imports

rustic dagger
#

Nope

#

Or mabe

grim temple
#

maybe just try 2 main functions, one for desktop one for mobile, and guard them with #[cfg(desktop)] (and not(dekstop) )

rustic dagger
#

But it checks

#

if running mobile

#

if cfg!(desktop) {

grim temple
#

cfg!(desktop) resolves to a boolean

#

while #[cfg()] will completely remove the irrelevant code

rustic dagger
#

yes

#

Oh

#

Maybe it will work the way I have it now, else I will change it up again

#

Oke will just use that other way

#

Btw why does this error happen at IOS:

 tauri ios init
error: The subcommand 'ios' wasn't recognized

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Usage: yarn run tauri [OPTIONS] <COMMAND>

For more information try '--help'
error Command failed with exit code 2.
Error: Process completed with exit code 2.
grim temple
#

wrong cli version

rustic dagger
grim temple
#

you're not using the cli download from git in the ios job so it uses whatever is listed in package.json

rustic dagger
#

But this downloads cli from git, right?

        git clone -b next https://github.com/tauri-apps/tauri
        cd tauri/tooling/cli/node
        yarn
        yarn build
grim temple
#

correct, you download and build it, but you don't actually use it

#

just compare your android and ios jobs i guess

rustic dagger
#

It installs the tool, right?

grim temple
#

no

#

it just builds it

rustic dagger
#

Android is now successful! Lets goo!

grim temple
#

nice

rustic dagger
grim temple
#

well, the first question would be, why? :D

#

can't it just do the same as the android version?

rustic dagger
#

IDK, I didn't write it!

rustic dagger
#

So my next question would be, what do we get out of yarn build of the next branch cli thingy? Where is the tauri command file thingy located after building it?

Or Maybe better: How to replace the yarn tauri with the newly builded tauri command?

grim temple
#

because it works better
i doubt that, it's the same cli, just wrapped with napi-rs so that it's shippable as a npm package.

where is it
tooling/cli/node/tauri.js i think

#

honestly i'd just use the same thing you used in the android version, it should even be slightly faster to build

rustic dagger
#

Hmm...

#

at android: ```yml
- name: Build apk
run: tauri/tooling/cli/target/debug/cargo-tauri android build --split-per-abi --debug

Thats where the cargo builded thingy is at least...
#

and yarn build runs: cross-env TARGET=node napi build --platform as seen in the package.json of the cli/node

#

Btw also one quick question: Does IOS also not need to run the yarn build inside my app folder or does ios need the yarn build (and then of course combined with yarn tauri ios build)

#

I guess I will switch to the cargo version

#

After 10 minutes of waiting:

Run tauri/tooling/cli/target/debug/cargo-tauri ios init
  
       Error No code signing certificates found. You must add one and set the certificate development team ID on the `tauri > bundle > iOS > developmentTeam` config value or the `TAURI_APPLE_DEVELOPMENT_TEAM` environment variable. To list the available certificates, run `tauri info`.
Error: Process completed with exit code 1.
grim temple
#

afaik there is no alternative than to actually pay apple

high adder
#

there are some way to get free cert

#

for example townhouse, etc

rustic dagger
#

Umm, than I will 'disable' ios (for now)

#

Btw the cache action: No cache found

rustic dagger
#

The following warnings were emitted during compilation:

warning: `"pkg-config" "--libs" "--cflags" "javascriptcoregtk-4.1" "javascriptcoregtk-4.1 >= 2.24"` did not exit successfully: exit status: 1

error: failed to run custom build command for `javascriptcore-rs-sys v0.5.1`

Caused by:
  process didn't exit successfully: `/home/runner/work/Plan2Go/Plan2Go/src-tauri/target/release/build/javascriptcore-rs-sys-d80cdd012bd7e89b/build-script-build` (exit status: 1)
grim temple
rustic dagger
#

And now ubuntu has the ```

error[E0599]: no method named into_i32 found for enum timeout::Timeout in the current scope
--> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/xdg/zbus_rs.rs:72:38
|
72 | notification.timeout.into_i32(),
| ^^^^^^^^ method not found in timeout::Timeout
|
::: /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-rust-4.5.10/src/timeout.rs:3:1
|
3 | pub enum Timeout {
| ---------------- method into_i32 not found for this enum

For more information about this error, try rustc --explain E0599.
error: could not compile notify-rust due to previous error
warning: build failed, waiting for other jobs to finish...
Error failed to build app: failed to build app
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.

problem
grim temple
#

a) it's not building the web but the tauri app because your package.json script still does tauri build, and your frontend doesn't need to be built since it's all static

#

still weird tho

#

cause even if you remove that step, it will fail in the last step with the same error

rustic dagger
#

Oke

#

Oh wait, the tauri action also does it

rustic dagger
#

I guess I will just do that

rustic dagger
#

Uhmm

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileArm64DebugJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':app:arm64DebugCompileClasspath'.
   > Could not resolve project :tauri-android.
     Required by:
         project :app
      > No matching configuration of project :tauri-android was found. The consumer was configured to find an API of a component, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'com.android.build.api.attributes.ProductFlavor:abi' with value 'arm64', attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.3.1', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
          - None of the consumable configurations have attributes.
grim temple
#

no idea tbh. can't remember seeing that before

rustic dagger
#

What I did was update the version of tauri to the newest 2.0-alpha, but I did not disable the next branch building task afaik

rustic dagger
#

Any updates or ideas?

#

I think I will be trying the build at least now again, to see if the updated Next branch might already have fixed it. (btw it is using the next branch binary, but still for android builds the branch)

rustic dagger
#

Any ideas for this now?

grim temple
#

nope

rustic dagger
#

tauri/tooling/cli/target/debug/cargo-tauri android build --split-per-abi --debug

glass herald
#

did alpha.3 uses javascriptcore-4.1?

#

Is there any workaround because webkit2gtk is still in javascriptcore-4.0

grim temple
#

yes, alpha.3 switched the jsc version, but it also switched webkit2gtk versions to libwebkit2gtk-4.1

glass herald
rustic dagger
#

Hmm...

grim temple
glass herald
#

Had to comment some lines, it runs. Thanks

rustic dagger
grim temple
#

well, i wouldn't call it strange. init only inits your project, like adding the android studio project. build actually tries to build the project so that's where all the juicy stuff actually happens

rustic dagger
# grim temple well, i wouldn't call it strange. `init` only inits your project, like adding th...

But the build says:

No matching configuration of project :tauri-android was found. The consumer was configured to find a runtime of a component, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'com.android.build.api.attributes.ProductFlavor:abi' with value 'arm64', attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.3.1', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:

#

Maybe I should actually remove the building of the tauri next branch and completly use the the release thingy

grim temple
#

did you ever try it locally before?

rustic dagger
#

Nope, I don't have a linux enviroment

grim temple
#

you don't need to. you can build android on windows and macos too

rustic dagger
#

And my laptop is not really going to be able to run it

grim temple
#

that's fair

rustic dagger
#

It cannot even run MInecrfat Bedrock good enough

#

and like too less space

#

But it did work once... and then I updated the tauri version with npm and it now no longer works

grim temple
#

now that's interesting

rustic dagger
#

Yeah true.. But maybe I should just remove the tauri next branch building step... (or bettter just remove the usage, for now)

grim temple
#

would definitely speed up the workflow a bit at least

rustic dagger
#

let me just try with using tauri commnd first

grim temple
#

fwiw it builds fine in my fork of your repo, but it always gets stuck at the end of the build step for some reason

rustic dagger
#

Oh wait I messed up

#

Wait

#

Wait what? Why is the tauri command not existing now?

grim temple
#

it's yarn tauri android x (or npm run tauri android x)

rustic dagger
#

oh

#

btw what does --split-per-abi --debug do

grim temple
#

debug turns rust's debug mode on (faster but bigger binaries)

#

split-per-abi is something android specific that i don't know either

rustic dagger
#

oke

grim temple
rustic dagger
#

Maybe since you are in Working-Group, you can ask on #archive-mobile

grim temple
#

you can ask too :D

rustic dagger
#

I cannot

#

I don't have access

#

I am not allowed to send messages

grim temple
#

ohoh somebody didn't read #rules 👀

#

(just kidding btw, but it's indeed mentioned there)

rustic dagger
#

Oke

#

That wasn't there when I first joined

#

I believe

#

But sure

grim temple
#

doesn't matter

rustic dagger
#

yeah

#

I should have disabled the build of tauri next branch as well...

rustic dagger
#

Hmmm is it correct that it takes more than 1 hour?

grim temple
#

nope

rustic dagger
#

But it is sort of doing things

grim temple
#

that's the timeout i was talking about

rustic dagger
#

it is showing the Compiling xxx thingys

rustic dagger
grim temple
#

different wording, used stuck instead of timeout

grim temple
rustic dagger
#

Oh... I didn't made that out of it

grim temple
#

while the build in tauri's main repo takes 20 minutes

#

and does not get stuck there

rustic dagger
#

Hmmmmm

grim temple
#

the --split-per-abi --debug stuff also didn't make a difference

rustic dagger
#

hmm, why is this sooo difficult...

grim temple
#

easy:

  1. tauri v2 is in early alpha, explicitly to figure out issues like this
  2. github actions are a pain to work with x)
blissful trout
#

did you guys try with verbose enabled?

#

Ludea also faced this

rustic dagger
#

But what would it fix?

#

It would only tell us what it is doing, right?

grim temple
#

well, we need to know what it's doing so that we can fix whatever is happening

rustic dagger
#

Uhmm, oh right...

#

But still, WHY did it work before I upgraded it so we could disabled the tauri next branch?

grim temple
#

same answer basically. that is what we're trying to figure out right now

rustic dagger
#

Oke sure

#

I will firstly disabled the build of the unused branch building thingy

#

And what do I need to add to enable verbose?

grim temple
#

add --verbose behind the --debug flag

rustic dagger
#

Oke

#

Oke it will now start building

#

Btw can you also look at how we could combine the action (of the apk build) into the Build App Action?

(as in what with: fields have to be chnaged so it will add the android build argument thingy)

grim temple
#

tauri-action can't handle tauri's v2 alpha yet so that should be impossible for now

rustic dagger
#

Oke

#

Uhmm after
Debug [tauri_mobile::bossy] setting stderr to Stdio { .. } on command "cargo build --package app --manifest-path /home/runner/work/Plan2Go/Plan2Go/src-tauri/Cargo.toml --target aarch64-linux-android --features custom-protocol --color always"

it doesn't show actual verbose info anymore (cause the compiling of cargo)

#

So I dont know if it is going to be usefull, but we will see

#

Oh wait it does the cargo per target

blissful trout
#

wait are you using the Node.js CLI?

#

or the Rust one

rustic dagger
#

I see a lot of file or directory '/home/runner/work/Plan2Go/Plan2Go/src-tauri/gen/android/app/app/src/*/*', not found (where * is replaced by text)

rustic dagger
#

Since the builded cargo one didn't work, it now runs: yarn tauri android build --split-per-abi --debug --verbose

blissful trout
#

nvm it's the rust one

#

ahh

grim temple
#

we tried both actually

blissful trout
#

ok 😦

grim temple
#

wait

#

no

rustic dagger
#
AAPT2 aapt2-7.3.1-8691043-linux Daemon #0: shutdown
BUILD SUCCESSFUL in 10m 9s
147 actionable tasks: 147 executed
Watching 1051 directories to track changes
Watching 1050 directories to track changes
Watching 1049 directories to track changes
Watching 1048 directories to track changes
grim temple
rustic dagger
#

this is where it is now stuck at

blissful trout
#

I know the currently published node CLI is a little weird at least

rustic dagger
rustic dagger
#

So what do you recommend?

#

But I will wait untill it hits 30 minutes (max)

rustic dagger
#

It is still 'building'

rustic dagger
#

So yeah, why does your work, and mine not

grim temple
#

wdym, mine is stuck in the same place

#

but i had 2 runs side by side

#

one with npm run tauri android build and one with cargo tauri android build

rustic dagger
#

Oh wait you used cargo tauri

grim temple
#

so it comes down to lucas' I know the currently published node CLI is a little weird at least kkushLUL

rustic dagger
#

But is there rn any way for it to work?

blissful trout
#

did it work with Cargo?

grim temple
#

for me yes

blissful trout
#

ok, I just need swift-rs to be released to publish tauri

rustic dagger
#

But is cargo tauri android build different from npm run tauri android build?

blissful trout
#

yeah, the npm one uses Node-API and it's a little weird with stdout/stderr so spawning some commands freeze the app (don't ask me why)

rustic dagger
#

Hmm I am now using cargo install tauri-cli --version "^2.0.0-alpha" && cargo tauri android build and it still is stuck after 1:40 hours

#

  No history is available.
Transforming savedstate-1.2.0.aar (androidx.savedstate:savedstate:1.2.0) with DexingNoClasspathTransform
Caching disabled for DexingNoClasspathTransform: /home/runner/.gradle/caches/transforms-3/46aa139b01fdf81b2b9389a46adcf412/transformed/savedstate-1.2.0-runtime.jar because:
  Build cache is disabled
DexingNoClasspathTransform: /home/runner/.gradle/caches/transforms-3/46aa139b01fdf81b2b9389a46adcf412/transformed/savedstate-1.2.0-runtime.jar is not up-to-date because:
  No history is available.
The input changes require a full rebuild for incremental DexingNoClasspathTransform: /home/runner/.gradle/caches/transforms-3/46aa139b01fdf81b2b9389a46adcf412/transformed/savedstate-1.2.0-runtime.jar.
grim temple
rustic dagger
#

Yes, thats why I tried

#

Oh wiat

#

it is my client/browser

#

it didnt update

#

the .zip is 439 MB

grim temple
#

probably because of the split abi stuff?

#

mine is 64.3

#

without the flag

rustic dagger
#

Btw there are some anotations:

Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions-rs/toolchain@v1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

rustic dagger
grim temple
rustic dagger
#

Sure

rustic dagger
#

Oke, btw where are my linux, windows, mac installables?

rustic dagger
#

I dont see them

grim temple
rustic dagger
#

v0.1.0 is old, it is November 14

grim temple
#

check the upload dates

rustic dagger
#

Oh, it updates the assets

rustic dagger
#

Btw I just see whilst I was copying my folder on my laptop, that the target folder is 9,76 GB

#

Shall I btw remove --debug from the android build command?

grim temple
grim temple
rustic dagger
#

Oke

rustic dagger
# grim temple that's a bit large. it should be something around 2GB for each target (2gb for d...

release = 2,23 GB
debug = 7,52 GB

debug folder:

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----          7-2-2023     11:41      482042778 Plan2Go.lib
-a----         10-2-2023     09:16      481982666 app.lib
-a----         10-2-2023     16:32      123179008 app.pdb
-a----          7-2-2023     11:41      482042778 deps\Plan2Go.lib
-a----         10-2-2023     09:16      481982666 deps\app.lib
-a----         5-12-2022     09:51      203813176 deps\libwindows-c3a28a5e1e0dc926.rlib
-a----        10-11-2022     19:18      188125966 deps\libwindows-539a3251dc00f06a.rlib
-a----         10-2-2023     16:32      123179008 deps\app.pdb
#

Maybe I should just run a 'clean' command, like at maven exists

grim temple
#

yeah, if your debug folder is older, and may have lived through some rust version updates it will grow over time

#

rust does not clean after itself

grim temple
rustic dagger
grim temple
#

but your app will be built from scratch on the next run as it removes everything

grim temple
rustic dagger
#

Oh

#

Hmmmm

#

Shall I do it?

grim temple
#

just delete it

rustic dagger
#

delete the target folder?

grim temple
#

yeah

#

or cargo clean

#

same thing

rustic dagger
#

and I guess just the debug folder inside

#

I will move it to trashbin

#

then now I will run the dev command

grim temple
rustic dagger
#

Yeah

#

Btw now that mobile build is sorted out, mayeb I shoudl somehow hook it up to the releases thingy

#

so you can download from there

#

And once we are done, I will put the full workflow file up to public for everyone, so anyone can use it