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

Slather is Dependent on `xcode-select` for coverage path #361

Closed
dpfannenstiel opened this issue Jan 2, 2018 · 4 comments

Comments

@dpfannenstiel
Copy link

@dpfannenstiel dpfannenstiel commented Jan 2, 2018

Currently, Slather is dependent on running xcode-select -p to determine the location of the coverage data. This complicates the use of slather in an environment where multiple versions of Xcode are required to support released applications under a long term SLA.

Add a flag -x or --xcode-version to indicated the version of Xcode to use.
Add a flag -p or --coverage-path to specify the path to the Coverage data.

@ksuther

This comment has been minimized.

Copy link
Contributor

@ksuther ksuther commented Jan 2, 2018

You can use the DEVELOPER_DIR environment variable when invoking slather to force it to use a specific version of Xcode. I think that will accomplish what you want.

@dpfannenstiel

This comment has been minimized.

Copy link
Author

@dpfannenstiel dpfannenstiel commented Jan 2, 2018

I'll certainly give that a try, however looking at the code on master I don't find that string literal in a case insensitive search.

Additionally, "BUILD_DIRECTORY" is documented as indicating where the "gcno" files are located. I don't know what that is, but it looks like the use case will also allow the user to set the location of the profile data.

@ksuther

This comment has been minimized.

Copy link
Contributor

@ksuther ksuther commented Jan 2, 2018

DEVELOPER_DIR is part of xcode-select/Xcode, not slather, so that's why you don't see it mentioned.

You can use the build directory argument to point to where your derived data is, if you use a custom build path.

@dpfannenstiel

This comment has been minimized.

Copy link
Author

@dpfannenstiel dpfannenstiel commented Jan 3, 2018

Thanks, that solved my problem. Deeply appreciate the quick responses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.