similar to: [LLVMdev] Default targets and MS Visual C++

"Keith Walker" <keith.walker at arm.com> writes: > When using cmake to configure the LLVM build for building with MS Visual C++ > only the X86 target is built by default, whilst for any other compilation > system all targets are built by default. > > > > I was just wondering whether there is a current reason for this difference > of the default targets

Ok! If there are indeed cross-compiling targets defined, then vs2005 projects probably should be maintained. In any case, this is all up to Jean-Marc, since he's the one that actually has authority to change it :) Jean-Marc -- what's your opinion? On 11/28/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote: > > I pulled the test directory from 2003, but everything else

Hi All, I have been using a slightly modified version of libtheora (from about a year ago) and since libthoera is now reached BETA 2 I thought it would be time to update. My application worked fine with that version of libtheora. So now I am trying to build libtheora beta 2 in Ms Visual C++ 2005 and I am having a few problems. When I try to compile it I get the error below. You are compiling

Hi All, I have been using a slightly modified version of libtheora (from about a year ago) and since libthoera is now reached BETA 2 I thought it would be time to update. My application worked fine with that version of libtheora. So now I am trying to build libtheora beta 2 in Ms Visual C++ 2005 and I am having a few problems. When I try to compile it I get the error below. You are compiling

Hello, I'm trying to compile a library in MS Visual C++ using R.dll. For that, I need R.lib for linking. Where can I get it? "Readme.packages" for R says: "First build the import library R.lib by lib /def:R.exp /out:Rdll.lib" But for this, I need R.exp, that is also not provided with R installation (Lib.exe output: LIB : fatal error LNK1104: cannot open file

Russell Wallace <russell.wallace at gmail.com> writes: > C:\llvm\bin>llc -version > Low Level Virtual Machine (http://llvm.org/): > llvm version 2.6svn > DEBUG build. > Built Jan 31 2010(20:46:01). > > Registered Targets: > x86 - 32-bit X86: Pentium-Pro and above > x86-64 - 64-bit X86: EM64T and AMD64 > > I did specify the release build

I pulled the test directory from 2003, but everything else from 2005. The 2005 files have more ?cross-compiling? targets than the 2003 ones. I fixed the various missing files in the new 2008 projects (misc.c and one other other are gone now). The only thing you could do which would make them more compact would be to get rid of the subdirectories under each vs-version. There is no real need for

Keith Kyzivat a ?crit : > Something to look into perhaps is Trolltech's 'qmake' tool. > It fills the role of something like autotools or now defunct imake. I think TrollTech deserves a prize for their accomplishment in making qmake even worse than autotools (I'm using it for something else and wish I wasn't -- Qt itself is fine though). I've heard good things about

C:\llvm\bin>llc -version Low Level Virtual Machine (http://llvm.org/): llvm version 2.6svn DEBUG build. Built Jan 31 2010(20:46:01). Registered Targets: x86 - 32-bit X86: Pentium-Pro and above x86-64 - 64-bit X86: EM64T and AMD64 I did specify the release build with cmake; the lack of crashing on exit of programs compiled therewith confirms that :-) As far as I can see, the

On Fri, Apr 6, 2012 at 6:15 PM, Alan Garny <agarny at hellix.com> wrote: > Hi, > > From what I have seen on this mailing list and elsewhere, it would seem that > it isn’t possible to build LLVM as a shared library using Visual C++. Still, > I would imagine that quite a few people are or would be interested in it, > so… is there any plan to support this any time soon? This,

Hi, Myself and a colleague of mine are trying to use LLVM's exported targets [1] on trunk and I've noticed that the generated CMake files (LLVMConfig.cmake and LLVMExport.cmake) are broken when trying to use Visual Studio 2015 (using CMake 3.2.1). ## Broken target properties in LLVMExports.cmake LLVM itself builds fine but when our project tries to do ``find_package(LLVM)`` we get the

Hello, I'm running MS Office 2003 in Wine 1.1.0. When I launch Excel, the following dialog box appears with a cryptic error message: Code: Microsoft Visual Basic ! Error accessing file. Network connection may have been lost. I don't know what Visual Basic has in common with a network connection, but when I attempt to utilize Tools > Macros > Visual Basic Editor, all of the

Hi, >From what I have seen on this mailing list and elsewhere, it would seem that it isn't possible to build LLVM as a shared library using Visual C++. Still, I would imagine that quite a few people are or would be interested in it, so. is there any plan to support this any time soon? This, unless it's already supported in some way or another which I am not aware of.? I have been

The VS2005 project files are known to not be up-to-date, so I can understand that you'd need to fix some things. Can you verify with an import of the VS2003 project files, that there is no need for any fixes, and just works after importing? Managing multiple project files should be minimized if at all possible. If a straight import of vs2003 project files can be done without any changes

We're having a problem that is the reverse of prblems that others have had: if we have a file open in Visual C++, and change it from another editor (either on the PC or on Unix), Visual C++ does not notice that it has been changed and ignores the file when it does a make. If the file is on a local drive, everything works fine. We're running Samba version 2.0.4b on Solaris 2.6 and Visual

Hi, I am trying to implement on a Win7 box the showArgs example of section 5.10.2 "Calling .External" of the R extension manual. I am using interchangeably gcc (RTools) and Visual C++ (via Makefile.win) to build a package. I get a couple of runtime oddities when the dll compiled with Visual C++. I'd value comments, observations and tips from interested readers. I tried my best to

Hi I installed a program through Wine without much of a problem But then It flashes a Error message Saying "Microsoft Visual C++ Runtime Error" I assume I need to install the Visual C++ libraries through WineTricks. to at least to try to fix the Problem I got Winetricks installed and Ready...I think. Now I just need a walkthrough on how to install the Visual C++ Libraries through

Since upgrading samba to version 2.0.3, we're now unable to create new Visual C++ files, projects and build executables in network home directories. No other problems are reported! When creating a new Project an error message occurs: "The specified filename is invalid", except C++ goes ahead and creates the directory. It does create the necessary directory, but never seems to find

I'm a programmer using Microsoft Visual FoxPro for daily work. I'm trying to run a self written program on wine. This program uses several Windows API functions. An example is: DECLARE INTEGER ShellExecute IN z:/usr/lib/wine/shell32.dll.so ; INTEGER, STRING, STRING, STRING, STRING, INTEGER ShellExecute( 0, "open", "notepad.exe", "", "", 1 )

All, I'm a newbie to R and I am interested in seeing a simple example of calling a 3rd party Visual Studio generated DLL from RStudio. Does anyone have a simple example which also walks through the preliminary steps of setting up the INCLUDE path and the library path to either a DLL or LIB file ? I have tried to find an easy example, but thus far had no luck finding an example using Rcpp