[GRADLE-3364] Provide way to configure Visual C++ tool chain like GCC Created: 16/Nov/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Sterling Greene Assignee: Unassigned
Resolution: Won't Fix Votes: 0


With GCC/Clang, the name of each tool can be configured separately (via https://docs.gradle.org/current/javadoc/org/gradle/nativeplatform/toolchain/GccCommandLineToolConfiguration.html). The Visual C++ tool chain has hardcoded names for each architecture (arm, x86, x86-64, itanium), but this makes it hard to add any other architectures or configure an alternative assembler.

Possible workaround:

Comment by Ante Ilic [ 17/Nov/15 ]

The fix should take into account that the tool being used might be using the unix standard for passing arguments. This is why the workaround didn't work for me as the output file is specified with "-o".

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:46:52 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.