Re: make file help please
I suggest you install Linux (Debian is really easy) and use that. I started off using cygwin and found it painfully slow (on my PIII 600) but after installing Debian, everything worked much faster and was more enjoyable. Daniel Stenberg wrote: On Thu, 2 Mar 2006, roolku wrote: I am working on a plugin in a cygwin h120 sim and I am tired of waiting for make to find out that nothing else has changed apart from the plugin itself. The build system (and everything else) is dead slow on cygwin because the file system/handling is extremely slow in cygwin. So I just want to compile that single c file. For that purpose I added a new target to the makefile in my build directory like this: If you really want to venture down that road I wish you good luck but I don't feel like spending much of _my_ time on it.
building/distributing plugins separately (Re: make file help please)
I am working on a plugin in a cygwin h120 sim and I am tired of waiting for make to find out that nothing else has changed apart from the plugin itself. I think the clean way to develop a plugin would be to be able to build it from another directory than the rockbox build dir. Linux developpers may think about how kernel modules can be built from any directory, making it easier to distribute them separately. Here's how I had to fiddle with rockbox's make variables to do so. As you see, there are many hacks in there, especially concerning the pluginlink.lds file. It would be nice if we could just define the SRC variable, the BUILDDIR (this makefile works with simulators too), and then include a standard Makefile... BUILDDIR=/home/devernay/rockbox/iriver include $(BUILDDIR)/Makefile GCCOPTS += $(DELUXE) -O2 export OBJDIR=$(PWD) SRC=asteroids.c SUBDIRS= all: $(SRC:.c=.rock) clean: $(RM) pluginlink.lds $(SRC:.c=.elf) $(SRC:.c=.map) \ $(SRC:.c=.o) $(SRC:.c=.rock) *~ \#*\ install: all @if [ -d $(BUILDDIR)/archos ]; then \ echo Installing $(SRC:.c=.rock) in \ $(BUILDDIR)/archos/.rockbox/rocks \ install -d $(BUILDDIR)/archos/.rockbox/rocks; \ for f in $(SRC:.c=.rock); do \ install -m 755 $$f $(BUILDDIR)/archos/.rockbox/rocks/$$f; \ done \ else \ echo *** You must install $(SRC:.c=.rock) manually in the \ .rockbox/rocks directory on your player; \ fi $(SRC:.c=.rock): vsm.c game.c rom.h $(SILENT)ln -sf $(BUILDDIR)/apps/plugins/pluginlink.lds . @$(MAKE) -C $(APPSDIR)/plugins VPATH=$(PWD) \ SRC=$(SRC) SUBDIRS=$(SUBDIRS) BITMAPLIBS= V=1
Re: building/distributing plugins separately (Re: make file help please)
On Fri, 3 Mar 2006, Frederic Devernay wrote: I think the clean way to develop a plugin would be to be able to build it from another directory than the rockbox build dir. Linux developpers may think about how kernel modules can be built from any directory, making it easier to distribute them separately. I don't think anyone would mind fixes and changes that would make that easier! -- Daniel Stenberg -- http://www.rockbox.org/ -- http://daniel.haxx.se/
Re: make file help please
On 3/3/06, mathew holton [EMAIL PROTECTED] wrote: I suggest you install Linux (Debian is really easy) and use that. I I wouldn't recommend Debian to anyone who is new to Linux. I consider myself an experienced linux user and found other distributions way more beginner-friendly. I'd recommend Fedora Core (http://www.fedora.redhat.com) for beginners. (No, I don't want to start arguing about Debian -- it has its strengths, but I really think it isn't suited for beginners) -- Dominik
Re: make file help please
I would suggest Ubuntu as good Linux distribution. As it is based on Debian, the package system is imho incredibly good. Haven't used Fedora, but I guess that it is a .rpm based distro which as far as I know is not up to par with .deb. Ubuntu is also very easy to install and is functional straight out of the box. If your curious, you could always download the live-cd and try it out. On 3/3/06, mathew holton [EMAIL PROTECTED] wrote: Well, I won't start arguing about Debian then. All I know is that I had very little linux experience (I installed Red Hat about 7 years ago...that's it) and I found it extremely amazing. Maybe other distro's are just as amazing now, compared to 7 years ago. I don't know. Dominik Riebeling wrote: On 3/3/06, mathew holton [EMAIL PROTECTED] wrote: I suggest you install Linux (Debian is really easy) and use that. I I wouldn't recommend Debian to anyone who is new to Linux. I consider myself an experienced linux user and found other distributions way more beginner-friendly. I'd recommend Fedora Core (http://www.fedora.redhat.com) for beginners. (No, I don't want to start arguing about Debian -- it has its strengths, but I really think it isn't suited for beginners) -- Dominik
Re: make file help please
I also found this frustrating but got used to it in the end. Out of interest, what specifically causes this slow down? Something in the Unix file handling emulation I guess - but presumably this could be improved dramatically? -- gl - Original Message - From: mathew holton [EMAIL PROTECTED] To: Rockbox development rockbox-dev@cool.haxx.se Sent: Friday, March 03, 2006 8:55 AM Subject: Re: make file help please I suggest you install Linux (Debian is really easy) and use that. I started off using cygwin and found it painfully slow (on my PIII 600) but after installing Debian, everything worked much faster and was more enjoyable. Daniel Stenberg wrote: On Thu, 2 Mar 2006, roolku wrote: I am working on a plugin in a cygwin h120 sim and I am tired of waiting for make to find out that nothing else has changed apart from the plugin itself. The build system (and everything else) is dead slow on cygwin because the file system/handling is extremely slow in cygwin. So I just want to compile that single c file. For that purpose I added a new target to the makefile in my build directory like this: If you really want to venture down that road I wish you good luck but I don't feel like spending much of _my_ time on it.
wav codec broken
Hi,
someone broke the wav codec 6 weeks ago (it only affected the DVI_ADPCM
format). Here's the (quick) fix.
BTW, I don't think exit (which is a standard C function name) is a
good name for a label. EXIT would be better IMHO.
fred
Index: apps/codecs/wav.c
===
RCS file: /cvsroot/rockbox/apps/codecs/wav.c,v
retrieving revision 1.20
diff -u -r1.20 wav.c
--- apps/codecs/wav.c 18 Jan 2006 20:22:03 - 1.20
+++ apps/codecs/wav.c 3 Mar 2006 17:17:12 -
@@ -532,12 +532,14 @@
blockalign, channels, bitspersample,
int16_samples+i*samplesperblock*channels,
decodedsize)
-!= CODEC_OK)
+!= CODEC_OK) {
i = CODEC_ERROR;
-goto exit;
-if (decodedsize != samplesperblock)
+goto exit;
+}
+if (decodedsize != samplesperblock) {
i = CODEC_ERROR;
-goto exit;
+goto exit;
+}
}
wavbufsize = nblocks*samplesperblock*channels*2;
}
