ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] Gutenprint 5.2.8 with LTIB


From: Andy Yew
Subject: Re: [Ltib] Gutenprint 5.2.8 with LTIB
Date: Wed, 25 Jan 2012 21:57:13 +0800

Dear Mike,

Thanks for the simple (beginner forgiving) explanation and also the ijsgutenprint example.

As this makefile (ijsgutenprint) looks similar to some spec file language, i also think the spec file method you've suggested might work. Due to lack of experience, i'd like to ask for another help from you: Could you "roughly" write a "possible" spec file content for my case here (Gutenprint and extract-strings)?? For build, configure/compile, & install parts....

After this draft is got, i'll test it out here....

Thanks in advance!!
Andy

On Wed, Jan 25, 2012 at 8:10 PM, Mike Goins <address@hidden> wrote:
On Wed, Jan 25, 2012 at 6:50 AM, Mike Goins
<address@hidden> wrote:
> On Sun, Jan 22, 2012 at 1:05 PM, Andy Yew <address@hidden> wrote:
>> Hi all,
>>
>> Has anyone successfully build/LTIB Gutenprint?
>
>
> Gutenprint is one of those that are not cross-compile friendly (after
> taking a brief look at it).   It requires running a just built
> "extract-strings" on the host, but it does not appear differentiate
> between "build" and "host".  There are a couple options to get around
> this.

Here is another method used to cross-compile the package:
http://pits.googlecode.com/svn-history/r5/trunk/ijsgutenprint/Makefile

It builds libijs and extract-strings outside the source tree.  A
wrapper script file called extract-strings in created in the expected
location that references the host binary (which satisfies the rule to
build it).

It is very possible to do this entirely within the spec file.

<snipped for brevity since replying to own message, apologies>

_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/ltib


reply via email to

[Prev in Thread] Current Thread [Next in Thread]