similar to: [LLVMdev] Problem building 2.0 release with .sln on win32 (and patch)

I am still using them for llc/llvm-as/opt/llvm-dis/tablegen and a few others. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of steve naroff Sent: Wednesday, January 14, 2009 4:09 PM To: llvmdev at cs.uiuc.edu; cfe-dev at cs.uiuc.edu Subject: [LLVMdev] win32/llvm.sln, win32/clang.sln Folks, Is anyone still using the Visual

Hi, I just moved to the CMake solution. By the way, the generated libs haven't the same names. In my opinion, we have to choose one way and remove the other one. If it helps, you can put in the win32 directory the result of CMake, or add a script that generate this win32 directory with cmake. Gab > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces

Please, don't remove, I'm using!!! Regards, Makslane > From: snaroff at apple.com > To: llvmdev at cs.uiuc.edu; cfe-dev at cs.uiuc.edu > Date: Wed, 14 Jan 2009 16:09:13 -0800 > Subject: [cfe-dev] win32/llvm.sln, win32/clang.sln > > Folks, > > Is anyone still using the Visual Studio solution files in the win32 > directory? > > If they aren't

Hi Steve, The Visual Studio solution and project files are quite handy. CMake creates absolute paths instead of relative paths, making it cumbersome to move things around. Also, for newcomers (e.g. students) it's really great to be able to download the package, open the solution and compile without any complication. They haven't been updated in a while, but it would be nice to have

These are the updated .sln and .vcproj files for building llvm with MSVC 2008. It turned out that the compiling errors were because these projects wasn't updated to reflect the actual status of the llvm files. I checked all the files (removed, moved or added) and now they are ok. It compiles all targets from the first "Build Solution", both for Debug and for Release mode. You need

On Tue, 13 May 2008, Razvan Aciu wrote: > These are the updated .sln and .vcproj files for building llvm with MSVC > 2008. > It turned out that the compiling errors were because these projects wasn't > updated to reflect the actual status of the llvm files. > I checked all the files (removed, moved or added) and now they are ok. > It compiles all targets from the first

I cannot see my post with a patch for FLAC.sln (too long?) Here I repeat this message, with patch file compressed to .zip: --------------------------------------------------------------- Every time I open current FLAC.sln in MSVS 2005, it rewrites (fixes) this file. The diff between new and old files is attached. Current version has several problems: a) it has one extra EndProject line. b) it

Makslane Araújo Rodrigues <makslane at hotmail.com> writes: > Please, don't remove, I'm using!!! What's preventing you from using CMake? Is there some problem we can solve? -- Oscar

> > I just moved to the CMake solution. By the way, the generated libs > > haven't the same names. > > Which ones? The only difference is that we now generate .lib files > where > .obj were generated on the past, and require a parameter to be passed > to > the linker for including them on the final executable. I was linking with VMCore.lib support.lib

Hi Steve, On Thu, 15 Jan 2009, steve naroff wrote: > For development, CMake is working great for me. I rarely get build > errors related to the project file being out-of-date. > > Is it true that CMake only generates absolute paths? Any idea on the > difficulty of generating relative paths? I consider this a pretty big > obstacle... I did not follow the full-thread, just

Mondada Gabriele <g.mondada at etel.ch> writes: > I just moved to the CMake solution. By the way, the generated libs > haven't the same names. Which ones? The only difference is that we now generate .lib files where .obj were generated on the past, and require a parameter to be passed to the linker for including them on the final executable. > In my opinion, we have to choose

Douglas Gregor <dgregor at apple.com> writes: >>> Please, don't remove, I'm using!!! >> >> What's preventing you from using CMake? >> >> Is there some problem we can solve? > > At some point, we'll need to deal with the testing issue in the CMake > build system. Clang, for example, uses some GNU make magic to run its > tests,

On Jan 15, 2009, at 8:43 AM, Óscar Fuentes wrote: > Makslane Araújo Rodrigues > <makslane at hotmail.com> writes: > >> Please, don't remove, I'm using!!! > > What's preventing you from using CMake? > > Is there some problem we can solve? At some point, we'll need to deal with the testing issue in the CMake build system. Clang, for example, uses

I verified the patch and it compiles all the targets, both in Debug and Release modes. If there is no someone else to keep the MSVC projects files updated, I will try from time to time to update them and to add the new targets. Maybe a note must be put in "docs/GettingStartedVS.html" at the Requirements section that llvm needs now MSVC (Express) 2008 to compile. Razvan -----

first: thank you for helping out >I might try compiling your source from the VS's Developer Command Prompt: >cmake --build . --target Fibonacci >Does this work? call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat" cd llvm-build cmake --build . --config Debug --target Fibonacci building Fibonacci example works BUT

Hi, How do I listen to .sln audio file or convert it to some format that can listened to? Sox does not seems to support .sln as an input file. Thanks. - Andrew

Folks, Is anyone still using the Visual Studio solution files in the win32 directory? If they aren't being maintained, they should probably be removed (to avoid any confusion). Thanks for any feedback, snaroff

Hi Oscar, For development, CMake is working great for me. I rarely get build errors related to the project file being out-of-date. Is it true that CMake only generates absolute paths? Any idea on the difficulty of generating relative paths? I consider this a pretty big obstacle... Thanks for all your hard work on this, snaroff On Jan 15, 2009, at 9:46 AM, Óscar Fuentes wrote: >

my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) x64 Native Tools Command Prompt for VS 2017 directory structure: test     llvm <-- git clone https://github.com/llvm-mirror/llvm, git checkout release_70       tools         clang <-- git clone https://github.com/llvm-mirror/clang, git checkout

Óscar Fuentes wrote: > srs <skaflotten at gmail.com> writes: > > >>>>> Try adding this to the link command of your executable: >>>>> >>>>> /INCLUDE:_X86TargetMachineModule >>>>> >>>>> I should document this somehow. >>>>> >>>>> >>>> Yeah, this is