similar to: Using VC8/VS2005 command line compiler on wine

Hello, I've managed to get LLVM 1.8 to build properly with MSVC8 with some effort. Most of the changes necessary were very minor C++ usage issues; for instance, VC8 can't deal with prototyping something that's really a class as 'struct Foo;' or vice versa (it creates issues with matching function signatures during linking.) Additionally, I had to do quite a few updates to the

Bugs item #16211, was opened at 2007-12-10 15:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=16211&group_id=85 Category: win32-service Group: Packaging Status: Closed Resolution: Rejected Priority: 3 Submitted By: Sorin Sbarnea (intersol) Assigned to: Daniel Berger (djberg96) Summary: win32-service will not install/build corectly if the system

On Thu, 24 Aug 2006 srhilber at ncsu.edu wrote: > I've managed to get LLVM 1.8 to build properly with MSVC8 with some > effort. Most of the changes necessary were very minor C++ usage issues; > for instance, VC8 can't deal with prototyping something that's really a > class as 'struct Foo;' or vice versa (it creates issues with matching > function signatures

Hello, We found a problem that we are not sure who is responsible. Here is what we found: On some small file (around 1 sec) if we ask to compress the file at 128kb/s On an encoder compiled with Microsoft visual 7.1 it generate a file at 160kb/s (that is the behaviour we expect because of the short length of the file) On same encoder compiled with Microsoft visual 8.0 with the same parameter it

Hi, Have you tried the new VC8 Beta? It's been out for less than 2 weeks: http://lab.msdn.microsoft.com/express/visualc/default.aspx It's supposed to have improved standards compliance. Regards, -Eugene Talagrand On Thu, 8 Jul 2004, Chris Lattner wrote: > Date: Thu, 08 Jul 2004 01:56:03 -0500 (CDT) > From: Chris Lattner <sabre at nondot.org> > Reply-To: llvmdev at

I was going through documentation and source lately, and I decided how to make llvm bytecode more compatible to C++: 1) thiscall sould be introduced, which would take N arguments and the first argument would always be the C++ "this" argument. This would abstract llvm compiler dependant C++ code emittion. 2) the ret instruction should be able to return structs (as Chris has already

On Tue, 21 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: > I was going through documentation and source lately, and I decided how to > make llvm bytecode more compatible to C++: > 1) thiscall sould be introduced, which would take N arguments and the > first argument would always be the C++ "this" argument. This would > abstract llvm compiler dependant C++ code emittion. Sure.

I was going through documentation and source lately, and I decided how to make llvm bytecode more compatible to C++: 1) thiscall sould be introduced, which would take N arguments and the first argument would always be the C++ "this" argument. This would abstract llvm compiler dependant C++ code emition. 2) the ret instruction should be able to return structs (as Chris has already

Hello Guys, I''m trying to get this working: t = Thread.new { while true puts "printing a line" sleep 2 end } gets t.exit puts "exiting" As you see, the idea is get multiple "printing a line" until a hit enter. The thing is this is a known problem for 1.8 on win32. I tried both mingw, VC6 and VC8 with the same results. Saw a post

All, Mongrel 1.1.3 Rails 2.0.2 Ruby 1.8.6 Windows XP SP2 When I issue the command "ruby script/server" from any of my Rails projects on v. 2.0.2, I get a Windows dialog with the error: "The application has failed to start because MSVCR80.dll was not found. Re-installing the application may fix this problem." I''ve gone through the process of attempting to introduce

On Thu, 8 Jul 2004, Vladimir Prus wrote: > > Sorry, but it is not even close to working (its template and STL support > > is horribly lacking). The Visual Studio "Whidbey" compiler, now in beta, > > will handle it though with only a reasonable amount of tweaking to the > > LLVM sources. I have no idea about when Microsoft intends to release it > > though,

Chris Lattner wrote: > On Thu, 8 Jul 2004, Bill Wendling wrote: > > I just wanted to know if anyone's looked into using the free version of > > Microsoft's Visual C++ toolkit for LLVM: > > > > http://msdn.microsoft.com/visualc/vctoolkit2003/ > > Sorry, but it is not even close to working (its template and STL support > is horribly lacking). The

>From: Paolo Invernizzi <arathorn at fastwebnet.it> >Date: Thu, 16 Sep 2004 11:18:00 +0200 >If VC6 is not doing something wrong with templates... ;-/ As far as I know is template handling a part of some C++ ISO standard. Then, MS should adhere to this... However, what you objects against is that MS didn't implement STL the way STL should be implemented. And the reason to

Hi all, With the latest 1.8.6 release out today, I was wondering - what would you all think of a Windows-only fork of Ruby? I mean Perl has ActiveState, right? It ships with a slightly different interpreter and different libraries, so why not Ruby? Here''s what I''m thinking: * Win2k or later. No 95/98/ME support. No cygwin/mingw, either. * Assume VC++ 8. Use whatever

Hey Daniel, I''m trying to leave you a comment on this article you wrote: http://djberg96.livejournal.com/168403.html But since you disabled OpenID and anonyous, I''m not fond to register for another account just to reply your comments. Quoting your post: "" Unfortunately, I''ve slammed into the cold hard fact that FFI just isn''t the grand solution

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: speex_vs2008.diff Type: application/octet-stream Size: 165590 bytes Desc: speex_vs2008.diff Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20071127/08917736/speex_vs2008-0001.obj

On Fri, 27 Jan 2006, Jeff Cohen wrote: > _CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it in > VS2003. It shouldn't hurt to define it though, even if VC2003 where it does nothing. Right? -Chris > Morten Ofstad wrote: > >> Jeff Cohen wrote: >> >>> The project files need frequent updating. I cannot maintain VS2005 >>>

Jeff Cohen wrote: > The project files need frequent updating. I cannot maintain VS2005 > project files, so while they could be distributed with LLVM, they will > become broken fast. Also, VS2003 and VS2005 project and solution files > cannot coexist in the same directories, further complicating matters. The VS2003 project files convert without problems -- you might want to add in

_CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it in VS2003. Morten Ofstad wrote: > Jeff Cohen wrote: > >> The project files need frequent updating. I cannot maintain VS2005 >> project files, so while they could be distributed with LLVM, they >> will become broken fast. Also, VS2003 and VS2005 project and >> solution files cannot coexist in

The project files need frequent updating. I cannot maintain VS2005 project files, so while they could be distributed with LLVM, they will become broken fast. Also, VS2003 and VS2005 project and solution files cannot coexist in the same directories, further complicating matters. Aaron Gray wrote: > Hi Morten, > > If you can make the VS2005 project files availiable on the net then I