Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

P3A buildflag cannot be set to false #12450

Closed
freespeech4ever opened this issue Nov 2, 2020 · 1 comment
Closed

P3A buildflag cannot be set to false #12450

freespeech4ever opened this issue Nov 2, 2020 · 1 comment

Comments

@freespeech4ever
Copy link

Description

Compilation will fail on Windows/Linux/Mac if brave_p3a_enabled buildflag is set to false. Appears that only a few references in brave_browser_process_impl are not guarded. I am submitting a patch that allows it to build.

Steps to Reproduce

  1. Set brave_p3a_enabled = false in components/p3a/buildflags.gni

Actual result:

Fails due to undeclared identifiers.

Expected result:

Successful build without P3A.

Reproduces how often:

Always

Brave version (brave://version info)

Latest.

Version/Channel Information:

  • Can you reproduce this issue with the current release? Yes
  • Can you reproduce this issue with the beta channel? Yes
  • Can you reproduce this issue with the nightly channel? Yes
@bsclifton
Copy link
Member

Thanks for checking this out - P3A is a core piece of functionality which was only guarded as it didn't have an implementation on Android yet. This is being fixed when addressing #6176 and the guards will be removed. My recommendation would be to patch this functionality out. The only place which is sending the data is components\p3a\brave_p3a_service.cc which you can patch to no-op

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants