Heikki Toivonen <heikki@citec.fi> from the DocZilla project suggested this - Unlike every other compiler on the planet, xpidl currently doesn't accept -Ifoo, but instead requires -I foo I learned it the first way myself, but it seems likely that xpidl will borrow $(INCLUDES) lines from other build systems, so it makes sense to follow other compilers there.

It seems reasonable to fix this. But the $(INCLUDES) rationale may not hold water... If we export all idl files to dist/idl (as I plan) then the include path is constant and trivial.

Marking these as ASSIGNED. Pesky bugzilla-daemon.

Hm. It seems that xpidl happily finds its target file from the -I include paths, even when the target file isn't in the working directory. Is this a feature, or a bug?

Checked in a fix.

I vote bug. This could cause subtle and hidden errors but offers no significant advantage.