Build Error on Windows

[yashxog]

Hey guys, I am trying to build the Zen on Windows everything went well but got an error during the build,

ERROR:- 00:00:30 ERROR: Invalid value --with-l10n-base, /c/Users/Nextgen/Desktop/open-source-clone/desktop/engine/browser/locales doesn't exist
00:00:30 Config object not found by mach.
00:00:30 * Fix above errors and then restart with "./mach build"

I have the correct file path and en-US is also located inside the path but still why I am getting this error don't know can anyone please help resolve this?

[dosubot[bot]]

Hey @yashxog, I'm here to help you with any bugs, questions, or becoming a contributor. Let's squash those bugs together! 🐞

The error you're encountering suggests that the path specified for the --with-l10n-base option does not exist or is not being recognized correctly. Here are a few steps you can take to troubleshoot and resolve this issue:

1. Verify the Path: Double-check that the path /c/Users/Nextgen/Desktop/open-source-clone/desktop/engine/browser/locales exists on your system and that it contains the necessary localization files, including the en-US directory.

2. Path Formatting: Ensure that the path is correctly formatted for the Windows environment. Sometimes, path issues arise from incorrect slashes or case sensitivity. You might want to try using backslashes (\) instead of forward slashes (/) in the path.

3. Environment Variables: Make sure that any environment variables or configurations that might affect the path are set correctly. This includes ensuring that the current working directory is set properly when running the build command.

4. Permissions: Check if there are any permission issues with accessing the directory. Ensure that your user account has the necessary permissions to read from the specified path.

5. Configuration File: Verify that the configs/common/mozconfig file correctly sets the --with-l10n-base option. It should look something like this:

   ac_add_options --with-l10n-base="$PWD/browser/locales"

   Ensure that $PWD resolves to the correct directory path.

If these steps do not resolve the issue, consider checking for any additional logs or error messages that might provide more context on the problem.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[yashxog]

Thanks for the suggestion It worked by changing the path formatting to backslash () from forward slash (/). in the configs/common/mozconfig.