Howto build a complete Image for any dreambox!

[hemertje]

see the original howto here:

http://cvs.tuxbox.org/cgi-bin/viewcv...=date&view=log

This is the current status:

Revision 1.197.2.51.2.1 - (view) (download) (annotate) - [select for diffs]
Fri Feb 4 18:04:40 2005 UTC (22 hours, 26 minutes ago) by ghostrider
Branch: dreambox
Changes since 1.197.2.51: +550 -269 lines
Diff to previous 1.197.2.51
new dreambox cdk part 3 ( final part )

To build a complete Image for any dreambox do following:

1.) create a lokal directory for your new dreambox cdk and change into this new directory

2.) check out tuxbox-cvs branch "dreambox":
export CVS_RSH=ssh
cvs -d anoncvs@cvs.tuxbox.org:/cvs/tuxbox -z3 co -P -rdreambox .

3.) change into "cdk" directory

4.) "chmod ugo+x prepare"

5.) "./prepare <dm7000, dm500, dm56x0> ( dm7000 is default )

6.) "make checkout" ( this updates many parts of the CVS to HEAD branch )

7.) "make dreamboximage_root"

8.) "make rebuild-flash"

9.) "make flash-compress"

you now find the new image in "../root/cdkflash" named "complete.img"

in root/cdkflash/ you can delete .part_? files to remove parts from the image.. or you can add other parts to image with make flash-?... to see what parts exist you can look into Makefile.am

in dm56x0 and dm500 image many space is left for add other things.. for dm7000 you must remove parts before you add other parts..
max size of cramfs (kernel+bild) is 1152K ( 1179648 bytes )
max size of squashfs is 4992K (5111808)
complete this is 6144K (6291456)

to remove sambaserver you only must remove .part_sambaserver in root/cdkflash.. to remove reiserfsck remove .part_reiserfsck

when you will add "other plugins, programs, files" to your Image you can copy your parts to root/cdkflash/dreamfiles/? (bin/sbin) .. then do make rebuild-flash and make flash-compress but take not that root/cdkflash/dreamfiles will be deleted when new version of dreamdrivers.. or dreamfiles are available..

the other way to add own files to your image is to put your files after flashing the image into the box to /var .. at this place you have 1.7MB.. for most things this is enough..

to remove partially languages edit Makefile.am in part "flash-enigma":
when you like to remove russian language from you image then change the followinmg for loop :
@for i in ar sr ur ; do rm -R $(flashprefix)/root/share/locale/$$i; done
into
@for i in ar sr ur it ; do rm -R $(flashprefix)/root/share/locale/$$i; done

the cdk downloads automatically all dreambox specific parts from sources.dreamboxupdate.com ( drivers.. closed source tools.. )


have fun...

[PLi®]

Works great.

The only problem I know have is that my own plugin won't worlk. Actually I have recompiled it with the newly build CDK and that has passed without errors. But when I try to install this in the newly build image I get errors that functions cannot be found so probably earlier stripped from the libs by mklibs.py

When I then first copy my plugin before mklibs.py runs then mklibs.py is not able to run completely because it cannot find the functions used from enigma.

Anybody know how I can fix this problem?

Peter

[xphile]

Yep take a look at Makefile.am. Look at any of the enigma based plugins and you find this comment:

flash-plugin_ngrabstartstop: $(flashprefix)/.part_plugin_ngrabstartstop
$(flashprefix)/.part_plugin_ngrabstartstop: $(flashprefix)/.flash .plugins flash-enigma
	$(INSTALL) -d $(flashprefix)/root/lib/tuxbox/plugins
# copy enigma plugins after mklibs.. (mklibs.py do not detect enigma as a shared lib)
	@touch $@

Then if you search a bit further you see:

@if [ -f $(flashprefix)/.part_plugin_ngrabstartstop ] ; then \
		cp $(targetprefix)/lib/tuxbox/plugins/ngrab*.so $(flashprefix)/root/lib/tuxbox/plugins/ ; \
		cp $(targetprefix)/lib/tuxbox/plugins/ngrab*.cfg $(flashprefix)/root/lib/tuxbox/plugins/ ; \
	fi

Basically the copy of enigma based plugins must happen after the mklibs step. Use ngrab as an example to follow.

Originally Posted by PLi®

Works great.

The only problem I know have is that my own plugin won't worlk. Actually I have recompiled it with the newly build CDK and that has passed without errors. But when I try to install this in the newly build image I get errors that functions cannot be found so probably earlier stripped from the libs by mklibs.py

When I then first copy my plugin before mklibs.py runs then mklibs.py is not able to run completely because it cannot find the functions used from enigma.

Anybody know how I can fix this problem?

Peter

[g_moir]

can you please help me with step 2?
i get no error when i do the export line, but cvs is an unknown command when doing the second line?

