<div dir="ltr">On Wed, Jun 12, 2013 at 11:03 AM, Bill Hoffman <span dir="ltr"><<a href="mailto:bill.hoffman@kitware.com" target="_blank">bill.hoffman@kitware.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 6/12/2013 10:29 AM, J Decker wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It's not nessesary for 2005, 2008, 2010, or 2012 versions.<br>
visual studio builds a seperate browse information database. 2010 and<br>
12, when in sources you can right click on the #include <filename><br>
filename and open directly.<br>
<br>
Headers do get all mixed up in the same headers folder (including all<br>
the system headers that got included) but they do not need to be<br>
specified; and updating the timestamp on a header does cause proper<br>
compiles without them being listed.<br>
</blockquote></div>
I disagree... :)<br>
<br>
If you want them organized into folders then you should add them. VS IDE developers like to have them. They are not required for the build to work (unless they are generated files). However, if you have developers on the team that really use the VS IDE, they will want those header files listed as sources of the project, so they can click on them and edit them. They will not want to have to open a .cxx file and right click on a header to edit it.<div class="HOEnZb">
<div class="h5"><br>
<br>
-Bill<br>
<br>
</div><div class="h5"><br></div></div></blockquote><div><br></div><div>Another reason to have the headers in the project is for when doing project or solution wide text searches. Unless the header file is in there it won't search those files even if they are included.</div>
<div><br></div><div>James</div></div><br></div></div>