Re: [webkit-dev] Plugin Troubles with Local Builds vs. Nightly Build Differences

2011-02-11 Thread Alex Milowski
On Thu, Feb 10, 2011 at 3:55 PM, Jon Shier j...@jonshier.com wrote:
 Alex:
        See my bugs here: https://bugs.webkit.org/show_bug.cgi?id=49146
        https://bugs.webkit.org/show_bug.cgi?id=37507

        Basically, updated versions of the required executables aren't part of 
 the open source repository.

 Workaround: Copy the WebKitPluginAgent and WebKitPluginHost to your locally 
 built WebKit.framework from a recent nightly.

Does that work for debugging as well?   Seems like it should ...


-- 
--Alex Milowski
The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered.

Bertrand Russell in a footnote of Principles of Mathematics
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


[webkit-dev] Plugin Troubles with Local Builds vs. Nightly Build Differences

2011-02-10 Thread Alex Milowski
I've been trying to get some plugins to work with a locally built
version of WebKit without much success.  They do work in the nightly
build and so that makes me think that my configuration or build is
somehow different.

I've noticed that when I use Tools/Scripts/run-safari, the plugin is
launched using:

   /System/Library/Frameworks/WebKit.framework/WebKitPluginAgent

instead of my locally build WebKit.framework from my build directory.
In fact, the 'WebKitPluginAgent'
executable isn't there in my locally built version of 'WebKit.framework'.

Also, I would like to build a version of 'WebKit.app' like the nightly
build.  The nightly build works with these plugins.

I was able to run Tools/BuildSlaveSupport/build-launcher-app but that
put the frameworks in the wrong spot and the sparkle framework wasn't
built.  I was able to move things around a bit to get a working app
but plugins still do not work.

Is there a correct sequence of build steps to reproduce what the
nightly build does to build WebKit.app such that WebKitPluginAgent
also gets built (and hopefully plugins work)?

-- 
--Alex Milowski
The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered.

Bertrand Russell in a footnote of Principles of Mathematics
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Plugin Troubles with Local Builds vs. Nightly Build Differences

2011-02-10 Thread Jon Shier
Alex:
See my bugs here: https://bugs.webkit.org/show_bug.cgi?id=49146
https://bugs.webkit.org/show_bug.cgi?id=37507

Basically, updated versions of the required executables aren't part of 
the open source repository.

Workaround: Copy the WebKitPluginAgent and WebKitPluginHost to your locally 
built WebKit.framework from a recent nightly.


Jon


On Feb 10, 2011, at 6:28 PM, Alex Milowski wrote:

 I've been trying to get some plugins to work with a locally built
 version of WebKit without much success.  They do work in the nightly
 build and so that makes me think that my configuration or build is
 somehow different.
 
 I've noticed that when I use Tools/Scripts/run-safari, the plugin is
 launched using:
 
   /System/Library/Frameworks/WebKit.framework/WebKitPluginAgent
 
 instead of my locally build WebKit.framework from my build directory.
 In fact, the 'WebKitPluginAgent'
 executable isn't there in my locally built version of 'WebKit.framework'.
 
 Also, I would like to build a version of 'WebKit.app' like the nightly
 build.  The nightly build works with these plugins.
 
 I was able to run Tools/BuildSlaveSupport/build-launcher-app but that
 put the frameworks in the wrong spot and the sparkle framework wasn't
 built.  I was able to move things around a bit to get a working app
 but plugins still do not work.
 
 Is there a correct sequence of build steps to reproduce what the
 nightly build does to build WebKit.app such that WebKitPluginAgent
 also gets built (and hopefully plugins work)?
 
 -- 
 --Alex Milowski
 The excellence of grammar as a guide is proportional to the paucity of the
 inflexions, i.e. to the degree of analysis effected by the language
 considered.
 
 Bertrand Russell in a footnote of Principles of Mathematics
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Plugin Troubles with Local Builds vs. Nightly Build Differences

2011-02-10 Thread Alex Milowski
On Thu, Feb 10, 2011 at 3:55 PM, Jon Shier j...@jonshier.com wrote:
 Alex:
        See my bugs here: https://bugs.webkit.org/show_bug.cgi?id=49146
        https://bugs.webkit.org/show_bug.cgi?id=37507

        Basically, updated versions of the required executables aren't part of 
 the open source repository.

 Workaround: Copy the WebKitPluginAgent and WebKitPluginHost to your locally 
 built WebKit.framework from a recent nightly.

Great.  The workaround worked!  Thanks!

I've wasted a lot of time tracking this down.  We should really try to
get this updated so a local build works with plugins.

-- 
--Alex Milowski
The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered.

Bertrand Russell in a footnote of Principles of Mathematics
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev