Package Details: chromium-dev 126.0.6423.2-1

Git Clone URL: https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL: http://www.chromium.org
Keywords: browser web
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 160
Popularity: 0.019686
First Submitted: 2010-05-17 09:04 (UTC)
Last Updated: 2024-04-21 19:18 (UTC)

Required by (0)

Sources (13)

Latest Comments

« First ‹ Previous 1 .. 41 42 43 44 45 46 47 48 49 50 51 .. 152 Next › Last »

axfelix commented on 2015-12-06 20:47 (UTC)

@skzzorz thanks for finding that link -- looks like it is indeed explicitly disabled on mesa.

sflor commented on 2015-12-01 17:15 (UTC)

Does anybody know if there's a binary build with GTK3 support?

sl1pkn07 commented on 2015-11-12 17:50 (UTC)

nope, chromium-dev still need bundled libvpx (it needs headers not included in libvpx 1.5) 'vpx/vpx_codec_impl_bottom.h', 'vpx/vpx_codec_impl_top.h', greetings

prazola commented on 2015-11-12 14:57 (UTC)

Does 48.0.2560.0-1 build support libvpx 1.5?

prazola commented on 2015-11-10 16:21 (UTC)

Wow, latest nightly builds are a bit to heavy :D https://download-chromium.appspot.com/dl/Linux_x64 The executable reach 2gb when uncompressed. Do they have some build problem?

skzzorz commented on 2015-11-08 01:36 (UTC)

@axfelix a qucik search at cs.chromium.org leads to: https://code.google.com/p/chromium/codesearch#chromium/src/content/browser/gpu/browser_gpu_memory_buffer_manager.cc&sq=package:chromium&l=102&rcl=1446928296 it doesn't look like it's disabled by OS-related macro.

axfelix commented on 2015-11-05 22:04 (UTC)

I'm noticing that the --enable-native-gpu-memory-buffers flag doesn't seem to be working on Linux in newest chromium-dev despite the fact that this functionality *should* now be there; is it possible that this is blacklisted at compile time on non-ChromeOS platforms the way that vaapi was? Might be fun to have a look into that...

axfelix commented on 2015-11-03 23:52 (UTC)

Thanks!

skzzorz commented on 2015-10-29 09:59 (UTC)

@quartz55 @axfelix Pre-compiled builds for x86-64 with VA-API patch can be found at archlinuxcn's unofficial community repo at repo.archlinuxcn.org

ethail commented on 2015-10-27 11:46 (UTC) (edited on 2015-10-27 21:59 (UTC) by ethail)

Looking at the post on the chrome releases blog [0] for this release, shouldn't we be using 48.0.2541.0 instead of 48.0.2540.0? Not that it matters that much, as a release should happen shortly, I guess, but maybe for a future we could pay a little more attention when two versions targeted at diferent OSes are released. [0] http://googlechromereleases.blogspot.com.es/2015/10/dev-channel-update_20.html EDIT (a few hours later): I realized my tone could get misinterpreted, by "we" I mean everyone who uses this package and cares even a little about it, not just the maintainer.

« First ‹ Previous 1 .. 41 42 43 44 45 46 47 48 49 50 51 .. 152 Next › Last »