buildroot with the K3

[qlob]

It works, but take off the last "-" from that string... make is progressing now,

[twobob]

Originally Posted by qlob

It works, but take off the last "-" from that string... make is progressing now,

ah yeah. doh. apologies.

[qlob]

Doh. Just figured out the way buildroot really works.... I thought you dropped packages in just a random place somewhere and told buil root to build it, not that it was run every time you wanted to build packages.... need to read more...

[twobob]

in essence its a small 3 part process

Which I have outlined before but: since a picture and a few files can speak a thousand words.

create folder under packages (pictured - with relevant name)

create two files (provided examples) - edit them to use the "relevant name" - Just make one up.

BIG NOTE!!! YOU MUST REMOVE THE --prefix and --exec-prefix !!! you don't have a custom skeleton !! the target directories will be missing!! just run it without the --prefix etc.. until you build a custom skeleton (I can provide one)

You also need to go find the DL URL and copy the style I have provided.

The layout of the Config.in is VERY PICKY, keep the spacing exactly I have shown it. (four spaces indent is it? something like that)

When you are happy with your two new files:

add an entry - in the "relevant section" in the main packages Config.in (example provided with custom entries, search is your friend) (The placement in the file determines which menu it appears in)

re-run make xconfig. wow! they are there! let's build them!!!
ah shoot it broke! check the error output. it probably requires a lib BR doesn't have or you forgot to add support for in the make. Just add the relevant

requires - or selects - in the PACKAGE Config.in and maybe check the ./configure --help in the PACKAGES BUILD DIRECTORY!

Another trick:

say we have BR in ~/GIT/BRK3

always add it -C to your commands like:

make -C ~/GIT/BRK3 xconfig
(Then you can run the commands from ANYWHERE, not just the root.) helpful!

Err... I think that covers it.
EDIT: Ah yes. also try BR inline autocompletion for packages with the -C blah in place.
BR can delete the ".stamp_somethingLikeBuiltOrWhatever" flag files to help with letting BR know you want to rebuild something. Once it is "built" you have to tell it to rebuild like

make -C ~/GIT/BRK3 someapp-clean-for-rebuild (or whatever)

or you can go delete the flags yourself (I just do that TBH)
it's pretty obvious what they do - want to DL it again? delete .stamp_downloaded - etc...
(EDIT: Added a picture of the stamps - NOTE THE DIRECTORY)

RE MAKEFILE's:
The BR Readme covers the 3 main types of make files (It accepts).

Just get used to spotting the GNU Autotools ones and try adding them first - they work 95% of the time on the Kindle 5, - your milage will be less as the older TC may let you down from time to time.

Well, I'll attach the pics. I also pictured WinSCP ready to transfer built files.

HTH

[qlob]

Originally Posted by twobob

in essence its a small 3 part process

Which I have outlined before but: since a picture and a few files can speak a thousand words.

create folder under packages (pictured - with relevant name)

create two files (provided examples) - edit them to use the "relevant name" - Just make one up.

You also need to go find the DL URL and copy the style I have provided.

The layout of the Config.in is VERY PICKY, keep the spacing exactly I have shown it. (four spaces indent is it? something like that)

When you are happy with your two new files:

add an entry - in the "relevant section" in the main packages Config.in (example provided with custom entries, search is your friend) (The placement in the file determines which menu it appears in)

re-run make xconfig. wow! they are there! let's build them!!!
ah shoot it broke! check the error output. it probably requires a lib BR doesn't have or you forgot to add support for in the make. Just add the relevant

requires - or selects - in the PACKAGE Config.in and maybe check the ./configure --help in the PACKAGES BUILD DIRECTORY!

Another trick:

say we have BR in ~/GIT/BRK3

always add it -C to your commands like:

make -C ~/GIT/BRK3 xconfig
(Then you can run the commands from ANYWHERE, not just the root.) helpful!

Err... I think that covers it.
EDIT: Ah yes. also try BR inline autocompletion for packages with the -C blah in place.
BR can delete the ".SomethingLikeBuiltOrWhatever" flag files to help with letting BR know you want to rebuild something. Once it is "built" you have to tell it to rebuild like

