Great work on the bundle so far... though I'm currently having trouble running the executable. When choosing Build & Run or just Run, I get the following error:
/Library/Application Support/TextMate/Bundles/Xcode.tmbundle/Support/ bin/run_xcode_target.rb:175:in `run': undefined local variable or method `file' for # (NameError) from /Library/Application Support/ TextMate/Bundles/Xcode.tmbundle/Support/bin/run_xcode_target.rb: 193:in `run' from /Library/Application Support/TextMate/Bundles/ Xcode.tmbundle/Support/bin/parse_build.rb:202 from /Library/ Application Support/TextMate/Bundles/Xcode.tmbundle/Support/bin/ format_build.rb:559
Well I figured out that it's the variable name used to name the terminal window. The script uses {#file}. I replaced that with {#escaped_file} and it launchs the terminal window. But then I get an error that reports that it can't find the build. It's looking in a Release directory, but my build is a Debug build.
On Nov 17, 2006, at 10:23 AM, Michael Gregoire wrote:
Great work on the bundle so far... though I'm currently having trouble running the executable. When choosing Build & Run or just Run, I get the following error:
/Library/Application Support/TextMate/Bundles/Xcode.tmbundle/ Support/bin/run_xcode_target.rb:175:in `run': undefined local variable or method `file' for # (NameError) from /Library/ Application Support/TextMate/Bundles/Xcode.tmbundle/Support/bin/ run_xcode_target.rb:193:in `run' from /Library/Application Support/ TextMate/Bundles/Xcode.tmbundle/Support/bin/parse_build.rb:202 from /Library/Application Support/TextMate/Bundles/Xcode.tmbundle/ Support/bin/format_build.rb:559
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
The script uses {#file}. I replaced that with {#escaped_file} and it launchs the terminal window
Thanks for the report; broken in my checkins to add console output. Now fixed.
But then I get an error that reports that it can't find the build. It's looking in a Release directory, but my build is a Debug build.
This should actually work if it did in the past, since that section of the code hasn't really changed. It does work here.
The point of failure is in Xcode::Project#active_configuration_name; I'll try to look at this more later tonight. (If we can't find a user- specified configuration, we use 'Release' -- even if there isn't a 'Release' target. We should at least default to a target known to exist in the project file.)
Chris
On 17. Nov 2006, at 22:53, Chris Thomas wrote:
But then I get an error that reports that it can't find the build. It's looking in a Release directory, but my build is a Debug build.
This should actually work if it did in the past, since that section of the code hasn't really changed. It does work here.
The point of failure is in Xcode::Project#active_configuration_name; I'll try to look at this more later tonight. (If we can't find a user-specified configuration, we use 'Release' -- even if there isn't a 'Release' target. We should at least default to a target known to exist in the project file.)
I think this has always been a problem, but it’s one of those things affected by several parameters and hardcoded default values.
Try Xcode → New Project then Build & Run, I get the “Not found”- problem, currently it does not show the path used, but it used to say Release/… in the past.
Now open the project in Xcode, close it, and try Build & Run again, and it works.
On Nov 17, 2006, at 5:20 PM, Allan Odgaard wrote:
On 17. Nov 2006, at 22:53, Chris Thomas wrote:
But then I get an error that reports that it can't find the build. It's looking in a Release directory, but my build is a Debug build.
This should actually work if it did in the past, since that section of the code hasn't really changed. It does work here.
The point of failure is in Xcode::Project#active_configuration_name; I'll try to look at this more later tonight. (If we can't find a user-specified configuration, we use 'Release' -- even if there isn't a 'Release' target. We should at least default to a target known to exist in the project file.)
I think this has always been a problem, but it’s one of those things affected by several parameters and hardcoded default values.
Try Xcode → New Project then Build & Run, I get the “Not found”- problem, currently it does not show the path used, but it used to say Release/… in the past.
I did that and it worked immediately. :) Lots of complexity in Xcode's build/user config, obviously...
Chris
-
Allan Odgaard -
Chris Thomas -
Michael Gregoire