I have a number of help and manual 5 projects.
They are very modular and I require CHM output (merged at runtime) and PDF (merged at publish). A typical structure of the projects is shown below where P1, P2 etc are the master projects, L1, L2 etc are the next level of 'libraries' and LA,LB etc are a further level of libraries as children of L1 etc.
L1-LA,LB,LC,LD etc
L2
P1-L1,L2
P2-L1
P3-LA,LC
For example, project P1 uses the libraries L1 and L2. Library L1 uses LA,LB,LC and LD.
H&M seems to encode child projects with absolute paths and this seems to require me to work on a documentation project at a fixed disk location. Can I presume therefore that the best way of using FB with H&M is to pick a disk location, knit the project and libraries together so that they publish manually in this location and then use FB to pull the H&M source from elsewhere on disk (or svn), FB builds the project in this 'defined' lolcation and then FB copies the build output (PDF, CHM) back to a published location (or as source for installer).
This seems messy but necessary. Is there a better way?
Thanks