Hi shai,
Congratulations on the port. I'll try to address some of the issues you experienced:
"it requires SDL- and ALSA-check m4 macros (sdl.m4 and alsa.m4)"These are included in the source distribution archive, they are purposel omitted from the svn repository (anything that is autogenerated isn't stored on the svn).
"use macros to check for libzzip and remove it from the source archive (you probably know that as you already hardcoded in the automake files to link the binary against libzzip and don't use the internal version anymore)."Again, this is on the svn development trunk only - it will be altered when the next version is released. Pailes is reluctant to remove it from the source archive at present due to various reasons. It's worth pointing out that the automake build system is currently only used for the SDL version, OSX and Windows go there own way.
"you should really check whether SDL supports OpenGL in configure.in"Development version only.. The opengl support was just a test, and will probably be dropped altogether as it offered no advantages.
"Usually one has to add SDLCALL macros for SDL callbacks and you have to take care of atexit(SDL_Quit)-like statements because the SDL library calling convention (OS/2 syscall) differs from the C calling convention. Nevertheless it compiled and worked fine without it which even surprised me."Are you sure? I had already made those changes to the trunk before you downloaded it.
Regarding the mouse pointer flicker, blame SDL - it must not be using the hardware pointer, you'd be better patching SDL to fix this rather than writing a workaround specific to Milkytracker.
Posix or native path handling? You decide! Native might be better.
I prefer Milkytracker's internal filebrowser/message box rather than the OS provided ones. Makes it feel more integrated.
