summaryrefslogtreecommitdiffstats
path: root/content/content_utility.gypi
Commit message (Collapse)AuthorAgeFilesLines
* Mojo: split up service_provider.mojomdarin@chromium.org2014-07-311-1/+1
| | | | | | Review URL: https://codereview.chromium.org/423613002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@286725 0039d316-1c4b-4281-b951-d872f2087c98
* Extract mojo_base.gyp from mojo.gypmorrita@chromium.org2014-07-301-1/+1
| | | | | | | | | | | | | | | | | | | | This change extract essential part of Mojo, which is needed to build chrome and its submodules, to mojo_base.gyp. Other chrome submodules can safely depends on mojo_base.gyp without worrying about excessive dependencies behind. Caveat: mojo_service_manager stays on mojo.gyp even though it is required to build chrome. This change leaves it as it depends on net.gyp, which has non trivial dependencies. BUG=397672 TEST=none R=jamesr@chromium.org, viettrungluu@chromium.org, rockot@chromium.org TBR=darin@chromium.org Review URL: https://codereview.chromium.org/422163004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@286627 0039d316-1c4b-4281-b951-d872f2087c98
* Mojo: Remove InterfaceProvider.sammc@chromium.org2014-06-301-1/+1
| | | | | | Review URL: https://codereview.chromium.org/358743002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@280569 0039d316-1c4b-4281-b951-d872f2087c98
* Support exposing Mojo services between render frames, render threads, and ↵sammc@chromium.org2014-06-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | their respective hosts. This introduces ServiceRegistry as an abstraction around providing services to and accessing services from a remote peer. In particular, this adds peered service registries to RenderProcessHost and RenderThread, and to RenderFrameHost and RenderFrame - the RenderFrame setup is implemented using the RenderProcessHost/RenderThread ServiceRegistry pair. This replaces the existing WebUI handle setup by adding a webUI controller service to the frame host registry and a corresponding request for the webUI controller service to the frame registry. BUG=386155 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=279557 Review URL: https://codereview.chromium.org/285333003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@279623 0039d316-1c4b-4281-b951-d872f2087c98
* Shell / ShellClient -> ServiceProviderdavemoore@chromium.org2014-05-271-1/+1
| | | | | | | | | | | Try #2 of https://codereview.chromium.org/298653010/ Fixed newly introduced GN dependency. TBR=darin@chromium.org BUG= Review URL: https://codereview.chromium.org/298003008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272989 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 272983 "Change Shell / ShellClient to ServiceProvider"davemoore@chromium.org2014-05-271-1/+1
| | | | | | | | | | | | | | | > Change Shell / ShellClient to ServiceProvider > > BUG= > R=darin@chromium.org > > Review URL: https://codereview.chromium.org/298653010 TBR=davemoore@chromium.org Review URL: https://codereview.chromium.org/304593002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272984 0039d316-1c4b-4281-b951-d872f2087c98
* Change Shell / ShellClient to ServiceProviderdavemoore@chromium.org2014-05-271-1/+1
| | | | | | | | | BUG= R=darin@chromium.org Review URL: https://codereview.chromium.org/298653010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272983 0039d316-1c4b-4281-b951-d872f2087c98
* Move Mojo channel initialization closer to IPC::Channel setupdarin@chromium.org2014-04-241-0/+1
| | | | | | | | | | | | | | | | | | | This CL introduces two new content classes: - MojoApplicationHost encapsulates what's needed to host a Mojo App using Chrome IPC to bootstrap. - MojoApplication represents what's needed to be a Mojo App using Chrome IPC to bootstrap. The RenderProcess and RenderProcessHost interfaces are replaced with WebUISetup and WebUISetupClient interfaces. This way the interface is more specific to the service of setting up WebUI. WebUISetupClient is empty and uninteresting. RenderProcessHostImpl no longer deals with WebUI setup. That is all done directly by RenderViewHostImpl by talking to the WebUISetup service. Service names get defined in content/common/mojo/mojo_service_names.{h,cc}. TBR=sky@chromium.org, tsepez@chromium.org Originally reviewed at https://codereview.chromium.org/236813002/ Review URL: https://codereview.chromium.org/256403004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265962 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 265693 "Move Mojo channel initialization closer to IPC::C..."brianderson@chromium.org2014-04-231-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | This is causing runhooks failures on the iOS build bots. > Move Mojo channel initialization closer to IPC::Channel setup > > This CL introduces two new content classes: > - MojoApplicationHost encapsulates what's needed to host a Mojo App using Chrome IPC to bootstrap. > - MojoApplication represents what's needed to be a Mojo App using Chrome IPC to bootstrap. > > The RenderProcess and RenderProcessHost interfaces are replaced with WebUISetup and WebUISetupClient interfaces. This way the interface is more specific to the service of setting up WebUI. > > WebUISetupClient is empty and uninteresting. RenderProcessHostImpl no longer deals with WebUI setup. That is all done directly by RenderViewHostImpl by talking to the WebUISetup service. > > Service names get defined in content/common/mojo/mojo_service_names.{h,cc}. > > R=sky@chromium.org, tsepez@chromium.org > > Review URL: https://codereview.chromium.org/236813002 TBR=darin@chromium.org Review URL: https://codereview.chromium.org/247953005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265705 0039d316-1c4b-4281-b951-d872f2087c98
* Move Mojo channel initialization closer to IPC::Channel setupdarin@chromium.org2014-04-231-0/+1
| | | | | | | | | | | | | | | | | | This CL introduces two new content classes: - MojoApplicationHost encapsulates what's needed to host a Mojo App using Chrome IPC to bootstrap. - MojoApplication represents what's needed to be a Mojo App using Chrome IPC to bootstrap. The RenderProcess and RenderProcessHost interfaces are replaced with WebUISetup and WebUISetupClient interfaces. This way the interface is more specific to the service of setting up WebUI. WebUISetupClient is empty and uninteresting. RenderProcessHostImpl no longer deals with WebUI setup. That is all done directly by RenderViewHostImpl by talking to the WebUISetup service. Service names get defined in content/common/mojo/mojo_service_names.{h,cc}. R=sky@chromium.org, tsepez@chromium.org Review URL: https://codereview.chromium.org/236813002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265693 0039d316-1c4b-4281-b951-d872f2087c98
* Use UtilityProcessHost to patch files.waffles@chromium.org2014-03-281-0/+1
| | | | | | | | | | | | | Second part of a 2-part changelist. The first part is https://codereview.chromium.org/25883006/ BUG=304879 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=259726 Review URL: https://codereview.chromium.org/25909005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@260243 0039d316-1c4b-4281-b951-d872f2087c98
* Revert of Use UtilityProcessHost to patch files. ↵erikchen@chromium.org2014-03-261-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (https://codereview.chromium.org/25909005/) Reason for revert: linux asan failure http://build.chromium.org/p/chromium.memory/builders/Linux%20ASan%2BLSan%20Tests%20%282%29/builds/901/steps/unit_tests/logs/DifferentialUpdateFails Original issue's description: > Use UtilityProcessHost to patch files. > > Second part of a 2-part changelist. > The first part is https://codereview.chromium.org/25883006/ > > BUG=304879 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=259726 TBR=sorin@chromium.org,dgarrett@chromium.org,sky@chromium.org,cdn@chromium.org,waffles@chromium.org NOTREECHECKS=true NOTRY=true BUG=304879 Review URL: https://codereview.chromium.org/213923002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@259740 0039d316-1c4b-4281-b951-d872f2087c98
* Use UtilityProcessHost to patch files.waffles@chromium.org2014-03-261-0/+1
| | | | | | | | | | | Second part of a 2-part changelist. The first part is https://codereview.chromium.org/25883006/ BUG=304879 Review URL: https://codereview.chromium.org/25909005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@259726 0039d316-1c4b-4281-b951-d872f2087c98
* Fix names of in-process threads, tidy gpu DEPSscottmg@chromium.org2013-09-041-2/+2
| | | | | | | | | | | | Follow-up after http://crrev.com/217968 per comments on https://chromiumcodereview.appspot.com/23235002/ R=jam@chromium.org BUG=237249 Review URL: https://chromiumcodereview.appspot.com/23452016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221199 0039d316-1c4b-4281-b951-d872f2087c98
* Set up content in-process main threads via factoryscottmg@chromium.org2013-08-161-0/+2
| | | | | | | | | | | | | | | | | | | | | | This code was previously #ifdef'd out based on CHROME_MULTIPLE_DLL. This works for chrome, but not for test targets which link content_browser. content_browser needs to not link against child-only targets (as they'll cause linking blink into the browser dll). Instead of having utility_process_host_impl, et al. own the in-process implementation, use a factory to create them that's installed in test code, and in chrome for supporting --single-process. At the same time, remove the global CHROME_MULTIPLE_DLL define and localize it to chrome_exe.gypi because it's too easy to use incorrectly. TBR=darin R=piman@chromium.org,jam@chromium.org BUG=237249 Review URL: https://chromiumcodereview.appspot.com/23235002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217968 0039d316-1c4b-4281-b951-d872f2087c98
* Create default implementations of ContentRendererClient, ↵jam@chromium.org2012-05-301-0/+1
| | | | | | | | | ContentUtilityClient, and ContentPluginClient to make it easier to embed content. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/10449063 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139432 0039d316-1c4b-4281-b951-d872f2087c98
* Load mac sandbox definitions from resources instead of the bundle.jochen@chromium.org2011-11-251-9/+0
| | | | | | | | | | | Also, move all mac sandbox unittests to content BUG=90443 TEST=content_unittests Review URL: http://codereview.chromium.org/8589001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111614 0039d316-1c4b-4281-b951-d872f2087c98
* Create content::UtilityThread interface and make chrome code use that. This ↵ananta@chromium.org2011-10-141-2/+4
| | | | | | | | | | | | | | | | interface is implemented by the UtilityThreadImpl class in content\utility\utility_thread_impl.cc/.h which are renamed incarnations of the content\utility\utility_thread.cc/.h files. Changes as part of creating a content API. BUG=98716 TEST=No change in functionality. Review URL: http://codereview.chromium.org/8276026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105610 0039d316-1c4b-4281-b951-d872f2087c98
* Move content_utility_client.h to content\public\utility.ananta@chromium.org2011-10-131-1/+1
| | | | | | | | | | Changes as part of creating a Content API. BUG=98716 TEST=No change in functionality. Review URL: http://codereview.chromium.org/8252005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105398 0039d316-1c4b-4281-b951-d872f2087c98
* fix indentation in content_*.gypi.dpranke@chromium.org2011-09-261-22/+21
| | | | | | | | | | | | | This is a whitespace-only change to clean up from the refactoring of a couple weeks ago for the component build. R=jam@chromium.org BUG=90442 TEST=none Review URL: http://codereview.chromium.org/8046015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102800 0039d316-1c4b-4281-b951-d872f2087c98
* re-land r100988 (gpy refactoring for content dll).dpranke@chromium.org2011-09-141-7/+1
| | | | | | | | | | TBR=darin BUG= TEST= Review URL: http://codereview.chromium.org/7889027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101011 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r100988 (gpy refactoring for content dll).dpranke@chromium.org2011-09-141-1/+7
| | | | | | | | | | TBR=darin BUG= TEST= Review URL: http://codereview.chromium.org/7892021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100996 0039d316-1c4b-4281-b951-d872f2087c98
* This change merges all of the content code into a single library; the ↵dpranke@chromium.org2011-09-131-7/+1
| | | | | | | | | | | | | | | | | | | contents of the library are pulled from individual gypis that are now just collections of settings. There are three changes here ... 1) Move omx_video_decode_unittest into content_tests.gypi, and move a couple of other definitions into the top level content.gyp 2) Change all of the dependencies in the chrome gypi's from content_browser et al. to just "content" 3) Remove the "targets", "target_name", and "target_type" keys from the content_* gypis This change depends on http://codereview.chromium.org/7697008/ landing first to ensure we have the right dependencies set for content. BUG=90442 TEST=everything still compiles and links Review URL: http://codereview.chromium.org/7618029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100988 0039d316-1c4b-4281-b951-d872f2087c98
* Make all content client interfaces pure virtual.joi@chromium.org2011-06-291-1/+0
| | | | | | | | | BUG=87332 TEST=existing Review URL: http://codereview.chromium.org/7242016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90910 0039d316-1c4b-4281-b951-d872f2087c98
* Move UtilityProcessHost to content and move the message sending/dispatching ↵jam@chromium.org2011-06-091-0/+35
to the clients. This allows the content layer to use the class. BUG=76697 Review URL: http://codereview.chromium.org/6995095 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@88586 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-01 02:30:48 +0000