-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[question] Any hints on how to cross-compile for rpi4 #275
Comments
Did you try this on rpi4 ? |
Hi, |
The same as usual. If there is any error that stops the configure or build process, just let me know. $ sh autogen.sh |
I tried several months ago, can't remember clearly the error. Currently backing up the rpi and I get back to you. |
There it is, at the ./configure step and I don't know what to do here :
|
Okay, I added the definitions for aarch64 architecture. You can try again ( and we take the next problem ) |
Just the same output from a fresh clone I'm afraid :
|
Updated the rule to match against aarch64* , that should do it. |
Fresh clone and same output.
|
Updated the configure script to output a more informative error, can you try again ? It will still fail. |
About the same
|
Did you run autogen.sh ? The error I was expecting here is 'unknown arch' instead of 'unknown' |
Output from autogen.sh :
And as expected, ./configure output is the same. |
Just to make sure, do I need any extra deps on rpi or not ? |
No, no extra deps are needed. I pushed changes to all configure.ac scripts now |
Well, autoconf and configure went fine.
|
Okay, I changed the configure.ac scripts and removed the -mthumb -mthumb-interwork for this architecture. |
Also, please share the output of $ cat /proc/cpuinfo to see what optimizations can be enabled to speed up operations like memcpy, subsample, supersample, convert etc |
My lunch break is ending, more to come later. : ) |
From a fresh clone |
Can you send the config.h file that is created after running ./configure ? Updates have been pushed to veejay-core configure.ac script |
huge output when building veejay-core :
Sorry for so much French |
Yes, the first error that happens will be the most useful. You can redirect stderr to a file, this leaves just the errors. However, most likely your platform can't support the assembly included by new_arm.S and it needs to be excluded from the build when your platform is targeted. |
Can you run the following C program ?
$ gcc -march=armv8-a+crc -mfpu=neon -o test test.c && ./test $ gcc -march=native -o test test.c && ./test $ gcc -march=armv8-a+crc -o test test.c && ./test This will test for a SIMD NEON instruction. One of the gcc commands should compile and run with exit code 0 |
Please try building veejay-core from https://github.com/game-stop/veejay/tree/arm8 and send me the output from configure & make |
errors while building veejay-core : |
I might be misunderstanding what you asked, I'll just skip to try to build the new veejay-core for now. |
And the errors from when running make for the custom veejay-core : But diff tells me these two outputs are the same. One question here, ./configure says the following at the end :
Am I supposed to install one or more of the packages listed below ?
|
However, I can manage an ssh access for you if you believe it does help. |
That would be much appreciated, saves me a lot of time |
Your system does not have NEON support as I understand it
…On Wed, Sep 6, 2023 at 6:08 PM gui-lux ***@***.***> wrote:
And the errors from when running make for the custom veejay-core :
makevjcorecustom.txt
<https://github.com/game-stop/veejay/files/12539977/makevjcorecustom.txt>
But diff tells me these two outputs are the same.
One question here, ./configure says the following at the end :
configure:
configure: Veejay-Core 1.5.65 build configuration :
configure:
configure: Compiler flags: -march=armv8-a+crc -march=native -ftree-vectorize -O3 -fno-stack-protector -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -Wall -Wunused -fno-stack-protector
configure: architecture: auto
configure:
configure: Architecture: aarch64
configure:
configure: arm
configure: NEON enabled : no
configure:
configure: Platform: Linux
configure:
configure: Required dependencies:
configure: - POSIX Threads (pthread) : true
configure: - FFmpeg/AV AVFormat : true
configure: - FFmpeg/AV AVCodec : true
configure: - FFmpeg/AV Swscaler : true
configure: - FFmpeg/AV AVUtil : true
Am I supposed to install one or more of the packages listed below ?
***@***.***:~/compilation/vjc/veejay/veejay-current/veejay-core$ apt-cache search neon
libne10-10 - ARM neon (SIMD) library
libne10-dev - ARM neon (SIMD) library - development files
libneon27 - HTTP and WebDAV client library
libneon27-dbg - Detached symbols for libneon27
libneon27-dev - Header and static library files for libneon27
libneon27-gnutls - HTTP and WebDAV client library (GnuTLS enabled)
libneon27-gnutls-dbg - Detached symbols for libneon27 (GnuTLS enabled)
libneon27-gnutls-dev - Header and static library files for libneon27 (GnuTLS enabled)
librust-packed-simd-dev - Portable Packed SIMD vectors - Rust source code
—
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3467DFEKSTQAEQDZJEW33XZCNYZANCNFSM6AAAAAAXH5GIEU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Those 4 lines of C code need to be put in test.c , but once I have shell
access I can sort it out what exactly your CPU supports and what not. Maybe
it has NEON after all, the error message is just saying it cannot find the
source file.
…On Wed, Sep 6, 2023 at 5:53 PM gui-lux ***@***.***> wrote:
***@***.***:~/test$ gcc -march=armv8-a+crc -mfpu=neon -o test test.c && ./test
gcc: error: test.c: Aucun fichier ou dossier de ce type
gcc: error: unrecognized command-line option ‘-mfpu=neon’
gcc: fatal error: no input files
compilation terminated.
***@***.***:~/test$ gcc -march=native -o test test.c && ./test
gcc: error: test.c: Aucun fichier ou dossier de ce type
gcc: fatal error: no input files
compilation terminated.
***@***.***:~/test$ gcc -march=armv8-a+crc -o test test.c && ./test
gcc: error: test.c: Aucun fichier ou dossier de ce type
gcc: fatal error: no input files
compilation terminated.
I might be misunderstanding what you asked, I'll just skip to try to build
the new veejay-core for now.
—
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3467ASY2O3FCVMTISGT7LXZCMBFANCNFSM6AAAAAAXH5GIEU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I started work in another branch
$ git clone ....
$ git checkout arm8
…On Wed, Sep 6, 2023 at 5:46 PM gui-lux ***@***.***> wrote:
errors while building veejay-core :
make.txt <https://github.com/game-stop/veejay/files/12539836/make.txt>
—
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3467CPWJKDSO3FAMSL7LDXZCLFVANCNFSM6AAAAAAXH5GIEU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
May I write an email to the address found in veejay's banner ? |
Yes, either [email protected] or [email protected] will be fine |
Email sent, please check spam folder as I'm not standard GAFAM domain. |
So, my rpi has burnt in flames while building veejay... Sorry, this is my Friday's poorest joke ! Everything went fine - core, server, client, utils. \o/ Currently watching veejay running loaded with a bunch of avi/mjpeg 640x480 25fps samples + mixing FX, veejay eats roughly 120% of CPU, reloaded about 40%, temperature raising but fine. I need a better cooling system anyway. About the FX, yes, some of them produce unexpected result : chroma based, LVD, produces vertical green lines. Frei0r plugins from source produce vertical green lines and basically run between 10 and 15 fps. I'll see how it behaves with v4l2, http/mp4 streams and midi controller but I guess these features will be fine. I have an HDMI touchscreen plugged to the rpi, but it's only left-click capable so not really useful with reloaded. Anyway, this is really great, holidays well deserved ! |
Hey again
Thanks for the feedback, I have an idea what to look for but the fixes
could take a few attempts. Is it possible for you to setup a graphical
interface or to allow me to connect on port 3490 to get a picture remotely?
See you
…On Fri, 8 Sept 2023, 21:29 gui-lux, ***@***.***> wrote:
So, my rpi has burnt in flames while building veejay...
Sorry, this is my Friday's poorest joke ! Everything went fine - core,
server, client, utils. \o/
Currently watching veejay running loaded with a bunch of avi/mjpeg 640x480
25fps samples + mixing FX, veejay eats roughly 120% of CPU, reloaded about
40%, temperature raising but fine. I need a better cooling system anyway.
About the FX, yes, some of them produce unexpected result :
all overlay type, effectv type produce vertical green lines.
magic tracer produces big horizontal snow lines.
luma based run fine.
chroma based, LVD, produces vertical green lines.
Frei0r plugins from source produce vertical green lines and basically run
between 10 and 15 fps.
I'll see how it behaves with v4l2, http/mp4 streams and midi controller
but I guess these features will be fine.
No crash observed so far.
I have an HDMI touchscreen plugged to the rpi, but it's only left-click
capable so not really useful with reloaded.
Anyway, this is really great, holidays well deserved !
—
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3467GUYBX5KMR6UXTJO3DXZNW2XANCNFSM6AAAAAAXH5GIEU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sure, do you have wireguard ? |
Or wait, you should be able to connect through ssh, with -L argument and localport:host:remoteport format. |
Alright, I'll try that .. sometime during the holiday 😂
…On Fri, Sep 8, 2023 at 11:31 PM gui-lux ***@***.***> wrote:
Or wait, you should be able to connect through ssh, with -L argument and
localport:host:remoteport format.
—
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3467AUFFCWN3I6BCOIQRLXZOFBNANCNFSM6AAAAAAXH5GIEU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
avi/mjpeg 640x480 25fps
For ARM / pi based system, mjpeg is quite wasteful . Maybe, by increasing
bandwidth you can free up cpu resources, with lzo yuv or raw yuv or simply
reduce resolution instead
I reverted the changes to libsubsample, to see if this is where the
routines fail
It's currently building
Can you try Normal Overlay and Soft Blur at your next opportunity ?
…On Fri, Sep 8, 2023 at 9:29 PM gui-lux ***@***.***> wrote:
So, my rpi has burnt in flames while building veejay...
Sorry, this is my Friday's poorest joke ! Everything went fine - core,
server, client, utils. \o/
Currently watching veejay running loaded with a bunch of avi/mjpeg 640x480
25fps samples + mixing FX, veejay eats roughly 120% of CPU, reloaded about
40%, temperature raising but fine. I need a better cooling system anyway.
About the FX, yes, some of them produce unexpected result :
all overlay type, effectv type produce vertical green lines.
magic tracer produces big horizontal snow lines.
luma based run fine.
chroma based, LVD, produces vertical green lines.
Frei0r plugins from source produce vertical green lines and basically run
between 10 and 15 fps.
I'll see how it behaves with v4l2, http/mp4 streams and midi controller
but I guess these features will be fine.
No crash observed so far.
I have an HDMI touchscreen plugged to the rpi, but it's only left-click
capable so not really useful with reloaded.
Anyway, this is really great, holidays well deserved !
—
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3467GUYBX5KMR6UXTJO3DXZNW2XANCNFSM6AAAAAAXH5GIEU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
But to forward what, I tried but I think I didn't really understood
what you meant
…On Fri, Sep 8, 2023 at 11:31 PM gui-lux ***@***.***> wrote:
Or wait, you should be able to connect through ssh, with -L argument and localport:host:remoteport format.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Hi Niels, just rebuilt with latest fixes. About this ssh trick, you should be able to connect a local reloaded to the remote veejay. |
I left a server running in case you're around. |
Both work well. |
Not an expert at video processing here, and not familiar with lzo. From my knowledge, lzo is used in many cases but never knew that could be used with live video processing. EDIT : Question is more like : how do I create video samples in a more veejay-compliant format ? And did you have enough of the wonderful 'Comté' and the pretty unique 'Vin Jaune' ? |
Hi,
just curious, I'd love to see how veejay is running on rpi.
I don't even know if it's possible and not sure at all how I would proceed.
From my non-existent knowledge into this, I understand I need to install gcc-10-arm-linux-gnueabihf or something similar, install all dependencies on the rpi4 and that's all I know.
I'm running debian on an x86_64 host and my rpi4 runs diet-pi, a nice debian derivative.
Many thanks if you have ideas !
The text was updated successfully, but these errors were encountered: