AUR (en) - chromium-dev

Search Criteria

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.010897
First Submitted:	2010-05-17 09:04 (UTC)
Last Updated:	2024-04-21 19:18 (UTC)

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.010897

First Submitted:

2010-05-17 09:04 (UTC)

Last Updated:

2024-04-21 19:18 (UTC)

Latest Comments

« First ‹ Previous 1 .. 106 107 108 109 110 111 112 113 114 115 116 .. 152 Next › Last »

sl1pkn07 commented on 2012-03-16 18:41 (UTC)

@Nagisa oks. now disable (with comment) all references to build/install system FFmpeg library.

nagisa commented on 2012-03-16 18:27 (UTC)

You should also add a note near "compile with system ffmpeg" option that compiling with system ffmpeg currently fails and you can remove patch_for_ffmpeg-git.patch as it doesn't work anyway.

sl1pkn07 commented on 2012-03-16 18:23 (UTC)

:D thanks for this report! (need more of this). updated and added lib32-gcc-libs makedepend (if nacl is acctived) greetings and little cosmetics

<deleted-account> commented on 2012-03-16 16:01 (UTC)

Great work on getting all of this PKGBUILD fun worked out! I've been until now unable to compile Nacl, even with safe CFLAGS (took out the stack-smashing protection flags manually). Was receiving fatal errors that some gcc library files were missing. lib32-gcc-libs needs to be a dependency for 64-bit users if building Nacl, it seems.

sl1pkn07 commented on 2012-03-16 15:23 (UTC)

do'h fixed

jeagoss commented on 2012-03-16 12:56 (UTC)

On line 344 of the PKGBUILD, you need to change the first ${pkgdir} to ${srcdir}. This change allows for full compilation on i686. OLD: install -m775 "${pkgdir}"/opt/google/chrome/libgcflashplayer.so "${pkgdir}"/usr/lib/chromium-dev/libgcflashplayer.so NEW: install -m775 "${srcdir}"/opt/google/chrome/libgcflashplayer.so "${pkgdir}"/usr/lib/chromium-dev/libgcflashplayer.so

sl1pkn07 commented on 2012-03-16 12:19 (UTC)

@jeagoss try now (update pkgbuild) in 32bits, the PapperFlash library is named "libgcflashplayer.so". now install in /usr/lib/chromium-dev/libgcflashplayer.so (if detect 32bits) (like a RPM package) @imhumn edit /etc/chromium-dev/default and add "--ppapi-flash-path=/usr/lib/chromium-dev/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.2.31.114" in CHROMIUM_FLAGS (--enable-greasemonkey --enable-sync not need) i think fixed now in chromium-dev.install script. @all new pkgbuild enable compile "chromiumdrive" (chromedrive). for new major updates include it for default please test it greetings

jeagoss commented on 2012-03-16 10:15 (UTC)

It appears that the i386 versions of chrome do not actually include the pepperflash directory opt/google/chrome/PepperFlash in the rpm archive. I also checked the i386 versions of the deb's that are available, and the same seems to be true. Due to i386 not including the plugin, it causes the build to fail. I'm not sure if google is maintaining an i386 version of the plugin or not. I've been trying to figure this out. Until you can find a reliable source for the plugin, you might consider disabling the install on i686 architectures.

<deleted-account> commented on 2012-03-16 02:35 (UTC)

Nope. The CHROMIUM_FLAGS entry in /etc/chromium-dev/default is empty.