Re: [p4] Null directory (//) not allowed
PeterB <[email protected]>
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'PeterB'. Assume my depot is setup like this: Proj1/ Files/ Random.cpp More/ stuff Proj2/ Files/ Random.cpp More/ stuff Misc/ One/ Sync.bat Two/ Sync.bat And Perforce views: Workspace One is for ARM //depot/. //One/. +//depot/Proj1/Files/. //One/. +//depot/Proj1/More/. //One/. +//depot/Misc/One/. //One/. Workspace Two is for x64 //depot/. //Two/. +//depot/Files/Proj2/. //Two/. +//depot/Proj2/More/. //Two/. +//depot/Misc/Two/. //Two/. It sounds like Sambwise is saying that I could get into trouble easily. Does Perforce get confused with “Files”, “Misc” or “More”? He mentioned stream. Would using stream eliminate the problem? I.e. just check stream “and away go troubles…”. I really want to end up with what I call a flat directory structure in my workspace root. Perhaps later I will put header files in WorkspaceRoot/h but (I’m guessing here) that’s an easy change to the overlay structure: //One/h/. As mentioned in a previous post I structured the depot to exploit the commonality of the various files I am working with. I.e. same headers for ARM and x64. And for each unique workspace a sync.bat. FWIW, I wrote a perl script that assisted in obliterating all deleted files. Then extended it to do the same with all downlevel files. Still had problems. I would greatly appreciate any hints, sample workspace fragments or web pages that lead me away from trouble. -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/5477-null-directory-not-allowed _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user