From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <av1474@comtv.ru>
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by yquem.inria.fr (Postfix) with ESMTP id 416D3BC57
	for <caml-list@yquem.inria.fr>; Sat, 12 Jun 2010 23:07:47 +0200 (CEST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvQFANKTE0xN6B+ka2dsb2JhbACfFw0ICwkzvXSFGgSDSA
X-IronPort-AV: E=Sophos;i="4.53,408,1272837600"; 
   d="scan'208";a="52264273"
Received: from fe01x03-cgp.akado.ru (HELO akado.ru) ([77.232.31.164])
  by mail3-smtp-sop.national.inria.fr with ESMTP; 12 Jun 2010 23:07:46 +0200
Received: from [10.0.66.9] ([10.0.66.9] verified)
  by fe01-cgp.akado.ru (CommuniGate Pro SMTP 5.2.13)
  with ESMTPS id 191534695; Sun, 13 Jun 2010 01:07:45 +0400
Date: Sun, 13 Jun 2010 01:07:39 +0400 (MSD)
From: malc <av1474@comtv.ru>
X-X-Sender: malc@linmac
To: bluestorm <bluestorm.dylc@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [ANNOUNCE] llpp
In-Reply-To: <AANLkTikvlrBe-RWdTJ5BnxZPRbFDTgpf9WREpoa_Ro8h@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1006130106300.11997@linmac>
References: <alpine.LNX.2.00.1006122233180.11439@linmac> <4C13F2F1.9070508@gmail.com>  <alpine.LNX.2.00.1006130053120.11824@linmac> <AANLkTikvlrBe-RWdTJ5BnxZPRbFDTgpf9WREpoa_Ro8h@mail.gmail.com>
User-Agent: Alpine 2.00 (LNX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam: no; 0.00; malc:01 malc:01 usr:01 wrote:01 compile:01 typing:01 caml-list:01 minor:01 match:02 suggestion:03 tend:03 problem:05 install:05 standard:07 path:07 

On Sat, 12 Jun 2010, bluestorm wrote:

> 2010/6/12 malc <av1474@comtv.ru>
> 
> > > Two minor issues:
> > > 1. The mupdf from sumatrapdf installs fitz.h and mupdf.h directly into
> > > /usr/local/include, and not under fitz/, or mupdf/, so llpp failed to
> > > compile. I fixed by copying the headers to where llpp expected them to
> > be.
> >
> > I was a nanometer away from typing: please edit build.sh to match your
> > mupdf installation(or lack there of) into BUILDING, but then didn't,
> > sigh...
> 
> 
> I had the same problem and had to change link.c, not build.sh. It would be
> nicer if the harcoded header path were not "fitz/fitz.h" and "mupdf/mupdf.h"
> but "fitz.h" and "mupdf.h". You would have to add the corresponding
> "$mupdflibpath/fitz/" and "$mupdflibpath/mupdf" in your build.sh, but
> standard mupdf installation would work out of the box.

Thanks for suggestion, it's just that i tend to not install things instead
just letting the linger in their build environments, i'll try to integrate
this idea though, thanks once again. 

-- 
mailto:av1474@comtv.ru