Compiling unjewgled chromium

youtube.com/watch?v=R_fQ6Quv-4E

How long did it take?

how do we know that you're not a jew yourself?

a r c h the way i found out is, there was tearing in 'fs' which means it wasn't rly fs but windowed

long, trust me

HOW LONG?

It takes my computer like 2 to 3 hours.

at least 6 hours on x220 with -j3

that's long

why didn't you just get ftp.mozilla.org?

because I want unjewgled

UNMOZZJEWLA WHEN?

what do you mean it doesn't really go in fs?

...

Isn't that normal (and preferred) for mpv to use windowed fullscreen, not take over the whole display fullscreen?

>Isn't that normal
no
and mpv was just an example, if you press i3's fs keys they do the same as the fs button in FF

So what's the difference in this not fullscreen fullscreen and fullscreen in your opinion?

>in this not fullscreen fullscreen
it's windowed
>what's the difference
tearing
not following standards

>tearing
fix that on xorg/driver side
>not following standards
I ran mpv with -v to see if there was anything interesting related to this. Am I missing something here as everything seems to work just fine here?
[vo/opengl/x11] Detected wm supports NetWM.
[vo/opengl/x11] Detected wm supports FULLSCREEN state.
[vo/opengl/x11] Detected wm supports ABOVE state.
[vo/opengl/x11] Detected wm supports BELOW state.

>fix that on xorg/driver side
that's not the point
>Am I missing something here as everything seems to work just fine here?
mpv is not the issue, disable your xorg vsync, try fs/nofs
startx /bin/mpv --no-config video.webm

> chromium without google assfuckery
no such thing

2-3 hours with what specs, my dude

why don't you run gentoo?

>Xorg has tearing
What a surprise.

Attached: 1379244503469.png (716x586, 657K)

>anime
>missing the point
What a surprise.

Compiling FF really is a breeze compared to chromium. Not only compiles much faster, you can also just grab the

k meant just get the binary

How large is the code base (in GB)?

>using cucked ff
no thanks

how do you find the flags to use

./configure --help

why did they do it like that? the program's flags aren't even properly separated from make's

>Version 71
huh? Version 72 is out

i9-9900K 8 cores, 16 thread
16GB DDR4-3200 RAM
NVMe SSD

What about environment variables? The icecat script sets a couple of tgem

Not sure what you mean. I don't see much difference to other stuff I compile, with the exception that FF wants you to use their Mach build system.

i mean make in general

They are listed as well, when you use ./configure --help.
You put them in your mozconfig file as well before running ./mach build.

Shit I'm blind then, gonna check when I'm at home

awesome is for better dwm ricer
dwm is dwm

chromium is going to kill uBlock interoperability. Just by using chromium you’re getting jewgled, because you’re supporting the (open source or otherwise) development of a war machine of a browser out to kill open standards. A browser so powerful even microsoft gave up and is just adopting chromium backend.

tl;dr switch away from chromium. Firefox is your only real hope for internet diversity nowadays..if google has their way with chromium, then DRM like widevine will become much more commonplace on the internet.

Holy crap that shit's heavy as hell

Good goyy, we will let you think you've escaped our telemetry, yes very good goy.

fpbp

I use chromium for web dev and Firefox as main driver on desktop and mobile.
Is Firefox viable for webdev yet?
Can I have a clean web dev profile and my main profile run parallel?

Why would enabling the "Potentially annoying security features" flag break Vimium...