What kind of squeezeboxes ? The 7.4.2 is an old version it does not work with a Touch for example .
http://wiki.slimdevices.com/index.ph...are_comparison .
Can also get a bit problematic if you switch between local server and mysqueezebox.com as you have to upgrade and downgrade player fw to match .
The whole idea would have more appeal if the OP updated the never versions now and then .
Results 21 to 30 of 39
-
2012-06-29, 23:02 #21--------------------------------------------------------------------
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3 sub.
Bedroom/Office: Boom
Kitchen: Touch + powered Fostex PM0.4
Misc use: Radio (with battery)
iPad1 with iPengHD & SqueezePad
(in storage SB3, reciever ,controller )
server HP proliant micro server N36L with ClearOS Linux
http://people.xiph.org/~xiphmont/demo/neil-young.html
-
2012-06-30, 16:50 #22Junior Member
- Join Date
- Oct 2011
- Posts
- 12
I have a Boom and a Radio.
Yes, updating the version would be appealing. If I could get some guidance on the ins and outs of the process I'd be willing to take on creating an updated package.
As for switching between mysqueezebox.com and the server, well.. if I could get the server to work on my router, I wouldn't have reason to switch anymore.
The whole point of this exercise is to avoid having to either keep my desktop powered all the time or switch my SB's to mysqueezebox.com when my desktop is powered off.
-
2012-06-30, 17:38 #23--------------------------------------------------------------------
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3 sub.
Bedroom/Office: Boom
Kitchen: Touch + powered Fostex PM0.4
Misc use: Radio (with battery)
iPad1 with iPengHD & SqueezePad
(in storage SB3, reciever ,controller )
server HP proliant micro server N36L with ClearOS Linux
http://people.xiph.org/~xiphmont/demo/neil-young.html
-
2012-07-02, 01:49 #24
I had Optware up and running on my RT-N16. I believe that this will be a good starting point, see here: http://www.dd-wrt.com/wiki/index.php..._the_Right_Way.
Then, installing the SBS package should be as easy as installing any other optware package
Regards,Code:ipkg install squeezeboxserver_7.4.2-1_mipsel.ipk
StefanSqueezebox Classic,
Squeezebox Radio,
Squeezebox Server 7.4.2 running on Asus RT-N16, DD-WRTv24
(Kernel 2.6.24.111, Perl 5.8.8, MySQL 5.0.88)
-
2012-07-02, 01:59 #25
Hi,
I would highly appreciate a newer build, unfortunately I don't have the time to do it on my own.
But updating the actual SBS server code shouldn't be a problem at all, because it is all Perl and thus needs no re-compile. But as far as I remember, when I built the 7.4.2 package, I seriously struggled with getting some dependent Perl modules from CPAN to work.
In the end, my solution was to link all required Perl modules statically into the Perl executable, instead of linking them dynamically, because this solved some really strange run-time errors...
Hope this helps!
Regards,
StefanSqueezebox Classic,
Squeezebox Radio,
Squeezebox Server 7.4.2 running on Asus RT-N16, DD-WRTv24
(Kernel 2.6.24.111, Perl 5.8.8, MySQL 5.0.88)
-
2012-07-22, 20:20 #26Junior Member
- Join Date
- Oct 2006
- Posts
- 11
Hi Stefan,
I've been poking around at trying to make a Logitech Media Server 7.7.2 ipk for mipsel architecture, but it's a significant challenge to take on from scratch. When you built 7.4.2, did you use the nslu2 optware templated build system? if not, what did you use? Could you provide an archive of your build environment (makefile and buildme.sh with any modificaitons) to help people looking to make new builds?
Anonymous247
-
2012-07-23, 00:25 #27
I built it on my Router itself from practically unmodified sources using the buildroot optware package, so downloading the CPAN module packages and compiling them out-of-the-box worked quite well for me.
But as mentioned above, in the end, I finally struggled with building dynamic modules for the perl executable, so I decided to include them statically linked, but I hope that this problem is solved today by up-to-date CPAN modules.Squeezebox Classic,
Squeezebox Radio,
Squeezebox Server 7.4.2 running on Asus RT-N16, DD-WRTv24
(Kernel 2.6.24.111, Perl 5.8.8, MySQL 5.0.88)
-
2012-07-23, 13:51 #28Junior Member
- Join Date
- Oct 2006
- Posts
- 11
What about packaging? What changes to the .mk file were necessary to package the results correctly? You must have altered the existing 'sed' command to change the first line of slimserver.pl and scanner.pl to refer to the custom build of perl. What other changes were made to that make file, and could you post it somewhere for others to look at? I've started with the existing squeezecenter.mk file in the nslu2 svn depot, and rebranded everything to logitechmediaserver, and I can get to the point where I can produce a valid IPK that installs correctly, but of course when I try to run slimserver after installation, it notes the missing modules.
I've seen the discussion here:
http://forums.slimdevices.com/showth..._Class__C3__XS
and that looks like it might be helpful in my attempts.
-
2012-07-24, 00:19 #29
Sorry, I already forgot about that thread. Yes, it really might help you, because it documents my struggling very well ;-).
But since this is two years ago, I do not have any helpful build scripts anymore for you. But anyways, I did not start off using the squeezecenter package from optware / nslu2, but used the original sources from logitech and from CPAN archives thus I do not know about the 'sed' command line from the nslu2 svn depot.
But I believe that different steps may be necessary today with up-to-date sources.
Good luck!Squeezebox Classic,
Squeezebox Radio,
Squeezebox Server 7.4.2 running on Asus RT-N16, DD-WRTv24
(Kernel 2.6.24.111, Perl 5.8.8, MySQL 5.0.88)
-
2012-07-24, 01:12 #30Senior Member
- Join Date
- Oct 2005
- Location
- Ireland
- Posts
- 11,252
When optware was started with NSLU2 and other - cross compiling was the only practical way to build a package and so the scripts on the optware svn are all aimed at cross compiling a package on a more powerful server. The cross compile system will build centrally an ipk for each optware supported device.
With more powerful processors and more memory on device it is more practical and more reliable to build packages natively unless you really want to create an ipk package.
If you are not cross compiling, I think you should follow Steevee288's advice - start with LMS sources on your device (e.g. router) ensure you have all the necessary optware packages loaded (e.g. perl, gcc, ld ) and running on your device and then build natively on the device - do not go near the Squeezecenter optware build system.


Reply With Quote

