From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from mail-ea0-x233.google.com ([2a00:1450:4013:c01::233])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <alex.aring@gmail.com>) id 1WKp0g-0005l8-5M
	for ptxdist@pengutronix.de; Tue, 04 Mar 2014 14:03:50 +0100
Received: by mail-ea0-f179.google.com with SMTP id q10so337943ead.24
	for <ptxdist@pengutronix.de>; Tue, 04 Mar 2014 05:03:44 -0800 (PST)
Received: from omega (p20030064AA051101E2CB4EFFFE1BB546.dip0.t-ipconnect.de.
	[2003:64:aa05:1101:e2cb:4eff:fe1b:b546])
	by mx.google.com with ESMTPSA id x6sm63194924eew.20.2014.03.04.05.03.42
	for <ptxdist@pengutronix.de>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Tue, 04 Mar 2014 05:03:43 -0800 (PST)
Date: Tue, 4 Mar 2014 14:03:37 +0100
From: Alexander Aring <alex.aring@gmail.com>
Message-ID: <20140304130333.GA16356@omega>
References: <63F3A45AB9EA8943A92845E4748C0F4B010E551E@exchange-server.intranet.ggtg.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <63F3A45AB9EA8943A92845E4748C0F4B010E551E@exchange-server.intranet.ggtg.net>
Subject: Re: [ptxdist] Cross-compiling gstoraster
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de

Hi,

On Tue, Mar 04, 2014 at 12:13:24PM +0000, David Thomas wrote:
> Hello,
> 
> I have got further now. I saw that the path was wrong for installation of libraries. I have fixed that so please disregard my previous question.
> 
> My libcups.so library is now installed to the following directories:
> 
> platform-phyCORE-AM335x/root/usr/lib
> platform-phyCORE-AM335x/root-debug/usr/lib
> platform-phyCORE-AM335x/sysroot-target/usr/lib
> 
> My raster.h header file is installed to these:
> 
> platform-phyCORE-AM335x/root/usr/include/cups
> platform-phyCORE-AM335x/root-debug/usr/include/cups
> platform-phyCORE-AM335x/sysroot-target/usr/include/cups
> 

Normally you should not have any non runtime files like header files on
you target root. This is only needed at compile time.

> Ghostscript's configure still fails to pick it up:
> 
> checking cups/raster.h usability... no
> checking cups/raster.h presence... no
> checking for cups/raster.h... no
> 
> It must therefore be looking somewhere else for the files.
> 
> Questions are:
> 
> 1. Where is it looking? (I suppose this is the --sysroot used by gcc and the binutils.)
> 2. What would a typical macro look like to install a library there?
> 
Difficult to say if we don't know what you doing in the rule files,
please send it as RFC to this list and I can check it. Please use
"git send-email" for that and we need all rule files including
dependencies, maybe we can get these rules mainline then.

I see in ghostscript configure some options like:

--enable-cups
--with-pdftoraster

do you acitvated that in the rule file of ghostscript?

- Alex

-- 
ptxdist mailing list
ptxdist@pengutronix.de