kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

VS10: add detailed comment about MIDL processing

This commit is contained in:
Andreas Mohr 2013-04-16 16:02:47 +02:00 committed by Brad King
parent e619111d91
commit 2bab472ecb
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Source/cmVisualStudio10TargetGenerator.cxx
View File

@ -1579,6 +1579,21 @@ void cmVisualStudio10TargetGenerator::
WriteMidlOptions(std::string const& /*config*/, WriteMidlOptions(std::string const& /*config*/,
std::vector<std::string> const & includes) std::vector<std::string> const & includes)
{ {
// This processes *any* of the .idl files specified in the project's file
// list (and passed as the item metadata %(Filename) expressing the rule
// input filename) into output files at the per-config *build* dir
// ($(IntDir)) each.
//
// IOW, this MIDL section is intended to provide a fully generic syntax
// content suitable for most cases (read: if you get errors, then it's quite
// probable that the error is on your side of the .idl setup).
//
// Also, note that the marked-as-generated _i.c file in the Visual Studio
// generator case needs to be referred to as $(IntDir)\foo_i.c at the
// project's file list, otherwise the compiler-side processing won't pick it
// up (for non-directory form, it ends up looking in project binary dir
// only). Perhaps there's something to be done to make this more automatic
// on the CMake side?
this->WriteString("<Midl>\n", 2); this->WriteString("<Midl>\n", 2);
this->OutputIncludes(includes); this->OutputIncludes(includes);
this->WriteString("<OutputDirectory>$(IntDir)</OutputDirectory>\n", 3); this->WriteString("<OutputDirectory>$(IntDir)</OutputDirectory>\n", 3);