On Wed, Jan 25, 2012 at 1:29 PM, Andy Yew <[email protected]> wrote: > Dear Mike, > > It WORKS!
Great. > I simply copy&paste the spec file you've simply made to replace my previous > gutenprint.spec and scbuild it, it ended up with the beautifully build > success time: 236 seconds! This has been a long awaiting result and it > finally appear.... > > I've scinstall and scdeploy and the corresponding binary/libraries/modules > "properly" appears in the folders they shud show up, such as rootfs/usr/bin, > rootfs/usr/include etc. > > A big thanks for your help and could you email me your paypal email address > so that i could pay you a lunch or some beers?? Last request from me for > this topic... Aw thanks, but instead of me, please offer it to the list maintainer (Stuart). Most of what I learned was from him through this list. > Andy > > > On Thu, Jan 26, 2012 at 12:40 AM, Mike Goins <[email protected]> > wrote: >> >> On Wed, Jan 25, 2012 at 8:57 AM, Andy Yew <[email protected]> wrote: >> > 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.... >> >> I took the spec file and modified (more like hacked) it to get a host >> extract-strings. You may need work with it some more for the flags >> you want. >> >> Builds host version (as static so I don't have to manipulate libs). >> Copies extract-strings to a hostbin folder and replaces it with a >> wrapper script. >> Cleans >> Runs configure again for the build. >> Removes the extract-strings dependency for generating the header file. >> Builds. >> >> It's not very robust (and certainly not upstream worthy), but does get >> through that one stage. Warning, when the cross build runs, it blows >> away the wrapper script, but just right after that script is run. Any >> shift in the dependencies is likely to break the hack. My build did >> not complete since I am using a really old homegrown tool-chain, but I >> expect like the codesourcery tools will not have the issue I did (well >> after the extract-strings handling). >> >> I did not go into the install/deploy, but I do not expect any issues >> with those sections. You can test that out. >> >> Also, the version I found was suffixed with "-pre1", so adjust the >> spec file appropriately. >> >> >> > Thanks in advance!! >> > Andy >> >> Caught me in a good mood. >> >> >> > On Wed, Jan 25, 2012 at 8:10 PM, Mike Goins >> > <[email protected]> >> > wrote: >> >> >> >> On Wed, Jan 25, 2012 at 6:50 AM, Mike Goins >> >> <[email protected]> wrote: >> >> > On Sun, Jan 22, 2012 at 1:05 PM, Andy Yew <[email protected]> >> >> > 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 >> >> [email protected] >> >> https://lists.nongnu.org/mailman/listinfo/ltib >> > >> > >> >> _______________________________________________ >> LTIB home page: http://ltib.org >> >> Ltib mailing list >> [email protected] >> https://lists.nongnu.org/mailman/listinfo/ltib >> > _______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
