Does MacPorts require XCode 3.0's UNIX developer support?

[J.D. Merrick]

When installing Xcode 3.0 on Leopard, by default Unix developer  
support is disabled.  That is, by default the command line tools  
(gcc, ld, etc.) are installed in /Developer without adding to the  
boot volume symlinks to the tools in /usr/bin or to the header files  
in /usr/include.

Does MacPorts, including both the application itself as well as its  
individual ports, require those tools to be in /usr?  Or, is it just  
necessary for the tools to be visible in one's PATH?

The issue would arise if, for example, makefiles used hardcoded paths  
like /usr/bin/gcc or #include directives used paths like /usr/include/ 
stdio.h.  Do port maintainers attempt to remove such fully qualified  
filenames when working on a port?

I'd prefer not to have the development tools in /usr just because I  
just like keeping the root file system as clean as possible.  But if  
MacPorts needs it, I'll break the rule.

Thanks in advance,

J.D.