summaryrefslogtreecommitdiffstats
path: root/base
diff options
context:
space:
mode:
authormark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-01 16:55:59 +0000
committermark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-01 16:55:59 +0000
commita9b1f17f3ba502396dbc41d42a795d6672f8b750 (patch)
tree566f7e7212edfef1a1c05f2b3ec34c3a3c9631f8 /base
parent8d66f419e531fc1362b698769e7bd0cee31bd874 (diff)
downloadchromium_src-a9b1f17f3ba502396dbc41d42a795d6672f8b750.zip
chromium_src-a9b1f17f3ba502396dbc41d42a795d6672f8b750.tar.gz
chromium_src-a9b1f17f3ba502396dbc41d42a795d6672f8b750.tar.bz2
Fix Breakpad-enabled builds on the Mac.
.../src/chrome/app/breakpad_mac.mm: In function ‘void InitCrashReporter()’: .../src/chrome/app/breakpad_mac.mm:56: error: ‘parsed_command_line’ was not declared in this scope IMPORTANT NOTE: When you're making changes to files that aren't part of the normal build, you MUST test them. The next time I see an obvious case of "oops, I never actually built that file," I'm just going to back it out. As for this instance, I'm fixing it now, but you MUST build and test your change locally. We can't afford accidentally losing Breakpad coverage. I've already seen an embarrassing number of instances of "oops, Breakpad's broken" but we've fortunately caught them all before integrating them into a release. BUG=It doesn't build TEST=Does it build now? Review URL: http://codereview.chromium.org/178056 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25041 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
-rw-r--r--base/mac_util.mm3
1 files changed, 1 insertions, 2 deletions
diff --git a/base/mac_util.mm b/base/mac_util.mm
index b2e9b6e..dcfb6470 100644
--- a/base/mac_util.mm
+++ b/base/mac_util.mm
@@ -46,8 +46,7 @@ bool AmIBundled() {
bool IsBackgroundOnlyProcess() {
NSBundle* main_bundle = MainAppBundle();
NSDictionary* info_dictionary = [main_bundle infoDictionary];
- return [[info_dictionary objectForKey:@"LSUIElement"]
- isEqualToString:@"1"] ? true : false;
+ return [[info_dictionary objectForKey:@"LSUIElement"] boolValue] != NO;
}
// No threading worries since NSBundle isn't thread safe.