I need the build.ninja file to build chromium and it isn't generated - chromium

I was trying to build chromium, but when I run autoninja -C out/Default chrome, it says this:
ninja: error: loading 'build.ninja': El sistema no puede encontrar el archivo especificado.
It's in spanish, but it basically says that the system can't find the specified file.
That's right, it isn't a build.ninja file. But I don't know how to generate it.
Anything to make?
Edit, things I already tried:
Use gn gen out/Default, it throws an error.
Use it from Windows Terminal (CMD and PS) and from VS, same result for three ways.
Trying use VS 19 instead of 22, same result.
Edit manually \build\config\win\visual_studio_version.gni
Additional info:
I have Windows 11 and I use Visual Studio 2022, along with Visual Studio Code, I installed 2019 to try on if works with it, but not. :( If anything more is requiered, tell me.

You need to generate the build files before using ninja. Execute the following command:
gn gen out/Default
Then execute the autoninja command:
autoninja -C out/Default chrome

Related

My UIautomator is not starting in mac. I have done everything possible

I am learning appium and I have set up everything that is required. I have setup paths, installed android studio, run appium and created a virtual android device too. But when i am writing uiautomatorviewer its giving me an error
mac#Macs-MacBook-Pro ~ % uiautomatorviewer
-Djava.ext.dirs=/Users/mac/Library/Android/sdk/tools/lib/x86_64:/Users/mac/Library/Android/sdk/tools/lib is not supported. Use -classpath instead.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
mac#Macs-MacBook-Pro ~ %
Can anyone help me please
A. I encountered this issue once, sometime env var doesn't load and it throws error, open and load bash profile and run that command.
open ~/.bash_profile
source ~/.bash_profile
uiautomatorviewer
B. if appium server is running, try to close it and run the command.
Try the following command:
sudo ./uiautomatorviewer

lime test windows error command prompt not installed?

Everytime i load command prompt this always happens:
Me: cd Documents/Funkin-master
Me: Lime test windows
Error: You must have a "project.xml" file or specify another valid project file when using the 'test' command.
There is a Project.xml and I need to uninstall HaxeFlixel and reinstall a different version.
Someone help me please.
I WANNA MAKE MY OWN MOD.
I think you need to do "cd Documents/Funkin-master/Funkin-master" because I think you led to a directory that does not, in fact, have a project.xml. "cd Documents/Funkin-master" I think is just a folder containing a folder.
Oh! Also, if you need to update haxeflixel, the command is "haxelib update flixel".

Osquery MsBuild error msb1009

While building the Windows environment for OsQuery (on my Windows 10 VM) from their website(link: https://osquery.readthedocs.io/en/stable/development/windows-provisioning/), I am getting the msb1009 error during the phase where I have to run the tools\make-win64-binaries.bat command. I get the following result after running that command:
CMake Error at CMakeLists.txt:402 (project):
Failed to run MSBuild command:
C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/MSBuild/15.0/Bin/MSBuild.exe
to get the value of VCTargetsPath:
Microsoft (R) Build Engine version 15.7.179.6572 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
MSBUILD : error MSB1009: Project file does not exist.
Switch: VCTargetsPath.vcxproj
Exit code: 1
-- Configuring incomplete, errors occurred!
See also "C:/Windows/System32/osquery/build/windows10/CMakeFiles/CMakeOutput.log".
Microsoft (R) Build Engine version 15.7.179.6572 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
MSBUILD : error MSB1009: Project file does not exist.
Switch: osquery.sln
[-] osquery build failed.
I have been trying to make the osquery.sln file using that command and have looked online for solutions but without any success. Any help would be much appreciated!
Thanks in advance
Edit: Here is the output of running tools\make-win64-dev-env.bat and tools\make-win64-binaries.bat
tools\make-win64-dev-env.bat
tools\make-win64-dev-env.bat (contd..)
tools\make-win64-binaries.bat
Could you paste the full output of running the tools\make-win64-dev-env.bat and tools\make-win64-binaries.bat? Also have you tried closing out your shell and re-opening, or even worse -- reboot the system?
I ask because, as you note, it seems like the solution file never gets generated, which usually means there was either a missing dependency during provision, or some other issue when the script first ran. On first provision it's typically the case that a system reboot is needed, as Visual Studio community typically requires one. Further, we set a few shell environment variables that are leveraged during the build process, however those are supposed to be set at the end of the provisioning script.
Also feel free to hit us up in our Slack and check out the #windows channel :)
After a lot of code reading, researching online and trial and error, I found out that after a clean OS install, one would need to install git and then immediately clone the osquery repository on the user desktop rather than System32. This worked fine, at least for me. Just make sure to switch directories when opening command line with administrator mode.

/sbin/nologin issue with msys2 on Windows 10

I have just installed MSys2 (https://msys2.github.io, msys2-x86_64-20150916.exe) on my Windows 10 computer.
Once installed, the terminal is launched. But as soon as I stop it and relaunch it, I get the error: "Failed to run /sbin/nologin: No such file or directory".
Any idea on what to do?
You should figure out why Bash is trying to run /sbin/nologin. Check your Windows home directory (e.g. C:\Users\Joe) for files like .bash_profile, .profile, and .bashrc. Inspect those files and find which one is calling nologin.
If that doesn't help, try creating an empty file in C:/msys64/sbin/nologin, or wherever you actually installed MSYS2. An empty file would be a valid shell script and run without errors.
If the error is non-fatal you might consider just ignoring it.

dnvm upgrade command not working for ASP.NET 5 command line tools

While trying step 3 of Installing ASP.NET 5 on Windows, I am getting the following error on the command prompt of Windows 7. I have VS2015 Professional installed: PowerShell' is not recognized as an internal or external command, operable program or batch file.
After I restarted my Windows 7, the command worked. Following is the output:
C:\Windows\system32>dnvm upgrade
Determining latest version
Downloading dnx-clr-win-x86.1.0.0-rc1-update1 from https://www.nuget.org/api/v2
Installing to C:\Users\myUserName\.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-update1
Adding C:\Users\myUserName\.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-update1\bin to pr
ocess PATH
Adding C:\Users\myUserName\.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-update1\bin to us
er PATH
Setting alias 'default' to 'dnx-clr-win-x86.1.0.0-rc1-update1'