autoconf, Visual C++ and current CVS build?

Am I being more than normally dumb this festive season (can't be too much
indulgence, yet!) or is the current CVS checkin really broken?

Non-existent files like win32/getopt.h are referenced and the new #include
<beepcore-c/...> style hasn't been catered for in the Visual C++ projects.

Whilst comfortable programming old-fashioned Unix with makefiles etc. I'm
not up on the subtleties of using autoconf and have no idea how you
reconcile what appears to be an installation step with the CVS idea of
pointing at a working directory.

It seems, from fringe comments, that after checking out, you have to run
autoconf (on Unix) to put files into the correct directories.

Does this mean, when you are actively developing, you are supposed to work
against files in /usr/include?

I thought it was a big no-no to use <> inclusion for local package files?
Why can't relative refs in "" includes be used instead?

I've had to roll my own stack initially because we're using a pure XML
format for framing to talk to Flash (if there is interest, I'll publish
some stuff) and incorporating this in beepcore-c seemed way too hard and a
bit rude.

However, I expect to be using pure BEEP for other connections and I'm quite
happy to contribute back working Mac, WinCE and Win32 projects once I know
I've got a stable starting point :-)
-- 

Andy Dent BSc  MACS  AACM   http://www.oofile.com.au/
OOFILE - Database, Reports, Graphs, GUI for c++ on Mac, Unix & Windows
PP2MFC - PowerPlant->MFC portability


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf