So I converted all my code to use the C interface, thankfully it took less time than I expected. Most of mpd’s codebase uses plain C anyway, so maybe it will be for the better when I submit my patch.

After I changed the file extension from .cxx to .c, it was time to change the autotools configuration files so that wily bunch knows this is c and not c++. So pewpewpew get rid of the check for the C++ compiler for my file and change some more extensions. After an autoreconf -i to regenerate the configure script and Makefile.in I attempt to compile, and I get this:

make[1]: *** No rule to make target `src/decoder/gme_decoder_plugin.cxx', needed by `src/decoder/src_mpd-gme_decoder_plugin.o'.  Stop.

wat

But there is no gme_decoder_plugin.cxx anymore!

I furiously type make clean and autoreconf -i over and over but no cigar. Still get the same error. Hmm maybe I need to run some other programs that begin with auto*.

So I try automake. This output catches my eye:

automake-1.11: Sources ending in .c become .o
automake-1.11: Sources ending in .c become .obj
automake-1.11: reading /usr/share/automake-1.11/am/lang-compile.am
automake-1.11: Sources ending in .cxx become .o
automake-1.11: Sources ending in .cxx become .obj

Perhaps this could be a problem for tracking dependencies, since both .c and .cxx will end up with the same extension when compiled into object files?

Then I noticed another automake option:

Dependency tracking:
  -i, --ignore-deps      disable dependency tracking code
        --include-deps     enable dependency tracking code

I tried automake with the -i option, and blingblong everything is gravy. So as far as I can tell, the dependency tracking decided the gme_decoder_plugin.o file’s dependency was still gme_decoder_plugin.cxx when it tried to generate the Makefile.in from Makefile.am.

However, I ran ‘make clean’ several times before to try to solve the problem, therefore deleting the .o file. How exactly does automake track dependencies then?

So I google for libsidresidbuilder, and I get a packages.debian.org page for the package. I download and unpack it and hmm, it looks exactly like the libsidplay package from portage! There are libsidplay, libsidutils, resid, and builder subdirectories.

My guess is that libsidplay in portage is just not compiling the resid and libresidutils? Maybe some USE flags need to be suggested to allow building these, although I can’t imagine why you wouldn’t want to build them.

ln -s /etc/init.d/netif.tmpl /etc/init.d/netif.eth0

You then add the details for your interface in /etc/conf.d/netif.eth0. I won’t go over the details because the funtoo core networking guide does already.

Funtoo also uses grub 2, but I havn’t tried to set that up yet because grub was already on my other partition.

Haven’t got networking to work yet on my funtoo partition, but I’m very excited about the idea of portage using git, and I may switch my other gentoo boxes to use git with portage if it works out.

Hmm well, good thing I’m using gentoo, I thought! So I went to see what extra use flags could be set for xvidcap. There were only two, mp3 and theora. I enabled them both and rebuilt the package, and still no audio support!

After googling the issue I found this gentoo bug report: http://bugs.gentoo.org/show_bug.cgi?id=258042.

I tried the patch mentioned there for configure.in. It was supposedly because it was checking for an outdated function in ffmpeg. For some weird reason xvidcap has its own ffmpeg directory with the entire ffmpeg source in it! You have the option to use a system provided ffmpeg or this internal ffmpeg by passing the option “–without-forced-embedded-ffmpeg”. I tried both options, with and without this patch from bugs.gentoo.org and there were still compile time failures.

It appears xvidcap is still using an outdated ffmpeg api, maybe the aforementioned patch fixed it at the time. Here’s my compile error(or at least the relevant part):

: In function `add_audio_stream':
/var/tmp/portage/x11-misc/xvidcap-1.1.7/work/xvidcap-1.1.7/src/xtoffmpeg.c:394: undefined reference to `av_fifo_init'
xtoffmpeg.o: In function `do_audio_out':
/var/tmp/portage/x11-misc/xvidcap-1.1.7/work/xvidcap-1.1.7/src/xtoffmpeg.c:552: undefined reference to `av_fifo_write'
/var/tmp/portage/x11-misc/xvidcap-1.1.7/work/xvidcap-1.1.7/src/xtoffmpeg.c:555: undefined reference to `av_fifo_read'
xtoffmpeg.o: In function `cleanup_thread_when_stopped':
/var/tmp/portage/x11-misc/xvidcap-1.1.7/work/xvidcap-1.1.7/src/xtoffmpeg.c:673: undefined reference to `av_fifo_read'

I did some research, and the api for av_fifo* has changed. av_fifo_init changed to av_fifo_alloc, which was easy to change. av_fifo_write and av_fifo_read have changed to av_fifo_generic_write and av_fifo_generic_read, which require you to pass a pointer to a write/read function. This will require some more work to change these to the new api.

But I’m sure I’ll just forget about this in a few hours like all my other ideas for new projects.

tony@0_o ~/ $ emerge timdity++

Then start timidity with the timidity init script.

tony@0_o ~/ $ sudo /etc/init.d/timidity start

I use an e-mu xboard49. When I plug it in, I can see the midi ports available with aplaymidi -l.

tony@0_o ~/ $ aplaymidi -l
 Port    Client name                      Port name
 14:0    Midi Through                     Midi Through Port-0
 24:0    E-MU Xboard49                    E-MU Xboard49 MIDI 1
128:0    TiMidity                         TiMidity port 0
128:1    TiMidity                         TiMidity port 1
128:2    TiMidity                         TiMidity port 2
128:3    TiMidity                         TiMidity port 3

Then I can connect the two ports with aconnect.

tony@0_o ~/ $ aconnect 24:0 128:0

Then voila! Insant midi jam. You can select which midi patch with your midi controller, its called “select pgm bank” or something like that.

Next I’m going to try to install some soundfonts.

for FILE in *.jpg; do echo $FILE; convert -geometry 50% $FILE $FILE; done;

Sometimes you need to check variables:

#define LOG(x, fmt)		fprintf(stderr, "LOG: %s : %" #fmt "\n", #x, x)

LOG(butt, f);

Sometimes you just want to print something, to see if a loop or branch is being executed:

#define CHECK(x)		fprintf(stderr, "CHECK: %s\n", #x)

CHECK(hi);

Then you pass into CHECK whatever string you want to be printed.

Note I didn’t put a semicolon at the end of the macros. If I did, then I would have to remember to not put one when I used the macros, otherwise I would end up with two semicolons when the macro expanded!

I’ve seen a lot more complicated debugging systems implemented in larger projects, but these will work fine for now.

Another command to turn whitespace into tabs.

=a{

Reindents everything in the current block(between the previous ‘{‘ and next ‘}’). This command will do the same thing on the entire file:

g=GG

set -g default-command zsh

#status bar
set -g status-bg black
set -g status-fg cyan

#use C-o instead of C-b
unbind C-b
set -g prefix C-o
bind C-o send-prefix
bind o send-prefix

Got this mostly from the examples on tmux.sourceforge.net. First off I needed to change the default modifier key C-b to C-o, C-b conflicts with the shell and vim. Then I figured I’d change the statusbar color and take this opportunity to start using zshell.

Nothin’ like the good life.

highlight WhitespaceEOL ctermbg=red guibg=red
match WhitespaceEOL /\s\+$/

That worked pretty well because it highlighted all the trailing whitespace red, so it was easy to find and delete. But what if you want to delete all whitespace in one go? You need a user command like this:

command -nargs=0 -range=% NukeWhiteSpace ,s/\s\+$//g

Now you can just do :NukeWhiteSpace and all that whitespace will be gone!

Bigup #vim for helping me with this.