Package Details: lib32-libdovi 3.3.1-1

Git Clone URL: https://aur.archlinux.org/lib32-libdovi.git (read-only, click to copy)
Package Base: lib32-libdovi
Description: Library to read and write Dolby Vision metadata C-API (32-bit)
Upstream URL: https://github.com/quietvoid/dovi_tool/tree/main/dolby_vision
Licenses: MIT
Provides: libdovi.so
Submitter: quietvoid
Maintainer: quietvoid
Last Packager: quietvoid
Votes: 0
Popularity: 0.000000
First Submitted: 2023-05-27 11:59 (UTC)
Last Updated: 2024-08-04 13:36 (UTC)

Latest Comments

1 2 Next › Last »

quietvoid commented on 2025-01-18 14:55 (UTC) (edited on 2025-01-18 14:58 (UTC) by quietvoid)

seems not need ship the includes in the own include directory.

Can you clarify what you think the problem is?

It's installed to libdovi32 to avoid conflicting with extra/libdovi.
I couldn't find guidelines on whether it should be kept or not.

However I haven't tried depending on the native lib here.

sl1pkn07 commented on 2025-01-18 14:26 (UTC) (edited on 2025-01-18 14:27 (UTC) by sl1pkn07)

seems not need ship the includes in the own include directory. is the same file. only changes the 3 last lines and not affect anyting

└───╼  git diff libdovi32/rpu_parser.h libdovi/rpu_parser.h 
diff --git a/libdovi32/rpu_parser.h b/libdovi/rpu_parser.h
index 690f9ca..69c95fd 100644
--- a/libdovi32/rpu_parser.h
+++ b/libdovi/rpu_parser.h
@@ -741,7 +741,7 @@ const DoviData *dovi_write_av1_rpu_metadata_obu_t35_payload(DoviRpuOpaque *ptr);
 const DoviData *dovi_write_av1_rpu_metadata_obu_t35_complete(DoviRpuOpaque *ptr);

 #ifdef __cplusplus
-}  // extern "C"
-#endif  // __cplusplus
+} // extern "C"
+#endif // __cplusplus

-#endif  /* DOVI_H */
+#endif /* DOVI_H */

you can just drop it

greetings

exuvo commented on 2024-06-14 22:25 (UTC)

Well im not gonna delve into rust's weird specifics just for a 5 steps below dependency, ill just wait.

quietvoid commented on 2024-06-14 22:23 (UTC)

Rust toolchain management is recommended to be done using rustup rather than the Arch rust package.

exuvo commented on 2024-06-14 22:21 (UTC)

According to https://github.com/tuffy/bitstream-io/issues/20 the required rust version was released yesterday. And it does not seem to have trickled down to my pacman -Syu yet. Kinda a shit move by the guy to require it so soon. Guess ill wait a few days then.

quietvoid commented on 2024-06-14 22:18 (UTC)

You need to update your Rust toolchain.
Unfortunately this means the MSRV for the lib needs to be bumped. There's no lockfile so I'll try to do it shortly.

exuvo commented on 2024-06-14 20:57 (UTC)

Does not build for me, when compiling bitstream-io v2.4.0 (new since a few hours ago?) it fails with a few "error[E0658]: inline-const is experimental"

quietvoid commented on 2024-04-12 13:28 (UTC)

As intended. The package can't have side effects so you need to setup the toolchain.

silentnoodle commented on 2024-04-12 13:13 (UTC)

FYI, had to run rustup target add i686-unknown-linux-gnu for this to build

oxalin commented on 2024-03-02 17:29 (UTC)

Most of the time, what I've seen is to have a dependency on the native package. This way, the header files are installed for both packages.

libtiff and lib32-libtiff seem bad examples. libtiff drops all its header files under /usr/include without using any subdirectory, which could be conflicting with other header files of the same names.

lib32-libtiff already has a dependency on libtiff, so the header files are redundant. At least, they are into their own subfolder.

But thank you for moving the files under their own subdirectory so they won't conflict with the native package.

1 2 Next › Last »