make -C ~/GIT/BRK3 someapp-clean-for-rebuild (or whatever)

or you can go delete the flags yourself (I just do that TBH)
it's pretty obvious what they do - want to DL it again? delete .Donwloaded - etc...

RE MAKEFILE's:
The BR Readme covers the 3 main types of make files (It accepts).

Just get used to spotting the GNU Autotools ones and try adding them first - they work 95% of the time on the Kindle 5, - your milage will be less as the older TC may let you down from time to time.

Well, I'll attach the pics. I also pictured WinSCP ready to transfer built files.

HTH

Thanks so much! ngircd appears to already be in buildroot

[knc1]

Originally Posted by qlob

It works, but take off the last "-" from that string... make is progressing now,

I thought I was clear that was for the setting of the environment variable CROSS_COMPILE when using "manual make files" .

Build systems, often create their own equivalent of "CROSS_COMPILE" (Buildroot is one of them).
So there can be no common rule about the trailing '-' other than read the build system documentation.

[twobob]

Originally Posted by qlob

Thanks so much! ngircd appears to already be in buildroot

Yep. I was messing around with using alien armel builds the other day when you asked is all

Originally Posted by knc1

I thought I was clear that was for the setting of the environment variable CROSS_COMPILE when using "manual make files" .

Build systems, often create their own equivalent of "CROSS_COMPILE" (Buildroot is one of them).
So there can be no common rule about the trailing '-' other than read the build system documentation.

Yeah, There are great docs and even the website is fairly user friendly.

I read the docs about 10? times now. still only retain about 15% probably but it slowly goes in

Luckily only 15% is required to fire it up and let it run. Heh.

@qlob There are also lovely docs on doing a REALLY NEAT JOB (free electrons peoples do a good job of sharing tips, if a bit random) - might want to think about doing that. it's less of a PITA in the end. but your call.

: ) Enjoy the power.

[knc1]

Don't forget the "make manual" command if your using a "git clone".
The manual is inside of the release tar-ball, but not in the "git clone".

On multiple copies of BR . . .
git clone git://.....whatever the url is
Call that one your 'master'

For your working copies, just git clone the_local_path_and_name_of_the_master

[twobob]

Originally Posted by knc1

Don't forget the "make manual" command if your using a "git clone".
The manual is inside of the release tar-ball, but not in the "git clone".

On multiple copies of BR . . .
git clone git://.....whatever the url is
Call that one your 'master'

For your working copies, just git clone the_local_path_and_name_of_the_master

(and unless you apt-get is NOT configured to download "recommended" packakges? Get ready for a long wait)

[qlob]

SDL seems to be breaking... I did get ncurses built though, not sure if it is already on the Kindles, just picked programs I thought would be useful.

From now on, I'm most likely going to do only 1 or 2 packages at a time.

[twobob]

SDL build is breaking? or the resulting binary.

resulting binary wont work OOTB because of 4bpp FB. could be patched though. I will need clues to start doing that however...

If build is breaking I will test it in the AM

having fun? : )

[qlob]

the build, It's missing some sort of .so file...

Yeah, actually. never thought compiling could be fun xD .

Will deal with building things tomorrow, need to sleep.

hacking tired kills kindles, as they say.

[twobob]

Originally Posted by qlob

the build, It's missing some sort of .so file...

Yeah, actually. never thought compiling could be fun xD .

Will deal with building things tomorrow, need to sleep.

hacking tired kills kindles, as they say.

Ah right. I will have a play in the tomorrow too then. Might be the TC, undecided right now.

Night fella, good to have someone else on board with the BR hacking.

[knc1]

Originally Posted by twobob

(and unless you apt-get is NOT configured to download "recommended" packakges? Get ready for a long wait)

I keep forgetting that 2Gbyte of dependent packages that it takes to build the manual.

It might be worth the bandwidth to download a release tar-ball, just for the manual and throw away the rest of the files.

[qlob]

I think i used the tarball...