I just checked in r22506, which alters the structure of the
application on disk on the Mac slightly. The entire program has moved
into a dylib (framework) that lives within the app bundle, and the
main executable is now a tiny stub that doesn't do anything but jump
to the entry point in the dylib. I've got more related changes in the
oven, but that's another story...
The only noticeable change now from a development perspective is that
gdb won't be able to find debugging symbols for the dylib when you're
working in release mode. gdb looks for a dSYM bundle next to the
framework, but we don't copy the dSYM into the app bundle (because we
don't want it there). In case you need to debug a release-mode
bundle, you'll need to place a symlink:
cd xcodebuild
ln -fs ../../../Chromium\ Framework.framework.dSYM
Release/Chromium.app/Contents/Frameworks/
Then, when you debug Chromium.app:
gdb Release/Chromium.app
it will be able to load the framework's debugging symbols. I haven't
used the Xcode debugger in a while, but the same symlink should work
to get you on track there as well, since the Xcode debugger is just a
gdb front-end.
Mark
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
