summaryrefslogtreecommitdiffstats
path: root/content/content.gyp
Commit message (Collapse)AuthorAgeFilesLines
* Move gpu blacklist data file to content side.zmo@google.com2012-09-201-1/+1
| | | | | | | | | | | This also fixes the bug that GPU histograms are missing. BUG=151057 TEST=tree R=jbauman Review URL: https://codereview.chromium.org/10911315 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157851 0039d316-1c4b-4281-b951-d872f2087c98
* Upstreaming SelectFileDialog for Androidaurimas@chromium.org2012-09-181-0/+2
| | | | | | | | | | | | Upstreaming the Select File Dialog and its dependencies needed for Chrome on Android BUG=116131 Review URL: https://chromiumcodereview.appspot.com/10916160 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157424 0039d316-1c4b-4281-b951-d872f2087c98
* Remove {base,net}_java dependencies from GYP client targets on Android.pliard@chromium.org2012-09-101-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | On Android, some GYP client targets were explicitly depending on both the native and Java sides of a library. This removes the dependencies to {base,net}_java and make the native side ('base' and 'net) of these libraries depend on their Java counterpart. On Android it rarely makes sense to depend on a single side of a Java/C++ library. The {base,net}_java can now be considered as "private" targets although GYP does not support this concept unfortunately (AFAICT). Note that I made sure that the resulting APKs' size is unchanged. Additionally, this CL removes 'base_java' (i.e. does not replace it with 'base') from the targets including 'build/apk_test.gypi'. This dependency should not have been there (in the wrong layer) in the first place. It's needed by ChromeNativeTestActivity.java which clients should not know about. BUG=146323 TBR=lipalani,sky,willchan,brettw Review URL: https://chromiumcodereview.appspot.com/10913083 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155737 0039d316-1c4b-4281-b951-d872f2087c98
* Add iOS support to content.gypstuartmorgan@chromium.org2012-09-071-235/+272
| | | | | | | | | | | | | | | | | | | | Conditionalizes targets that don't make sense on iOS, and conditionalizes includes of files that have targets that don't make sense on iOS. The component build targets are not changed, since component builds aren't meaningful on iOS. Fixes gyp style to match the rest of Chromium. This doesn't yet build, due to some webkit/ dependencies that need to be resolved. BUG=None Review URL: https://chromiumcodereview.appspot.com/10914145 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155513 0039d316-1c4b-4281-b951-d872f2087c98
* Make java_aidl targets export include directoriescjhopman@chromium.org2012-08-131-0/+2
| | | | | | | | | | | | | | | | | | | Native code generation rules typically add their output directory to their dependent's 'include_dirs'. This change makes targets that include java_aidl.gypi do a similar thing for other java*.gypi targets. Make java.gypi pass this variable to ant and content.xml use the variable rather than hardcoding the directory. Also, move the aidl output folder into <(SHARED_INTERMEDIATE_DIR) as it should be. BUG= Review URL: https://chromiumcodereview.appspot.com/10855060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151315 0039d316-1c4b-4281-b951-d872f2087c98
* Make java.gypi export jar path to input_jars_paths variablecjhopman@chromium.org2012-08-091-0/+4
| | | | | | | | | | | | | | | | | Both java.gypi and apk_test.gypi expect the jar path in input_jars_paths. This means that we were specifying the dependence in both 'dependencies' and 'input_jars_paths'. This change makes it so that we don't need that redundancy. Also, make java.gypi use input_jars_paths in its input so that we actually rebuild targets when we should. BUG=136756 Review URL: https://chromiumcodereview.appspot.com/10837143 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150850 0039d316-1c4b-4281-b951-d872f2087c98
* Remove "chrome" hardcoded suffix from Android .pak path.tedchoc@chromium.org2012-07-171-0/+1
| | | | | | | | | | BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10778023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147043 0039d316-1c4b-4281-b951-d872f2087c98
* Fix Java file generation rule in java_aidl.gypisteveblock@chromium.org2012-07-101-3/+3
| | | | | | | | | | | | | | | | The Java file generation rule in java_aidl.gypi assumes the wrong output path for the generated file. This leads to spurious rebuilds. The problem is that by default, the aidl tool outputs the Java file to <output-path>/<package-path>/<input-file-root>.java, not to <output-path>/<input-file-root>.java as assumed by the rule. This change fixes the problem by explicitly specifying the output path to aidl. Also remove superfluous path components on input files. Review URL: https://chromiumcodereview.appspot.com/10690092 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145982 0039d316-1c4b-4281-b951-d872f2087c98
* Move java files into src parent directory.navabi@google.com2012-06-261-3/+3
| | | | | | | | | | BUG=134704 TEST= TBR=jam@chromium.org Review URL: https://chromiumcodereview.appspot.com/10668039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@144272 0039d316-1c4b-4281-b951-d872f2087c98
* Enable incremental linking on browser_tests and unit_tests.jam@chromium.org2012-06-221-0/+9
| | | | | | | This is based off scottmg's https://chromiumcodereview.appspot.com/10572043/ and after r143272. Review URL: https://chromiumcodereview.appspot.com/10644003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143501 0039d316-1c4b-4281-b951-d872f2087c98
* Added sandboxed process service.michaelbai@chromium.org2012-06-121-1/+16
| | | | | | | | | | BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10546079 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141618 0039d316-1c4b-4281-b951-d872f2087c98
* Allow for building content_shell from within WebKitjochen@chromium.org2012-05-221-1/+19
| | | | | | | | | BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/10388218 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138231 0039d316-1c4b-4281-b951-d872f2087c98
* Android content shell bringup.jrg@chromium.org2012-05-101-16/+6
| | | | | | | | | | | | | | | | | | Build media java files (we weren't). Fix adb_install_content_shell for cases where the app was stuck. Add upstream staging gyp var / #define. Be more consistent about jar output files (all in lib.java). Upstream a bunch of random files (e.g. ppapi). Upstream a bunch of java and native code hit as part of shlib init. Properly package jar files in content shell. BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10377059 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136219 0039d316-1c4b-4281-b951-d872f2087c98
* Upstream Geolocation for Android.jknotten@chromium.org2012-05-091-0/+16
| | | | | | | | | | TEST=content_unittests: GeolocationProvider.* LocationArbitrator.* There are also some integration tests downstream for the Java specific part. Review URL: https://chromiumcodereview.appspot.com/10209003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@136019 0039d316-1c4b-4281-b951-d872f2087c98
* fix incremental_chrome_dll shared build on windowsdpranke@chromium.org2012-04-251-1/+1
| | | | | | | | | | | | | | | | | | This patch applies patchset #2 from https://chromiumcodereview.appspot.com/10121004/ and then removes the changes to content_switches.cc (which weren't needed) and chrome_exe.gypi (which was not needed and was actually bad because it caused chrome.exe to depend on content.dll ). R=jam@chromium.org, vangelis@chromium.org, rogerta@chromium.org BUG=none TEST=local win build succeeds with incremental_chrome_dll = 1, all bots remain green. Review URL: https://chromiumcodereview.appspot.com/10166021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134008 0039d316-1c4b-4281-b951-d872f2087c98
* Implement the skeleton of an android content shell.tedchoc@chromium.org2012-04-251-0/+13
| | | | | | | | | | | | | Many TODOs here that will allow a quicker distribution of work to get the remaining pieces upstreamed. BUG=118591 TEST= Review URL: http://codereview.chromium.org/10035034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133857 0039d316-1c4b-4281-b951-d872f2087c98
* mac: Make content depend on mach_override in shared buildsthakis@chromium.org2012-03-121-4/+11
| | | | | | | | | | | | mach_override is used by both content and chrome. Since it's small, it's easier to just statically link it into both targets. BUG=90078 TEST=none Review URL: http://codereview.chromium.org/9690001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126103 0039d316-1c4b-4281-b951-d872f2087c98
* Move closure_blocks_leopard_compat to base now that it's used by two modules.jam@chromium.org2012-03-011-64/+0
| | | | | | | BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9549012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124331 0039d316-1c4b-4281-b951-d872f2087c98
* mac: Move the closure_blocks_leopard_compat target out of the component == ↵thakis@chromium.org2012-02-091-63/+64
| | | | | | | | | | | static_library block BUG=90087 TEST=none Review URL: https://chromiumcodereview.appspot.com/9371009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121200 0039d316-1c4b-4281-b951-d872f2087c98
* Fix component buildjam@chromium.org2012-02-041-0/+3
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120442 0039d316-1c4b-4281-b951-d872f2087c98
* Move DOMAutomationController code from chrome to content. This is needed by ↵jam@chromium.org2012-02-031-0/+1
| | | | | | | | | | | interstitial pages which are in content, and also browser tests in content. In followup changes, I'll make interstitial pages not have to derive from a concrete class, and instead implement some sort of delegate interface like we did with WebUI. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9310094 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120441 0039d316-1c4b-4281-b951-d872f2087c98
* remove build_webkit_exes_from_webkit_gyp flagdpranke@chromium.org2012-01-241-5/+1
| | | | | | | | | | R=tony@chromium.org BUG=105823 TEST=everything stays green Review URL: https://chromiumcodereview.appspot.com/9254040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@118774 0039d316-1c4b-4281-b951-d872f2087c98
* Enable content component (again!).dpranke@chromium.org2011-11-161-4/+8
| | | | | | | | | | | This version fixes a problem with the windows incremental linking build. We can't incrementally link chrome when content is being built as a DLL because chrome links in webkit_glue and webkit_glue depends on symbols defined in content. We can remove this when we fix glue. R=jam@chromium.org BUG=90442, 98755. Review URL: http://codereview.chromium.org/8570024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110360 0039d316-1c4b-4281-b951-d872f2087c98
* Add a content_resources target which currently includes the sandbox ↵jochen@chromium.org2011-11-151-1/+4
| | | | | | | | | | | | definitions on mac BUG=90443 TEST=none Review URL: http://codereview.chromium.org/8533023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110115 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 109534 since this change broke clobbered component build.sadrul@chromium.org2011-11-111-5/+2
| | | | | | | | | | | | | | | | Original CL: reenable component build w/ fix to test_support_content TBR=jam@chromium.org BUG=90442 TEST=the win shared debug builder compiles Review URL: http://codereview.chromium.org/8501025 TBR=dpranke@chromium.org Review URL: http://codereview.chromium.org/8538016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109654 0039d316-1c4b-4281-b951-d872f2087c98
* reenable component build w/ fix to test_support_contentdpranke@chromium.org2011-11-101-2/+5
| | | | | | | | | | TBR=jam@chromium.org BUG=90442 TEST=the win shared debug builder compiles Review URL: http://codereview.chromium.org/8501025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109534 0039d316-1c4b-4281-b951-d872f2087c98
* Turn on -Wexit-time-destructors for ui and content.thakis@chromium.org2011-11-091-0/+10
| | | | | | | | | | | | | I had hoped to just turn this on globally after fixing all instances, but people add these fairly often. So enable the warning for clean targets incrementally. BUG=10600 TEST=none TBR=ben Review URL: http://codereview.chromium.org/8495043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109274 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 108976 (broke win shared) - enable component build for contentthakis@chromium.org2011-11-081-5/+2
| | | | | | | | | | | | | R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/8343068 TBR=dpranke@chromium.org Review URL: http://codereview.chromium.org/8496006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108979 0039d316-1c4b-4281-b951-d872f2087c98
* enable component build for contentdpranke@chromium.org2011-11-081-2/+5
| | | | | | | | | | R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/8343068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108976 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 104632 - enable component build for content and appcache.rsleevi@chromium.org2011-10-081-5/+2
| | | | | | | | | | | | | | | | | | | R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/7888053 TBR=dpranke@chromium.org Review URL: http://codereview.chromium.org/8200023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104645 0039d316-1c4b-4281-b951-d872f2087c98
* enable component build for content and appcache.dpranke@chromium.org2011-10-081-2/+5
| | | | | | | | | | R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/7888053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104632 0039d316-1c4b-4281-b951-d872f2087c98
* Here are more exports needed for content_unittests to link in the component ↵dpranke@chromium.org2011-09-301-8/+4
| | | | | | | | | | | | build. R=jam@chromium.org, darin@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/8054037 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103394 0039d316-1c4b-4281-b951-d872f2087c98
* Move Leopard compatible block code to content/.avi@chromium.org2011-09-271-0/+62
| | | | | | | | | BUG=95573 TEST=no change Review URL: http://codereview.chromium.org/8060022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103017 0039d316-1c4b-4281-b951-d872f2087c98
* re-land r100988 (gpy refactoring for content dll).dpranke@chromium.org2011-09-141-9/+168
| | | | | | | | | | 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-168/+9
| | | | | | | | | | 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-9/+168
| | | | | | | | | | | | | | | | | | | 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
* Basic scaffolding for a "content shell", i.e. test browser over the content ↵jam@chromium.org2011-09-121-0/+1
| | | | | | | | | | | module. Once it's working, this will allow developers working on the core chrome code/web platform/networking etc to test their changes on a much smaller and hence faster to build/run/debug browser. This doesn't do anything yet because it's blocked on having TabContentsView implementations in content. BUG=90445 Review URL: http://codereview.chromium.org/7857019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100778 0039d316-1c4b-4281-b951-d872f2087c98
* Use precompiled headers for most large projects where the .gyp filejoi@chromium.org2011-09-071-0/+1
| | | | | | | | | | | | | | is not a third party file. On my machine, this speeds up a full recompile of the 'chrome' target in Debug mode by about 18%. BUG=none TEST=it builds, existing tests pass Review URL: http://codereview.chromium.org/7706011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99949 0039d316-1c4b-4281-b951-d872f2087c98
* Start moving ChromeMain code to content so it can be reused by other ↵jam@chromium.org2011-09-011-0/+1
| | | | | | | | | embedders. I've only moved a little bit of the code for now, and will do the rest in followup changes. BUG=90445 Review URL: http://codereview.chromium.org/7817015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99193 0039d316-1c4b-4281-b951-d872f2087c98
* Add a stub content_unittests target so we can point buildbot to it.phajdan.jr@chromium.org2011-07-261-0/+1
| | | | | | | | BUG=90443 Review URL: http://codereview.chromium.org/7467036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94111 0039d316-1c4b-4281-b951-d872f2087c98
* Move UtilityProcessHost to content and move the message sending/dispatching ↵jam@chromium.org2011-06-091-0/+1
| | | | | | | | | 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
* Move core renderer subdirectories to content.jam@chromium.org2011-03-161-0/+1
| | | | | | | TBR=avi Review URL: http://codereview.chromium.org/6673090 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78422 0039d316-1c4b-4281-b951-d872f2087c98
* Move plugin code to content.jam@chromium.org2011-03-161-0/+1
| | | | | | | TBR=avi Review URL: http://codereview.chromium.org/6672048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78386 0039d316-1c4b-4281-b951-d872f2087c98
* Move ppapi_plugin to content.jam@chromium.org2011-03-141-0/+1
| | | | | | | TBR=brettw Review URL: http://codereview.chromium.org/6679041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78042 0039d316-1c4b-4281-b951-d872f2087c98
* Move worker code from chrome\worker to content\worker.jam@chromium.org2011-03-141-0/+1
| | | | | | | TBR=atwilson Review URL: http://codereview.chromium.org/6691004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78039 0039d316-1c4b-4281-b951-d872f2087c98
* Move chrome\gpu to content\gpu.jam@chromium.org2011-03-121-1/+1
| | | | | | | TBR=avi Review URL: http://codereview.chromium.org/6684015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77903 0039d316-1c4b-4281-b951-d872f2087c98
* Move MessageRouter from chrome to content.jam@chromium.org2011-03-031-0/+1
| | | | | | | TBR=avi Review URL: http://codereview.chromium.org/6603027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76827 0039d316-1c4b-4281-b951-d872f2087c98
* Start moving core pieces of Chrome multi-process code to src\content. I'm ↵jam@chromium.org2011-02-181-0/+13
starting with tab_contents directory.In future changes the headers that include these files will be updated. Once all the files are moved (i.e. renderer_host, rest of browser, renderer etc), then refactoring can begin so that content\DEPS doesn't have chrome in it. Review URL: http://codereview.chromium.org/6537015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@75369 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-12 14:02:31 +0000