> - The docs around content scripts communicating with the embedding
> page aren't too clear. See e.g.:
> http://code.google.com/chrome/extensions/content_scripts.html#messaging
> That section is mostly just a big example but for example nowhere is
> the postMessage API described. I'd prefer it
I punted the WebKitAPI related tasks since they don't block M4.
-Darin
On Sat, Oct 31, 2009 at 7:56 PM, Dimitri Glazkov wrote:
>
> The moon is high. The zombies, wizards and various other bizarre
> beings are prowling the streets. Which could mean only one thing:
> Tombstone 4 is coming to get us
>
> 1) Do you support multiple inheritance? I notice the "inherit_from" is
> specified as an array. That's scaryish.
>
Multiple inheritance is supported, not sure it's wise to use, but well gyp
has lots of features like that :-)
I almost didn't support it, but concluded that, for instance 64-bi
I'm sure that there are better examples than the below. Presumably if
you want something defined in both Debug and Release, you want it
globally, and you'd be better off specifying it outside of the
configuration altogether.
Brad, we can still inherit from non-abstract configurations, right?
Thi
>
>
> Brad, we can still inherit from non-abstract configurations, right?
> This might be useful...
>
yes, we can, and it would
> Mark
>
> Bradley Nelson wrote:
> > configurations can now inherit from one or more other configurations, and
> > configurations which are not fully expressed should b
Hi,
when building after syncing, I now get
/Users/thakis/src/chrome-git/src/chrome/../xcodebuild/chrome.build/Debug/chrome.build/Script-649B47660F26D59AE4D7EEA0.sh:
line 2: BUILT_PRODUCTS_DIR: command not found
every time. If you get this too, it can be fixed by going to
Targets->Chrome->P
Oops.
http://codereview.chromium.org/353002
Nico Weber wrote:
> Hi,
>
> when building after syncing, I now get
>
>
> /Users/thakis/src/chrome-git/src/chrome/../xcodebuild/chrome.build/Debug/chrome.build/Script-649B47660F26D59AE4D7EEA0.sh:
> line 2: BUILT_PRODUCTS_DIR: command not found
>
> e
Greetings Chromium-developers,
(Please ignore this e-mail when you are not building Chromium with gcc 4.4.)
Today, a person reported gcc 4.4 yields the following build errors
while building Chromium on IRC:
"cc1plus: error: dereferencing pointer '...' does break strict-aliasing rules"
Unfortun
Hi all,
2009/11/2 Hironori Bono (坊野 博典)
>
> 1. Creating a file "~/.gyp/inclulde.gypi'.
> 2. Adding a following lines to the file.
>
> {
>'variables': {
> 'no_strict_aliasing': 1
>}
> }
>
>
IIRC specifying 'gcc_version': '44' does the same thing as above. This might
be better than
2009/11/2 Yuta Kitamura :
> IIRC specifying 'gcc_version': '44' does the same thing as above. This might
> be better than specifying 'no_strict_aliasing' directly.
Ah, you bet me to it. You're right; gcc_version is used to only
enable -fno-strict-aliasing when building v8.
Joel
--~--~
10 matches
Mail list logo
