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
Failed to create temporary outfile 'XXXX.tmp%%%%%%.dwarf': No such file or directory #929
Comments
+1 |
This is an issue from Here is the comment documentation for the problematic function
I submitted a bug over at LLVM, although fixes there wouldn't show up in Xcode for months if ever, AFAIK. |
Interesting. Thanks |
Is there any workaround for this issue? This is particularly painful when having an Xcode Bot for a project with a space in it's name. It creates a folder in the format "folder%20name" and then the carthage pre-intergration script fails. :( |
This still seems to be bug, and since it's an llvm issue, I doubt it's something that will be fixed quickly. @NickSkull, in regards to the Xcode Bot, I made my Before trigger to look like the following. It's a bit of a hack, but it will get you there. Assuming your project is named "Foo Bar": #!/bin/bash
if [ -d FooBar ]; then
rm -rf FooBar
fi
mv Foo%20Bar FooBar
pushd FooBar
/usr/local/bin/carthage bootstrap --platform iOS
popd
mv FooBar Foo%20Bar The script just temporarily moves the folder to a name without the "%", does the carthage update and then moves it back. |
This occurs when running Carthage in a directory with a % in its name.
First if I run the project cloned into a folder named "Project Name" it will work fine
The same project cloned into a folder called "project%20name" produces the following output
Background
This bug was found while using a Jenkins server with the multi branch project plugin and a git flow esque workflow. The problem is that git-flow names branches as "feature/featureName" or "release/versionNumber" which the multi-branch plugin converts to folders called "feature%2FfeatureName" and "release%2FversionNumber" respectively.
The text was updated successfully, but these errors were encountered: