BUG: Work-around Watcom WMake limitation for multiple-output custom command support.

1 files changed, 9 insertions, 0 deletions

diff --git a/Source/cmGlobalUnixMakefileGenerator3.h b/Source/cmGlobalUnixMakefileGenerator3.h
index 3f8dbc2..6ad6ec9 100644
--- a/Source/cmGlobalUnixMakefileGenerator3.h
+++ b/Source/cmGlobalUnixMakefileGenerator3.h
@@ -110,6 +110,9 @@ public:
       check-build-system step.  */
   virtual void CheckMultipleOutputs(cmMakefile* mf, bool verbose);
 
+  /** Get the command to use for a non-symbolic target file that has
+      no rule.  This is used for multiple output dependencies.  */
+  std::string GetEmptyCommandHack() { return this->EmptyCommandsHack; }
 protected:
   void WriteMainMakefile2();
   void WriteMainCMakefile();
@@ -151,6 +154,12 @@ protected:
   // that can be added.
   std::string EmptyRuleHackDepends;
 
+  // Some make programs (Watcom) do not like rules with no commands
+  // for non-symbolic targets.  If non-empty this variable holds a
+  // bogus command that may be put in the rule to satisfy the make
+  // program.
+  std::string EmptyCommandsHack;
+
   typedef std::map<cmStdString, cmStdString> MultipleOutputPairsType;
   MultipleOutputPairsType MultipleOutputPairs;
 };