User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0 Build ID: 20160726073904 Steps to reproduce: Build with mozconfig ac_add_options --enable-default-toolkit=cairo-gtk3 Actual results: ./mach build fails in ./configure when it tries to locate gtk+-2.0. Expected results: Configure should not need GTK 2.

(In reply to manday from comment #0) > User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 > Firefox/48.0 > Build ID: 20160726073904 > > Steps to reproduce: > > Build with mozconfig ac_add_options --enable-default-toolkit=cairo-gtk3 > > > Actual results: > > ./mach build fails in ./configure when it tries to locate gtk+-2.0. > > > Expected results: > > Configure should not need GTK 2. Plugin supports requires GTK2 because some plugin uses GTK2. (See Bug 624422)

Suggest to make it optional then or deprecate it. If a plugin hasn't been ported to GTK3 after 5 years, chances are it's not being maintained anyway.

It seems unfortunate that there's no way to disable this when building with gtk3. Especially given our drive to unsupport NPAPI plugins.

A build option to disable NPAPI support seems reasonable. NPAPI doesn't support GTK3 plugins, and there are no plans to add support.

given the progress made on NPAPI, maybe its time to revisit this? I for one haven't used flash in over a year AFAIK NPAPI still exists solely for flash. :) Thanks!

Just compiling today on machine, where it seems I cannot compile GTK2, so I have to rely on GTK3-only apps. Can some give update, how it look with disabling GTK2 dependency? Thank you

Let's dup of bug 1377445 as build config issue.