From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Cross-compiling gstoraster
Date: Tue, 4 Mar 2014 14:03:37 +0100 [thread overview]
Message-ID: <20140304130333.GA16356@omega> (raw)
In-Reply-To: <63F3A45AB9EA8943A92845E4748C0F4B010E551E@exchange-server.intranet.ggtg.net>
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
next prev parent reply other threads:[~2014-03-04 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 12:13 David Thomas
2014-03-04 13:03 ` Alexander Aring [this message]
2014-03-04 14:23 ` David Thomas
2014-03-05 8:54 ` Alexander Aring
2014-03-05 10:01 ` David Thomas
2014-03-05 15:17 ` David Thomas
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=20140304130333.GA16356@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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