From: Cary Lewis <cary.lewis@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: I am trying to build imagemagick with heic support
Date: Thu, 03 Oct 2019 20:57:00 -0000 [thread overview]
Message-ID: <CAEF1h+XgD76Nx6UBUi3_wxHHqYWyrDtXbTHDvEFUUcD19Xx6Xg@mail.gmail.com> (raw)
I downloaded libheif and when I configured it and built with the
--enable-shared option, it didn't build a .dll
The /usr/lib/libheif.la doesn't contain a library:
# libheif.la - a libtool library file
# Generated by libtool (GNU libtool) 2.4.6
#
# Please DO NOT delete this file!
# It is necessary for linking the library.
# The name that we can dlopen(3).
dlname=''
# Names of this library.
library_names=''
# The name of the static archive.
old_library='libheif.a'
# Linker flags that cannot go in dependency_libs.
inherited_linker_flags=''
# Libraries that this one depends upon.
dependency_libs=' /usr/lib/libde265.la -lpthread'
# Names of additional weak libraries provided by this library
weak_library_names=''
# Version information for libheif.
current=6
age=5
revision=0
# Is this an already installed library?
installed=yes
# Should we warn about portability when linking against -modules?
shouldnotlink=no
# Files to dlopen/dlpreopen
dlopen=''
dlpreopen=''
# Directory that this library needs to be installed in:
libdir='/usr/lib'
When imagemagick tries to link, I get this error:
*** Warning: This system cannot link to static lib archive /usr/lib/libheif.la.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
Has anyone successfully built ImageMagick with heic support on Cygwin?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2019-10-03 20:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEF1h+XgD76Nx6UBUi3_wxHHqYWyrDtXbTHDvEFUUcD19Xx6Xg@mail.gmail.com \
--to=cary.lewis@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).