tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

libjpeg-turbo coexistence?

Home Assistant uses

which has hardcoded search paths per OS, obviously not great, but easy
to add NetBSD.

I know one can use libjpeg-turbo as an option in pkgsrc, and I do that
on some systems.  I see in the destdir:

-rw-r--r--  1 gdt  users  826308 Dec 31 13:34 libjpeg.a
lrwxr-xr-x  1 gdt  users      12 Dec 31 13:35 ->
lrwxr-xr-x  1 gdt  users      16 Dec 31 13:35 ->
-rwxr-xr-x  1 gdt  users  674368 Dec 31 13:33
-rw-r--r--  1 gdt  users  960882 Dec 31 13:31 libturbojpeg.a
lrwxr-xr-x  1 gdt  users      17 Dec 31 13:35 ->
lrwxr-xr-x  1 gdt  users      21 Dec 31 13:35 ->
-rwxr-xr-x  1 gdt  users  754440 Dec 31 13:29

However, I wonder if there should be a way to build libjpeg-turbo as two

  one, that builds libturbojpeg, so that programs that want that API can
  use it, separately from the turbo/not choice

  one that replaces libjpeg

I wonder if it's still the case that turbo-provided jpeg is .so.8 vs
.so.9; it seems like a bug for that to persist.

I also wonder if we should be making jpegturbo the default, or if there
are good reasons not to.

Attachment: signature.asc
Description: PGP signature

Home | Main Index | Thread Index | Old Index