search for: vcvarsall

...$ find ~/.wine | grep nmake /home/mathieu/.wine/drive_c/Program Files/Microsoft Visual Studio 8/VC/bin/nmake.exe However I cannot figure out how to run the bat file for vs2005. Could anyone point me in the right direction ? $ cd ~/.wine/drive_c/Program Files/Microsoft Visual Studio 8/VC $ wine vcvarsall.bat wine: could not load L"C:\\Program Files\\Microsoft Visual Studio 8\\VC\\vcvarsall.bat": Bad EXE format for $ wineconsole "/home/mathieu/.wine/drive_c/Program Files/Microsoft Visual Studio 8/VC/vcvarsall.bat" It quickly open up a terminal, but close it afterward Thanks !...

...= x86_64-pc-win32 This doesn't currently seem to work. See, for example, the following output from when I run CMake twice from the command line, once with an x86 toolchain and once with an x64 toolchain: D:\src\llvm\build\ninja>"c:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" x86 D:\src\llvm\build\ninja>where cl C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\cl.exe C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\x86_amd64\cl.exe D:\src\llvm\build\ninja>cmake ..\.. -- Target triple: i686-pc-win32 -- Native target architecture is X...

Over the weekend I had a random urge to make clang-cl be able to self host. As of r230539, this should now be possible. Steps to try this out: 1) Run vcvarsall.bat, same as you would for an MSVC hosted build. 2) set CC=CXX=clang-cl (make sure it's in your path 3) Run CMake as you normally would, no special flags needed. 4) There is no 4, that's it! Currently LLD will not build, so if you have cloned LLD into your repo you will need to not build...

...tallation, system, cmake version, etc. If it does work, then it's more likely a problem with the cmake command line you're running. On Thu, Nov 29, 2018 at 9:45 AM Osman Zakir <osmanzakir90 at hotmail.com> wrote: > I opened up an elevated Developer Command Prompt for VS2017, ran vcvarsall > with argument amd64, and then ran the command "cmake-gui" in that command > prompt. Then in that gui window, I clicked on "Configure" without doing > anything else. At the end, I got an error window saying that there were > errors, and that project files may be i...

...oticed this happens when I use a global constant, eg. a string, but not always - for some inputs it triggers the error, for some it doesn't. The bat that links into exe looks like: ``` @call set path=C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Auxiliary\Build;%path% call vcvarsall.bat x64 cl /EHsc /DEBUG /Z7 /LD s.obj code.cpp ``` and the IR: https://godbolt.org/z/dcrzoq Researching a bit I could find an issue on Rust's Github that seems to have been solved by time, and the statement `default rel` for an assembler to be inserted at the beginning of the ASM file, whic...

I probably need GCC for Git bash. And the one I have is MinGW's GCC, which is the one for Windows. I don't know why CMake is trying to find Linux headers. Hopefully someone who knows better what to do will weigh in here. @Jonathan Goodwin<mailto:jondgoodwin at gmail.com> , are you sure you didn't have to tell it where the header files for Windows are? If I need to specify

...c. If it does work, then it's more likely a problem with the cmake command line you're running. On Thu, Nov 29, 2018 at 9:45 AM Osman Zakir <osmanzakir90 at hotmail.com<mailto:osmanzakir90 at hotmail.com>> wrote: I opened up an elevated Developer Command Prompt for VS2017, ran vcvarsall with argument amd64, and then ran the command "cmake-gui" in that command prompt. Then in that gui window, I clicked on "Configure" without doing anything else. At the end, I got an error window saying that there were errors, and that project files may be invalid. Here's...

You are correct, sir. Everything works much better if I run CMake and Ninja from a "developer command prompt." I displayed the path and almost fell off my chair laughing. The road to hell is paved with environment variable entries. Two questions. 1. Building with Visual Studio created build/release/bin. Building with Ninja created build/bin (no release directory). Does that make sense?

...es :-) > > > On 25 February 2015 at 15:48, Zachary Turner <zturner at google.com> wrote: > > Over the weekend I had a random urge to make clang-cl be able to self > host. > > As of r230539, this should now be possible. Steps to try this out: > > > > 1) Run vcvarsall.bat, same as you would for an MSVC hosted build. > > 2) set CC=CXX=clang-cl (make sure it's in your path > > 3) Run CMake as you normally would, no special flags needed. > > 4) There is no 4, that's it! > > > > Currently LLD will not build, so if you have clon...

I'm not sure if this is the correct place to email for this kind of thing, but I couldn't find any other contact info. Also, I am new to llvm, so please try to be understanding. I keep getting an error when I try to compile a simple Hello World program (as a test)(error included below). The error is: Clang: warning: unable to find a Visual Studio installation; try running Clang from a

Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, Tom

Hi guys, I discovered xapian today and I'm trying it because it looks promising compared to other FTS engines. However I'm in a windows environment so it's a bit painful to set up as there is no official binaries. I've heard about http://www.flax.co.uk/xapian_binaries And I'm trying to build their latest release (1.2.8). After a few tries I manage to compile everything with