[Owasp-esapi-c++] IDE Project Files
noloader at gmail.com
Thu Aug 4 00:15:53 EDT 2011
On Wed, Aug 3, 2011 at 11:11 PM, Kevin W. Wall <kevin.w.wall at gmail.com> wrote:
> On Wed, Aug 3, 2011 at 3:10 PM, Jeffrey Walton <noloader at gmail.com> wrote:
>> Hi All,
>> I noticed we have some Eclipse project files in root.
>> I think its great that the project offers support for IDE such as
>> Eclipse. In addition, I plan on getting this stuff into Visual Studio
>> (I know, but the idea is to make it easy on a typical user).
>> Should the IDE project files be corraled into folders? Perhaps:
>> or similar?
> In general, I find that Eclipse's ".project" file is generally not too
> useful, and on occasion (at least for the Eclipse meant for Java),
> can sometimes cause problems. I personally think it shouldn't be
> included in SVN at all. I generally ends up there by mistake b/c
> Eclipse usually checks it in. But personally, I don't think it belongs.
> It has more to do with what plugins you are using in Eclipse than
> the project itself.
> As for Visual Studio's '.cproject', that's a bit different as it at
> least has some information about the actual project.
OK - so Eclipse does not store anything useful, but Visual Studio does.
Someone else can delete the Eclipse project files if desired (I'm not
going to be responsible for breaking someone's IDE). But don't fret,
I'm sure I'll break them in the source files somehow ;)
Later, is it OK to add `ide/vs/` for Visual Studio? Or do you want IDE
support left out of source control (or perhaps a separate download).
More information about the Owasp-esapi-c++