Request for 32-bit ARM/Linux build of libdmd_reader_api.so

[xiongjz]

Hello,

I am developing a C++ data analysis tool that uses the DMD Reader API, and I need to deploy it on an embedded Linux system with a 32-bit ARM architecture.

I have reviewed the official dmd_reader_api_load.h header, which shows that the API supports both 64-bit (libdmd_reader_api_x64.so) and 32-bit (libdmd_reader_api.so) builds for Linux. The existence of the 32-bit variant is clear from the source.

However, I was unable to find a pre-compiled 32-bit binary (ARM/Linux) in the public repositories or within the pyDmdReader package. Could you please provide this file, or let me know the appropriate channel to obtain it?

I would be happy to provide additional details about my target platform if needed.

Thank you for your time and for maintaining this project.

Best regards,
xjz
3227998308@qq.com

[glaure]

Hi, I am afraid we do not have an libdmd_reader_api_x64.so or libdmd_reader_api.so for Linux. The references you found in the header file are more wishful thinking… I hope you can work around this limitation. Best regards, Gunther [cid:dewetron-logo_email-signature-150_ce539afa-b6be-4be4-9497-7b265fb4b6e5.png]<https://www.dewetron.com/> Gunther Laure | Team Leader Software Development ***@***.*** | www.dewetron.com<https://www.dewetron.com> +433163070284 DEWETRON GmbH, Parkring 4, 8074 Grambach, AUSTRIA <https://www.facebook.com/MyCompany>[cid:linkedin_a56b72d3-e383-4d44-be3b-70b0c715225d.png]<https://www.linkedin.com/company/dewetron/> [cid:youtube_880b6f0d-8a12-4051-a2ea-c74b7beafd50.png] <https://www.youtube.com/channel/UCE76NeVVgWF65etH8E1bOog> [cid:facebook_79c45449-903c-4ec0-b195-ff7161baa5ad.png] <https://www.facebook.com/dewetron.gmbh> [cid:instagram_3fe69145-c3ef-4d06-9c69-a7d5c15df8c5.png] <https://www.instagram.com/wearedewetron/> [cid:github_281fdf2e-da25-44d8-99d8-3c2dea93a9ea.png] <https://github.com/DEWETRON> [cid:oxygen-8-with-oxygen-go-mail_4aedfff1-effd-41f4-aa26-7e540b757bbb.png]<https://www.dewetron.com/products/software/oxygen-go-app/> [cid:download-on-the-app-store_a43c2afd-14e1-48e1-865b-b498da4b9328.png]<https://apps.apple.com/at/app/oxygen-go/id6756105868> <https://www.apple.com/at/app-store/>[cid:get-it-on-google-play_9ba09b3f-42e1-4929-854b-01d50fdd029c.png]<https://play.google.com/store/apps/details?id=com.dewetron.oxygengo&hl=de_AT> Von: xiongjz ***@***.***> Gesendet: Mittwoch, 6. Mai 2026 11:54 An: DEWETRON/pyDmdReader ***@***.***> Cc: Subscribed ***@***.***> Betreff: [DEWETRON/pyDmdReader] Request for 32-bit ARM/Linux build of libdmd_reader_api.so (Issue #24) This email originated outside of DEWETRON. DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe. [https://avatars.githubusercontent.com/u/100347638?s=20&v=4]xiongjz created an issue (DEWETRON/pyDmdReader#24)<#24> Hello, I am developing a C++ data analysis tool that uses the DMD Reader API, and I need to deploy it on an embedded Linux system with a 32-bit ARM architecture. I have reviewed the official dmd_reader_api_load.h header, which shows that the API supports both 64-bit (libdmd_reader_api_x64.so) and 32-bit (libdmd_reader_api.so) builds for Linux. The existence of the 32-bit variant is clear from the source. However, I was unable to find a pre-compiled 32-bit binary (ARM/Linux) in the public repositories or within the pyDmdReader package. Could you please provide this file, or let me know the appropriate channel to obtain it? I would be happy to provide additional details about my target platform if needed. Thank you for your time and for maintaining this project. Best regards, xjz ***@***.******@***.***> — Reply to this email directly, view it on GitHub<#24>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACUGAHXYD2NVTYPAHS4FSLT4ZMDR3AVCNFSM6AAAAACYS2VJC6VHI2DSMVQWIX3LMV43ASLTON2WKOZUGM4TAMZZGM3DIOI>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[xiongjz]

