Avoid hard-coded extensions for compilation outputs.

The multi-layered transformation (base -> base.pic -> base.pic.pcm -> base.pic.pcm.d) is kinda ugly, but is preferable to having 22 separate, mostly orthogonal artifact categories.

It's actually untested what happens if we put these new name patterns into the CROSSTOOL file.

--
MOS_MIGRATED_REVID=129423055

1 files changed, 15 insertions, 0 deletions

diff --git a/src/test/java/com/google/devtools/build/lib/rules/cpp/CcLibraryConfiguredTargetTest.java b/src/test/java/com/google/devtools/build/lib/rules/cpp/CcLibraryConfiguredTargetTest.java
index 9842db86e0..1c6f7548b3 100644
--- a/src/test/java/com/google/devtools/build/lib/rules/cpp/CcLibraryConfiguredTargetTest.java
+++ b/src/test/java/com/google/devtools/build/lib/rules/cpp/CcLibraryConfiguredTargetTest.java
@@ -293,6 +293,21 @@ public class CcLibraryConfiguredTargetTest extends BuildViewTestCase {
   }
 
   @Test
+  public void testObjectFileNamesCanBeSpecifiedInToolchain() throws Exception {
+    AnalysisMock.get()
+        .ccSupport()
+        .setupCrosstool(mockToolsConfig,
+            "artifact_name_pattern {"
+                + "   category_name: 'object_file'"
+                + "   pattern: '%{base_name}.obj'"
+                + "}");
+
+    useConfiguration();
+    ConfiguredTarget hello = getConfiguredTarget("//hello:hello");
+    assertThat(artifactByPath(getFilesToBuild(hello), ".a", "hello.obj")).isNotNull();
+  }
+
+  @Test
   public void testArtifactSelectionBaseNameTemplating() throws Exception {
     AnalysisMock.get()
         .ccSupport()