similar to: [LLVMdev] Windows Binaries for 3.3 - I've built some (including shared library)

Hi, I'm trying to compile vmkit but am running into some problems. I followed the instructions at http://vmkit.llvm.org/get_started.html and checked out llvm and clang from svn, compiled them no problem and the same with classpath 0.97.2. I then checked out vmkit from svn and tried to build it. All these are located at /home/callum/vmkit/{llvm,classpath-0.97.2,vmkit}. I used this to

gv@cs.uu.nl wrote: > > Hi all, > > are there any Win32 users that have built wxRuby with VC++ and could put a > binary for me online? (Or send it to me?) > > I am using Andy Hunt''s one-click-installer Ruby-1.8.10. I''ve got a little extra time today, so I''m going to try to do a build (and write up readme instructions). However, if anyone out there

Hi all, are there any Win32 users that have built wxRuby with VC++ and could put a binary for me online? (Or send it to me?) I am using Andy Hunt''s one-click-installer Ruby-1.8.10. Thanks. Gerard Vreeswijk

I'm afraid that still does not completely answer the question. I'll accept that it will work for C programs, given what you quote. It says nothing about C++ however. That's a different animal entirely. g++ mangles names in a completely different fashion than VC++. Does mingw use VC++ style mangling? g++ processes exceptions in a completely different fashion than VC++. I

On Friday 18 February 2005 11:40 am, Jeff Cohen wrote: > I'm not sure you understand the problem. I wouldn't be surprised :) > Are you saying that a file > compiled with mingw can catch an exception thrown by a file compiled > with VC++ when the two are linked into a single program? That a program > compiled with mingw can be linked against the VC++ runtime and *not*

I'm not sure you understand the problem. Are you saying that a file compiled with mingw can catch an exception thrown by a file compiled with VC++ when the two are linked into a single program? That a program compiled with mingw can be linked against the VC++ runtime and *not* the mingw/gcc runtime? Linking against system DLLs is very different from what I'm talking about. Adam

> GCC is smart enough to realize it doesn't return. That's because the > declaration of abort() is decorated with __attribute__((__noreturn__)). > > So is GCC smarter than VC++? As it turns out, in VC++ the declaration of > abort() is decorated with __declspec(noreturn). > > Whidbey is not stricter than 2003, it is merely buggier. VC++ has always > complained

GCC is smart enough to realize it doesn't return. That's because the declaration of abort() is decorated with __attribute__((__noreturn__)). So is GCC smarter than VC++? As it turns out, in VC++ the declaration of abort() is decorated with __declspec(noreturn). Whidbey is not stricter than 2003, it is merely buggier. VC++ has always complained about functions failing to return a

  Hi Helpers. I am creating one wrapper VC++ dll for use some simple statistical functions like correlation/covariance for my college project. I have done the following:   I have gone thru R-exts.pdf u r mentioning. I have follwed the steps gievn under topic "The R api: entry points for C code". I have done these things 1) Created vc++ simple dll project. 2)inclued <R.h> in the

Aaron Gray wrote: >> GCC is smart enough to realize it doesn't return. That's because the >> declaration of abort() is decorated with __attribute__((__noreturn__)). >> >> So is GCC smarter than VC++? As it turns out, in VC++ the >> declaration of abort() is decorated with __declspec(noreturn). >> >> Whidbey is not stricter than 2003, it is

Linking my VC++ application with the standalone Rmath library yields the following; ------ Build started: Project: Complex plugin, Configuration: Debug Win32 ------ Linking... Creating library .\../Debug/complex_plugin.lib and object .\../Debug/complex_plugin.exp libRmath.a(mlutils.o) : warning LNK4217: locally defined symbol __iob imported in function _REprintf libRmath.a(dbeta.o) :

Hi, I'm trying to create a constant (named) struct and store a pointer to it in another struct using the C Api (and the llvm-fs bindings). As a contrived example, this is what I want to do: %A = type { %VTable* } %VTable = type { void (%A*)*, void (%A*)* } define void @main(%A* %a) { entry: %0 = getelementptr inbounds %A* %a, i32 0, i32 0 ; [type=%VTable**] %2 = somehow make a

Chris Lattner wrote: > On Fri, 18 Feb 2005, Aaron Gray wrote: > >> GNU's frontends are in C is that the problem ? I do not see the area >> properly. Please can you explain thurther. > > I'll let Jeff explain this one. The problem is that gcc cannot be built using VC++. You'll have to ask the gcc project as to why, but they've made it clear they have no

Hi everyone, Windows XP Pro OpenSSL 0.9.8i Ruby 1.8.6-p114 Ok, I''m going a bit OT here, but I want to see if anyone knows the answer. I built Ruby with VC++ 8 (cl 14). I managed to build and install OpenSSL. I also managed to build the Ruby OpenSSL extension, after 1 minor tweak to x509.h to eliminate a macro conflict: --- x509.orig Thu Oct 02 11:30:10 2008 +++ x509.h Thu Oct

Yes, it should find windows.h with the default configuration. But you have to be suspicious of beta code that Microsoft gives out for free. It might just be very buggy, or it might be deliberately crippled. Considering the price tag on Visual Studio, it's one or the other (and probably both). Out of curiosity, did it accept the solution and project files as is, or did it want to

----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfileor directory Date: Thu, 23 Dec 2004 08:05:39 -0800 >Yes, it

I agree completely with you, Jeff. However, I think it somehow would be nice, if you guys could tell comming users that the win32 solution is geared toward VC++ 7.1 (and hence use of other tools are at their own risk). And, I think it also would be really cool, if you guys come up with a solution how to handle multiple VC++ x solutions/projects from the same source, possibly ranging from VC

----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfile or directory Date: Tue, 21 Dec 2004 16:29:47 -0800

>> I thought Whidbey would really be upto the job, obviously not. > > Well, we don't know until someone tries. Oh, well we have got a bug to report to Microsoft then ! I still may carry on implementing any mods on the VS2003 port over to 2005 so we know where we are with that. There may well be a second beta so it would be good to get any problems in and reported to Microsoft in

It's a possibility, though it would be better to create whole separate trees for different versions of VS. It's not just the project and solutions that need to be kept separate; the object files themselves cannot be mixed between different versions of VS. There's no rush though. Trust me, C/C++ programmers will not rush to adopt Whidbey once it's released. You'd be