Win32 build - directory structure

> I was under the impression that libzend & TSRM were _NOT_ supposed to > be "under" php4? That's how Andi explained it to me... Like I presume most of us have, when I started my first build on Win32 I scavenged the archives and got advice from Andi. Trouble was, I found multiple build instructions fragments, which taken together were inconsistent, incomplete, and even occasionally incorrect. What I am hoping to do with this web page is to consolidate the instructions and in the process resolve the issues necessary to make this work. My issues with placing the directories in a parallel structure (d:\projects\{php4,libzend,TSRM}) are two fold: 1) My first build was on Linux from a snapshot from bonsai. It's structure places libzend and TSRM inside the php4. I'd like some consistency between the two environments. 2) When I first tried it, it didn't work for me. I'm sure that there is some way to make it work and I would be interested in hearing how others have done so. I just tried again, and I get a slew of errors like the following: f:\projects\php4\php.h(36) : fatal error C1083: Cannot open include file: 'zend.h': No such file or directory I will say that parallel directories make it easier to interface with CVS. My strategy for coping with this is to have one set of "pristine" directories into which I do my updates and another set which I do my building, experimenting, and debugging. I'd like the instructions to reflect the consensus and standard practice. How have others resolved these issues?