/me kicks sudo

hey, just a joke

I know i know

😏😏

Failed to build with msvc tools (I can send output later) (this mode worked before on my home win10, didn't work at workplace win 7) VSSolution mode also incomplete - can build only part of generated projects

Ehich Visual Studio versions are you using?

Probably they are different in your Home and in your Work

2015 comunity both

Mmmm

Not sure if 2014 is *officially* supported

Btw, check in your Environment Variables the Path one

May be different updates.

What to search in path?

Check you have c:\ROSBE\bin

Not sure if you need that

Check you have c:\ROSBE\bin

location is another (E:\ReactOS\ROSBE\bin) but it presents in path

at home build stopped working today

Okis

Mmm

Odd

Okis asking our VS devs

Are you using Rosbe to compile ReactOS?

You have to use the Visual Studio prompt btw

You have to use the Visual Studio prompt btw

Yes, It's vs command prompt (otherwise rosbe will not detect this compiler)

Mmm

Okis in the VS prompt

Do a "cl"

If it says a DLL is missing

Then your VS path is not properly set

VS/VC

E:\ReactOS\build2>cl Microsoft (R) C/C++ Optimizing Compiler Version 19.00.23918 for x86 Copyright (C) Microsoft Corporation. All rights reserved. usage: cl [ option... ] filename... [ /link linkoption... ]

Mmmm

Process is simple: Start VS command prompt (x86) // set PATH=%PATH%;<path to rosbe\bin> // mkdir and cd build/msvc-ninja/ or similar // run path/to/source/configure.cmd // run ninja bootcd

I'm using this instruction

you need to start from the VS command prompt

in your start menu, you should have items like "VS2015 x86 Native Tools Command Prompt"

you have to start from there

Yes, It's right from there

then cl should work

did you do

set PATH=%PATH%;<rosbe>

because if cl isn't found

it sounds like you forgot the %PATH%; part

tried again

E:\ReactOS\build2>set PATH=%PATH%;e:\ReactOS\RosBE\bin; E:\ReactOS\build2>\ReactOS\Source\configure.cmd Detected Visual Studio Environment VS14-i386 Preparing reactos... The system cannot find the file specified. — The C compiler identification is MSVC 19.0.23918.0 — The CXX compiler identification is MSVC 19.0.23918.0 — Check for working C compiler using: Ninja — Check for working C compiler using: Ninja — broken CMake Error at C:/Program Files (x86)/CMake/share/cmake-3.3/Modules/CMakeTestCCompiler.cmake:61 (message): The C compiler "C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/cl.exe" is not able to compile a simple test program. It fails with the following output: Change Dir: E:/ReactOS/build2/CMakeFiles/CMakeTmp Run Build Command:"E:/ReactOS/ROSBE/Bin/ninja.exe" "cmTC_b444d"

Preparing reactos... The system cannot find the file specified. <---— suspicious

HBelusca (https://jira.reactos.org/secure/ViewProfile.jspa?name=hbelusca) resolved CORE-11508 - Implement support for post-mortem ("Auto-Execute") debugging as 'Fixed' https://jira.reactos.org/browse/CORE-11508

In temge Wiki it is recommended ro have RosBE directly in C:, dunno if having it as a subfolder and in E: can be guilty

hello everyone :)

Hi

Morning

Hi 😊

Hai

In temge Wiki it is recommended ro have RosBE directly in C:, dunno if having it as a subfolder and in E: can be guilty

Reinstalled into default C:\ROSBE - same result I'll try VS update 3 later

It was VS bug 🐞 UCRTVersion=10.0.10586.0 UniversalCRTSdkDir=C:\Program Files (x86)\Windows Kits\10\ Actually there was no CRT there

Ahaaa cool

:)

Work work work

2nded...

Hi everyone!

Welcome!

😊

Hola, man

Morning

Morning to you too!

Hi

Google SoC lwIP Report Week 6 https://reactos.org/blogs/google-soc-lwip-report-week-6

We need moar bug reports!

I'll get it in a virtual machine and run every application known to mankind to get as many problems as possible

Do I set it up as a windows xp machine? And will virtualbox drivers work with it?

The only way to find it out - try it

Do I set it up as a windows xp machine? And will virtualbox drivers work with it?

using Win XP mode, works fine

/me

/me

/me

/me

/me

/boring

/CantWaitTillThisKillsWindows

#CantWaitTillThisKillsWindows