[Quinten]

Originally Posted by g_moir

can you please help me with step 2?
i get no error when i do the export line, but cvs is an unknown command when doing the second line?

You need to install cvs, or have priviledges set to run cvs as a user.

[PLi®]

Originally Posted by xphile

Yep take a look at Makefile.am. Look at any of the enigma based plugins and you find this comment:

flash-plugin_ngrabstartstop: $(flashprefix)/.part_plugin_ngrabstartstop
$(flashprefix)/.part_plugin_ngrabstartstop: $(flashprefix)/.flash .plugins flash-enigma
	$(INSTALL) -d $(flashprefix)/root/lib/tuxbox/plugins
# copy enigma plugins after mklibs.. (mklibs.py do not detect enigma as a shared lib)
	@touch $@

Then if you search a bit further you see:

@if [ -f $(flashprefix)/.part_plugin_ngrabstartstop ] ; then \
		cp $(targetprefix)/lib/tuxbox/plugins/ngrab*.so $(flashprefix)/root/lib/tuxbox/plugins/ ; \
		cp $(targetprefix)/lib/tuxbox/plugins/ngrab*.cfg $(flashprefix)/root/lib/tuxbox/plugins/ ; \
	fi

Basically the copy of enigma based plugins must happen after the mklibs step. Use ngrab as an example to follow.

I founded that also but then not all libs necessary for the plugin are available in the image because mklibs.py did not see my plugin abd then the plugin will not start but gives an unresolved external popup when started.

Peter

[PLi®]

I have found the solution.

The mklibs.py which you get when using the new Makefile is not correct. I found out that the version I had from my previous tree is working correctly.

Now you can edit Makefile.am (in cdk dir) so that plugins are copied before mklibs.py will run,

example,
this is how it is :

	@$(PYTHON) $(flashprefix)/mklibs.py --target $(target) --ldlib ld.so.1 --libc-extras-dir $(targetprefix)/lib/libc_pic \
		-d $(flashprefix)/root/lib \
		-D -L $(targetprefix)/lib \
		--root $(flashprefix)/root \
		`find $(flashprefix)/root/bin/ -path "*bin/?*"` \
		`find $(flashprefix)/root/lib/ -name "libnss_*"` \
		`find $(flashprefix)/root/lib/tuxbox/ -name "*.so" -type f` \
		`find $(flashprefix)/root/sbin/ -path "*sbin/?*"`
	@if [ -f $(flashprefix)/.part_plugin_ngrabstartstop ] ; then \
		cp $(targetprefix)/lib/tuxbox/plugins/ngrab*.so $(flashprefix)/root/lib/tuxbox/plugins/ ; \
		cp $(targetprefix)/lib/tuxbox/plugins/ngrab*.cfg $(flashprefix)/root/lib/tuxbox/plugins/ ; \
	fi

and this is how it now can be so you won't have unresolved externals in your plugin ;-)

	@if [ -f $(flashprefix)/.part_plugin_ngrabstartstop ] ; then \
		cp $(targetprefix)/lib/tuxbox/plugins/ngrab*.so $(flashprefix)/root/lib/tuxbox/plugins/ ; \
		cp $(targetprefix)/lib/tuxbox/plugins/ngrab*.cfg $(flashprefix)/root/lib/tuxbox/plugins/ ; \
	fi
	@$(PYTHON) $(flashprefix)/mklibs.py --target $(target) --ldlib ld.so.1 --libc-extras-dir $(targetprefix)/lib/libc_pic \
		-d $(flashprefix)/root/lib \
		-D -L $(targetprefix)/lib \
		--root $(flashprefix)/root \
		`find $(flashprefix)/root/bin/ -path "*bin/?*"` \
		`find $(flashprefix)/root/lib/ -name "libnss_*"` \
		`find $(flashprefix)/root/lib/tuxbox/ -name "*.so" -type f` \
		`find $(flashprefix)/root/sbin/ -path "*sbin/?*"`

I hope this is clear for anybody

I have attached it on this message for everybody ;-)

Peter

[Gandalf3]

Thanks Peter, very helpfull

G

[Quinten]

I should really do a search first, but is there something like a test plugin (a simple "hello world" plugin would do just fine) around to start developing from? Yesterday I followed the above instructions and got it compiled (and running on the DB as well :o), and am now hungry for more

[Iveky3]

why i get these messages and is it critical?

...
RCS file: /cvs/tuxbox/apps/tuxbox/enigma/po/fi.po,v
retrieving revision 1.18
retrieving revision 1.1.2.6
Merging differences between 1.18 and 1.1.2.6 into fi.po
rcsmerge: warning: conflicts during merge
cvs checkout: conflicts found in apps/tuxbox/enigma/po/fi.po
C apps/tuxbox/enigma/po/fi.po
...


I get them on many files.