It complains that GraphViz is not found under Program Files. Correct, being a 32-bit program, it gets installed under Program Files (x86) on Windows 7 64-bit.
I am not sure whether it would be dangerous to move it.
Moving GraphViz to the 64 bit directory probably wouldn't work - my understanding is that the two Program Files directories are treated differently by Windows.
However, there is an easy way to get this to work - NAntGraph can be configured with the path to dot.exe so that it doesn't need to search for it.
I've written up description of how this works and added it to the main documentation for NAntGraph - see Configuration under the NAntGraph menu item.
I should have documented this earlier so that you didn't run into an issue. I'll make sure documentation and examples show up in a new release shortly.
I stumbled across your tool earlier today. I was hoping it would help me map out all the various files used for a particular build. None of our build scripts are single file, instead they make heavy use of include files with targets accessible to multiple build scripts. After the first execution, I noticed only the single build file was mapped. Is there a preferred method for mapping all the files included?
While the current version doesn't automatically include linked files, you can list multiple files on the commandline and they will all be loaded in and rendered in a single image.
Though, I'm not sure if this will suit your situation or not.
Comments
nantgraph2 does not work on 64-bit windows
It complains that GraphViz is not found under Program Files. Correct, being a 32-bit program, it gets installed under Program Files (x86) on Windows 7 64-bit.
I am not sure whether it would be dangerous to move it.
NAntGraph has configuration for this
Hi John.
Moving GraphViz to the 64 bit directory probably wouldn't work - my understanding is that the two
Program Filesdirectories are treated differently by Windows.However, there is an easy way to get this to work - NAntGraph can be configured with the path to
dot.exeso that it doesn't need to search for it.I've written up description of how this works and added it to the main documentation for NAntGraph - see Configuration under the NAntGraph menu item.
I should have documented this earlier so that you didn't run into an issue. I'll make sure documentation and examples show up in a new release shortly.
Thanks for the feedback,
Bevan.
Graphing NAnt build files with includes
I stumbled across your tool earlier today. I was hoping it would help me map out all the various files used for a particular build. None of our build scripts are single file, instead they make heavy use of include files with targets accessible to multiple build scripts. After the first execution, I noticed only the single build file was mapped. Is there a preferred method for mapping all the files included?
Graphing multiple build files
While the current version doesn't automatically include linked files, you can list multiple files on the commandline and they will all be loaded in and rendered in a single image.
Though, I'm not sure if this will suit your situation or not.
Cheers,
Bevan.