Thank you for your honest clarification regarding the missing Linux version of libdmd_reader_api.

I have actually managed to obtain a 64‑bit version of libdmd_reader_api.so (and it works on x86_64 Linux). However, my target system is a 32‑bit embedded Linux platform (ARMv7 / armhf). The 64‑bit library cannot be loaded there due to ELF class mismatch.

We are currently working on a 32‑bit embedded Linux system (ARMv7 / armhf) and would like to ask if there is any way to read DMD files on this platform.

Specifically:

Do you have a 32‑bit version of the DMD reader library (shared object) for Linux?

If not, is a static library (.a) available for 32‑bit ARM Linux?

Any guidance or workaround would be greatly appreciated.

[glaure]

I am looking into it. But this is not trivial.
DMD Reader has a lot of dependencies ...

ldd build/Release/libdmd_reader_api_x64.so
linux-vdso.so.1 (0x000071e1232a8000)
libboost_log_setup.so.1.90.0 => /usr/lib/x86_64-linux-gnu/libboost_log_setup.so.1.90.0 (0x000071e12319e000)
libboost_log.so.1.90.0 => /usr/lib/x86_64-linux-gnu/libboost_log.so.1.90.0 (0x000071e1230ea000)
libboost_filesystem.so.1.90.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.90.0 (0x000071e1227d8000)
libboost_locale.so.1.90.0 => /usr/lib/x86_64-linux-gnu/libboost_locale.so.1.90.0 (0x000071e122733000)
libboost_thread.so.1.90.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.90.0 (0x000071e122715000)
libboost_chrono.so.1.90.0 => /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.90.0 (0x000071e12270c000)
libcap.so.2 => /usr/lib/x86_64-linux-gnu/libcap.so.2 (0x000071e1226ff000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x000071e122400000)
libm.so.6 => /usr/lib/x86_64-linux-gnu/libm.so.6 (0x000071e1222da000)
libgcc_s.so.1 => /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 (0x000071e1226d1000)
libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x000071e122000000)
/lib64/ld-linux-x86-64.so.2 (0x000071e1232aa000)
libicui18n.so.78 => /usr/lib/x86_64-linux-gnu/libicui18n.so.78 (0x000071e121c00000)
libicuuc.so.78 => /usr/lib/x86_64-linux-gnu/libicuuc.so.78 (0x000071e121800000)
libicudata.so.78 => /usr/lib/x86_64-linux-gnu/libicudata.so.78 (0x000071e11f800000)

Which distribution do you run on your armhf 32bit device?

There are parts that are using AVX and other assembler instructions. That will have to be ported to ARM.
As I said, this task is not trivial.

Best regards
Gunther

[glaure]

I used Ubuntu 24.04 and its ARM cross toolchain (armhf).

Please test this library:
https://cloud.dewetron.com/s/zW9N3kYBkR78GkS

It will have a lot of dependencies you have to fullfill from the Ubuntu 24.04 repository.

Bye Gunther

[xiongjz]

Thank you very much for your detailed explanation and for sharing the library.

I fully understand that this is not a trivial task, especially with the AVX dependencies and the need to port parts to ARM. I really appreciate the effort you’ve put into this.

I will test the library on my armhf 32-bit device (running Ubuntu 24.04, as you suggested) right away and let you know the results.

Thanks again for your support.

Best regards,
xjz

[xiongjz]

I have tested the library on my armhf device. Unfortunately, I am still facing compatibility issues due to differences between the Ubuntu version on my embedded system and the one you used.

I fully understand that this is a non‑trivial task, and I do not want to take up more of your time. However, if you are interested and have the capacity, I could provide you with my cross‑compilation toolchain (or the exact build environment) so that you might be able to produce a version that matches my target system. If that is not something you wish to pursue, I completely understand – your help so far has already been very valuable.

Thank you very much for your time, patience, and for providing the test library. I really appreciate the effort you put into this, especially given the complexity of porting AVX‑dependent code to ARM.

Best regards,
xjz