Getting DevStudio dependencies correct

[Jonathan Gilligan]

I am working on a project in CWeb, where I work on a source file foo.w, which is then compiled by a custom build step to produce foo.c, foo.h, and foo.tex. I include foo.c, foo.h, and foo.tex in my project, and use the basic C compiler settings to control the compilation of the .c files and another custom build rule to control the compilation of the documentation foo.tex to foo.pdf. Here is where I get into trouble. A makefile would have no problem understanding that foo.tex depends on foo.w and that foo.pdf depends on foo.tex, so if foo.w has been changed, a build must FIRST compile foo.w to foo.tex and THEN compile foo.tex to foo.pdf. I can't seem to get DevStudio to understand this, so when I edit foo.w and hit build, it first compiles foo.tex to foo.pdf and then compiles foo.w to foo.tex!. Any thoughts? This is analogous to things people must also have gone through working with Bison and Flex in DevStudio. Bomb our homes and threaten our children, and, as difficult as it is, we will still love you --- Martin Luther King, Jr.

[J Patel]

Hi, Why not create 2 different projects and just have foo.w in one and the other files in the other project. You can then set project dependencies to have the second project (the one with .c,.h and .tex) files to be dependent on the first one. So, when you hit build it will compile the first project (seeing your .w has changed) and then compile the second one (with the newly generated files). I've never worked with Bison and Flex but this may work.. HTH Jignesh