List for cgit developers and users
 help / color / mirror / Atom feed
Subject: Missing dependency
Date: Mon, 20 Jan 2014 10:07:38 -0500	[thread overview]
Message-ID: <CAG=jP7jXopJtHCppqWD=9AsDU0U0MvqmsLD3EyUZzZkmJyJ6eA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pwqBJ+RDP7axsPjWaTt2rhm=jkswf+DiKH_3EMq2X+vg@mail.gmail.com>

Jason,

I'm no Makefile expert, but a solution ? la CMake involves checking for the
library/header existence in common library/header location (/usr/...,
/usr/local/..., etc). If the library is found, we use it, otherwise, we
prompt a relevant error message. CMake has its own Find* mechanism; isn't
the autotools ./configure exactly for that purpose?

HTH,
-F


On Fri, Jan 17, 2014 at 5:36 PM, Jason A. Donenfeld <Jason at zx2c4.com> wrote:

> On Fri, Jan 17, 2014 at 8:08 PM, F?lix C. Morency
> <felix.morency at gmail.com> wrote:
> > You should add pkg-config to the list of dependencies in the README. It
> is
> > required if you want to build with Lua support. Also, it might be a good
> > idea to check for pkg-config presence in the Makefile.
>
> Thanks for the report; this is a good idea.
>
> Do you have any ideas on a fallback, for when pkg-config isn't
> available? I know for LUA_IMPLEMENTATION=VANILLA, we can probably just
> add a -llua to LIBS, but it's not as straight forward for
> LUA_IMPLEMENTATION=JIT. Any feedback would be most appreciated.
>
> Jason
>



-- 
F?lix C. Morency, M.Sc.
Plateforme d?analyse et de visualisation d?images
Centre Hospitalier Universitaire de Sherbrooke
Centre de recherche clinique ?tienne-Le Bel
Local Z5-3031 | 819.346.1110 ext 16634
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140120/426a119c/attachment.html>


      reply	other threads:[~2014-01-20 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 19:08 
2014-01-17 22:36 ` Jason
2014-01-20 15:07   `  [this message]

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='CAG=jP7jXopJtHCppqWD=9AsDU0U0MvqmsLD3EyUZzZkmJyJ6eA@mail.gmail.com' \
    --to=cgit@lists.zx2c4.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 NNTP newsgroup(s).