new package: movit

[knyipab]

Following #20351, try to make a PR here to see if Actions of this repo can build movit package which is supposed to require on device build.

[TomJo2000]

Interesting, the builds are actually failing differently between x86 and Aarch64.

[TomJo2000]

Please do keep your commits squashed by the way.
You can use git rebase -i HEAD~2 to do so.
And you will probably want to commit subsequent revisions with git commit --amend to amend the HEAD commit.

See https://www.baeldung.com/ops/git-squash-commits#1-squash-the-last-x-commits for for info on interactive rebase.

[knyipab]

I rectified the build script following your review.

After all, the similarity in x86 and aarch64 build is that they both fail to run ./make_bundled_shaders to generate cpp file, error prompt is a bit different cuz x86 host tries to runs aarch64 binary.

I pause here and perhaps wait for someone who knows any around to cross-compile it. And also for fixing the symbol issue for arm if that's do-able.

[TomJo2000]

Regarding the missing symbols on arm.
Code search actually dug up an existing solution.

termux-packages/packages/marisa/build.sh

Lines 12 to 20 in 6cac06b

	termux_step_pre_configure() {
	# fix arm build and potentially other archs hidden bugs
	# ERROR: lib/libmarisa.so contains undefined symbols:
	# 39: 00000000 0 NOTYPE GLOBAL DEFAULT UND __aeabi_uidiv
	# 40: 00000000 0 NOTYPE GLOBAL DEFAULT UND __aeabi_idiv
	# 49: 00000000 0 NOTYPE GLOBAL DEFAULT UND __aeabi_idivmod
	LDFLAGS+=" $($CC -print-libgcc-file-name)"
	autoreconf -fi
	}

May need to be adjusted slightly, but LDFLAGS+=" $($CC -print-libgcc-file-name)" seems to be the operative part.

[knyipab]

Thanks a lot! The arm fix works as I updated in the TUR PR.

Still, I highly doubt if this package can be cross-compiled. More work may be needed to look into movit's build script.

[TomJo2000]

sorry about the delay on the CI runs, I need to approve them manually since this is a first time contribution

[TomJo2000]

huh just rewrite it in Python, that's of course also an option.
Nice thinking @licy183.

[knyipab]

thanks a lot @licy183

[TomJo2000]

I did also test building shortcut with movit from this PR and it built fine.

[knyipab]

Tested with shotcut (settings -> GPU effects (unstable)) on my device (Snapdragon 8 Gen 2)
The movit track editor is signjficantly slower than cpu mode except for zink in dri3 + generic vulkan loader.
The export outputting a overlay video does not work well (only the top video rendered).
I tried a number of GPU acceleration setups but don't find any useful.

Still, we may add this for mlt framework and shotcut, provided that it is an opt-in feature.