Could the bundle (to the current directory) be auto-detected if the bundle path isn't provided?
ie, instead of always requiring the bundle to run the app:
$ ./build/elinux/x64/release/bundle/elinux_test --bundle=${PWD}/build/elinux/x64/release/bundle
allow for:
$ ./build/elinux/x64/release/bundle/elinux_test
I'm having trouble understanding the intended use of the 2 different executable files:
├── bundle
│ ├── data
│ ├── elinux_test // The end-result executable mentioned in the documentation?
│ └── lib
├── <other_things_required_for_the_build>
└── runner
├── <other_files>
├── elinux_test // Intermediary executable required by the embedder?
It would be great to understand the purpose of the runner one 🙂
Looking at the documentation, the desired output executable lives inside the bundle : https://github.com/sony/flutter-elinux/wiki/Running-flutter-apps#run-without-the-flutter-elinux-command
Could the bundle (to the current directory) be auto-detected if the bundle path isn't provided?
ie, instead of always requiring the bundle to run the app:
allow for:
I'm having trouble understanding the intended use of the 2 different executable files:
It would be great to understand the purpose of the
runnerone 🙂Looking at the documentation, the desired output executable lives inside the
bundle: https://github.com/sony/flutter-elinux/wiki/Running-flutter-apps#run-without-the-flutter-elinux-command