Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to specify which target to use when building the project. #4387

Closed
photex opened this issue Sep 13, 2019 · 3 comments
Closed

Unable to specify which target to use when building the project. #4387

photex opened this issue Sep 13, 2019 · 3 comments
Assignees
Labels
answered Issues that have an answer and don't require additional action from maintainers

Comments

@photex
Copy link

photex commented Sep 13, 2019

Environment

  • 0.2.105.2133-192
  • 1.37.0
  • CLion 2019.2.1
  • Windows 10

Problem description

I'd like to be able to configure which target is built when building the project. Currently there is no option to control this.
It may not seem like much, but when you have a large build, you end up with an enormous amount of disk space wasted.

@mchernyavsky mchernyavsky self-assigned this Sep 13, 2019
@mchernyavsky
Copy link
Member

See this comment: #4386 (comment)

@photex
Copy link
Author

photex commented Sep 13, 2019

Sorry, as I mentioned in the other issue I keep mixing terms.

Here I'm not talking about which 'project' to build.

I have a workspace with a bunch of 'projects' and I build for multiple 'targets'. I don't see a way to specify the target triple to build with:

I build for many target triples:

  • x86_64-unknown-linux-gnu
  • aarch64-unknown-linux-gnu
  • x86_64-pc-windows-msvc
  • x86_64-pc-windows-gnu
  • x86_64-unknown-linux-musl
  • aarch64-unknown-linux-musl

I personally never want the 'default'.

@photex
Copy link
Author

photex commented Sep 13, 2019

And so cool, that the new build window actually supports all that correctly! :D

@mchernyavsky mchernyavsky added the answered Issues that have an answer and don't require additional action from maintainers label Sep 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered Issues that have an answer and don't require additional action from maintainers
Projects
None yet
Development

No branches or pull requests

2 participants