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: 159
Popularity: 0.006688
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 .. 103 104 105 106 107 108 109 110 111 112 113 .. 152 Next › Last »

sl1pkn07 commented on 2012-04-12 02:13 (UTC)

@jeagoss http://i.imgur.com/uIMfV.png

jeagoss commented on 2012-04-12 01:23 (UTC)

I have a working PKGBUILD and patches to make chromium compile with pulseaudio. I also commented on your bug thread with the patch. You can download the patches and PKGBUILD from here. http://archrepo.jeago.com/sources/chromium-dev/

<deleted-account> commented on 2012-04-11 14:52 (UTC)

Thanks, as always for the updates! One suggested change to the PKGBUILD: if building with clang and you use plugins, both from and not from the Web Store, clang_use_chrome_plugins=1 will also have to be added to the GYP_DEFINES variable. Was using the clang build earlier, and this was necessary to see my plugins in-browser. AFAIK, this shouldn't cause any problems if you don't use plugins. See [https://code.google.com/p/chromium/wiki/Clang] for more informations.

sl1pkn07 commented on 2012-04-11 00:33 (UTC)

update to 20.0.1096.1 now back 64bit pepperflash!!! now use pkgbuild sugested by @nagisa now pepperflash 32 and 64 bits use same paths /usr/lib/chromium-dev/Pepperflash/libpepflashplayer.so notes for @nagisa - In /etc/makepkg.conf #-- Make Flags: change this for DistCC/SMP systems MAKEFLAGS="-j8" no "need" fast build option. only uncomment and edit makepkg.conf (accoirding you cores) to enable multicore compilation and ${MAKEFLAGS} dont work. use $MAKEFLAGS instead - The disable pulseaudio is for http://crbug.com/119903. i dont know the fail build is related by http://crbug.com/111392 patch. (still fail build with/out patches) - All ffmpeg system libs/ffmpegsumo build is according by http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/chromium/ (make by phajdan.jr , Chromium developer) i comment all build with ffmpeg system libs for use in the future. active now don't have changes in perfomance. - all no common variables warned by namcap. change to: "_<variable>" any other suggestion are welcome greetings and PD: really sorry my english :S

nagisa commented on 2012-04-06 19:37 (UTC)

I made (didn't test it too much tough) new PKGBUILD based on your PKGBUILD. Maybe you want to take some parts from it or even take whole PKGBUILD. https://gist.github.com/7df6bd01b6e5f5d8bc15

<deleted-account> commented on 2012-04-06 14:43 (UTC)

That switch didn't work for me when Pepper Flash first hit this PKGBUILD. I had to point Chromium directly to the file with another switch. It's possible that's a Windows switch, not sure.

misc commented on 2012-04-06 07:38 (UTC)

Well, the only change that commit actually requires (assuming, again, that it's really the only one responsible) is to start Chromium with --enable-bundled-ppapi-flash .

misc commented on 2012-04-06 07:23 (UTC)

Couldn't you just include a patch that reverts http://codereview.chromium.org/9969131/diff/1/chrome_content_client.cc ? Seems like that's the only change responsible for disabling it. Haven't tested it though since I don't use pepper yet. No idea why they did that (and only on 1084), either.

sl1pkn07 commented on 2012-04-06 01:23 (UTC)

http://dl.dropbox.com/u/6596386/google-chrome-unstable-19.0.1084.9-130290.x86_64.rpm for older flash 64

« First ‹ Previous 1 .. 103 104 105 106 107 108 109 110 111 112 113 .. 152 Next › Last »