project.pbxproj output file name gideros

#Project.pbxproj output file name gideros pdf#

The Output Folders (the folder for the individual outputs) are named from the designer-defined Name of each Job.

The Containing Folder (the folder for all outputs from the Jobs allocated to the output container currently being configured) is named from the Variant that is being used to generate the outputs, in this example Model.4G.

The outputs are stored in a manually named folder called Output.

Note that in the following image the output and folder naming works as follows: The Expression-based output name is specified in the Settings dialog for the chosen output, click the Changelink for the Output Container to configure this. Click the Change link to define the Output name. The image below shows which elements can be used, refer to the Supported Special Strings table below for more details.Įlements from the Output can be used in the expression-based output name, including 1-OutputName, 2-DataSource and 3-VariantName.

#Project.pbxproj output file name gideros pdf#

Specifying Expression-based Output Names and Folder NamesĮxpression-based output names and folder names are defined in Output Job files, for both PDF and Folder Structure type outputs.Ĭertain elements from the Output in the Outjob can be used in the output name, such as the current name of this Output, and the Variant Name.

If you can provide an rspec test that exposes this specific bug, then I'd be happy to reopen the issue.Note that the PDF file extension is automatically added during file generation, if it is not manually defined. Your issue sounds similar to #47 and I wouldn't be surprised if your coverage files have just been specially configured to go elsewhere, in which case you'll need to specify that location to Slather. gcno underneath the tree /Library/Developer/Xcode/DerivedData, the default location for coverage files generated by Xcode. This means that Slather couldn't find any. Are you sure your project is setup for generating coverage files? Try slather setup your/project.pbxproj If you look at the exception that was raised, it says

Issues have been opened up (and closed) on Synx regarding this in the past (ie, venmo/synx#42 (comment)), but these issues belong on the xcodeproj repo.Īs for the stack trace, this is a specific exception case that Synx looks for.

This is a product of the way that the xcodeproj gem works, which also powers gems like Synx and Cocoapods. So, Slather didn't break the pbxproj file - as you said, it just rewrote it as XML. So afaik, the setup function of slather is not working right now and should be fixed ASAP as slather is more or less not useable in comparison with Travis CI (only with a customised setup). The project I was looking into is the XNGAPIClient, which had their last successful measurement in mid December (see this build Travis CI Coveralls.io).Īs it's definitely not the difference between XCode 6.1 and XCode 6.1.1 (tried that), I tried to add these flags manually and slather started to work. Are you sure your project is setup for generating coverage files? Try `slather setup your/project.pbxproj` (StandardError)įrom /Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/lib/slather/coverage_service/simple_output.rb:13:in `post'įrom /Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/bin/slather:64:in `post'įrom /Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/bin/slather:36:in `execute'įrom /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'įrom /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11:in `execute'įrom /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp/command.rb:125:in `run'įrom /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp.rb:6:in `Clamp'įrom /Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/bin/slather:6:in `'įrom /Users/florian/.rvm/gems/ruby-2.2.0/bin/slather:23:in `load'įrom /Users/florian/.rvm/gems/ruby-2.2.0/bin/slather:23:in `'įrom /Users/florian/.rvm/gems/ruby-2.2.0/bin/ruby_executable_hooks:15:in `eval'įrom /Users/florian/.rvm/gems/ruby-2.2.0/bin/ruby_executable_hooks:15:in `'Īfter investigating into this for several hours, I found another 'example' project which is using Slather + Coveralls.io and their slather support is broken as well. Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/lib/slather/project.rb:49:in `coverage_files': No coverage files found.