Sorry, you have to provide two packages if you need multiple
pre-byte-compiled packages for XEmacs and Emacs. Or you might be able
to compile with a byte-compiler from a very old emacs. Needs testing.
I know *that*. I guess I wasn't clear enough.
I use conditional compilation to select function and macro definitions
targeted at specific XEmacs versions. Ugly as a hippo with zits, but
regrettably necessary for performance reasons (code that is compatible
with all relevant Emacs versions is noticably slower).
The same kind of problem can occur even if you don't write twisted
code like I do. All it takes is a macro definition in the base set of
packages that changes in an incompatible way between XEmacs versions
since macro definitions get expanded at compile time.
The point is that in my case (and potentially others), the output of
the 21.1.8 byte compiler might not run properly in 21.2 and vice
I was simply wondering how to deal with this sort of problem in
packages for XEmacs. Can I have uncompiled package and have the Emacs
getting the package automatically build it?