SamyGO

Hello everyone!

I'm looking to set up my own dev environment to be able to compile stuff for H Series TVs. Before I reinvent the wheel I thought I would ask if there is a preferred build environment (I was hoping for buildroot, since it can handle some depenencies). I found this documentation: http://wiki.samygo.tv/index.php?title=S ... _toolchain, but it looks rather old and I'm not sure if it's the best to follow for H-Series.

So, long story short - what are you guys using to compile stuff for H-Series?

My goal is to compile ImageMagik for it (and have "convert").

Also, as a side question - is there in place an "app distribution mechanism"? Meaning, if I compile ImageMagik and I build something that requires it and I want to share it with the community (I'm thinking of developing a webend remote + screenshot utility based on existing libraries) - is there a preferred way of doing it?

Thanks!

Bump?

ANY arm toolchain works. Rest are available on samsung website and also here: http://download.samygo.tv/Toolchains/

About "ImageMagic question" -> NOT understand

Thank you for the link. I'll look into it.

Regarding my Imagemagik question - the broader question was about software distribution. I've previously been a member of the WDLXTV community that used a concept of app.bins for software distribution. An app.bin was an ext3 or cramfs image that stored all the files/libs/binaries/startupscripts that were needed to run that application (example applications can be found here for reference: http://apps.wdlxtv.com/). On startup a script on the firmware would scan for a list of app.bin files in the root of the USB drive and activate them (loop-mount them, run startup scripts).

The app.bin developer would package as many files as needed into one app.bin and have the end user download it and copy it to the USB drive.

I was wondering if SamyGO already had a similar system in place, but from what I've read on the forum most software distribution (libso, config files) is done via the forum mostly - probably because we're talking about just a few files.
I'll look into porting the app.bin loader mechanism for SamyGO, because having the user copy a bunch of files (including symlinks) into different directories will be a pain for everyone...

well 95% of my libs have just single file that you copy to /tmp/