search for: vc2003

...15 00:46 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=220&aid=9297&group_id=35 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: Patch to compile wxruby 0.0.39 on windows (vc2003,swig 1.3.31,wxwidgets 2.8.0) Initial Comment: I''m sorry for the size of this beast, but the changes to wxruby were made just to support the other project i was working on, so they accumulated :) Main parts of this patch rakemswin.rb : updated to WxWidgets 2.8 and using File.join for fil...

...9;t exist in VS2003 either. Don't know where to add it. Chris Lattner wrote: > 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 >>>> project files, so while they could be distributed wit...

...kay, I have done as you have requested. The only thing I did not like was a clsh between the enum X86 and the new namespace X86, which I had to rename as x86 :( Anyway, I suppose the lower case 'x' in 'x86' fits in with the lowercase 'llvm' namespace. Build tested on MS VC2003 and Linux. Aaron -------------- next part -------------- A non-text attachment was scrubbed... Name: NewX86AsmPrinter.tar.gz Type: application/x-gzip Size: 5810 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050701/3cda425e/attachment.bin>

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 >>> project files, so while they could be distributed with LLVM, they will >>> become br...

...d. > > The only thing I did not like was a clsh between the enum X86 and the > new namespace X86, which I had to rename as x86 :( > > Anyway, I suppose the lower case 'x' in 'x86' fits in with the > lowercase 'llvm' namespace. > > Build tested on MS VC2003 and Linux. > > Aaron > >------------------------------------------------------------------------ > >_______________________________________________ >LLVM Developers mailing list >LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >http://mail.cs.uiuc.edu/mailman/listi...

_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

...e talking about, or am I missing something? -Chris >> 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 >>>>> project f...

...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 lue of >> that. > > ok. If both you and Jeff are okay with still implementing a VC2005 version spawning off changes to the VC2003 port then I am happy to do that. >> Q. Is abort() used rather than C++ exception handling for compatibility >> reasons with older C++ compilers ? > > These aren't recoverable errors: These abort calls are really put in for > the moral equivalent of "assert(0);":...

Ok, I have checked in the first draft of rails win32 service into examples mongrel_rails_service is the controller, and the _svc script is actually the service. The controller uses Mongrel Commands as requested by Zed, but the service was simplified for debugging purposes, later will merge and refactor both files. The environment defaults to production, so if wanted to run it on other, you must

...pilers and doesn't require this huge amount of > per-compiler-version crap? Otherwise, I'm seriously considering removing > all those project files from the build since time has proven there's > just no way to get them up-to-date. It would actually be fine to just maintain the VC2003 (or possibly older) VC project file (and only the project file is needed). All newer VC versions will happily upgrade an older project if you try to open it. That said, we don't use the supplied project. We simply compile in the speex .c files. You could easily replace the Win32 build files wi...

...ing I did not like was a clsh between the enum X86 and the >> new namespace X86, which I had to rename as x86 :( >> >> Anyway, I suppose the lower case 'x' in 'x86' fits in with the >> lowercase 'llvm' namespace. >> >> Build tested on MS VC2003 and Linux. >> >> Aaron >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >&...

On Thu, 30 Jun 2005, Aaron Gray wrote: > I have "refactored" the X86AsmPrinter into a number of files ready for > the MASM and NASM backends to be added. Nice! > There is a new namespace llvm::X86 to replace the anomonous namespace as > this does not work accross mutiple .h and .cpp files. Other than that > everything is pritty straight forward, t may possibly need

...gt; -Chris > >>> 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 >&...

On Fri, 18 Feb 2005, Aaron Gray wrote: >>> 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

Feature Requests item #3978, was opened at 2006-03-30 05:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=414&aid=3978&group_id=85 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: Compile files for Ruby One-Click installer Initial Comment: Compile the files so they work

Hi, Is is possible to have makefiles, batchfiles, whatever that just calls the command-line compilers and doesn't require this huge amount of per-compiler-version crap? Otherwise, I'm seriously considering removing all those project files from the build since time has proven there's just no way to get them up-to-date. Jean-Marc Alexander Chemeris a ?crit : > Hello, > > On

...ery to allow for run-time without changing how the other platforms work, esp. the platform function overrides. I also included two small fixes to svn, as well as project file changes needed to get things working. If anyone has any feedback that would be great. I have tested this on windows using vc2003 and darwin using xcode. I mainly want to make sure I didn't break any of the arm/blackfin stuff, as I don't have the setup(s) to test that. Thanks! Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: filters_altivec.c Type: application/octet-stream Siz...

I am trying to run "Sony Vegas Movie Studio 8.0" on Ubuntu 7.04 in wine-0.9.41 but I get this error: "This application is not supported in Windows 2000". How can I make wine emulate Windows XP? Thanks in advance. Dotan Cohen http://what-is-what.com http://gibberish.co.il ?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-?-? A: Because it messes up the order in which people

I have "refactored" the X86AsmPrinter into a number of files ready for the MASM and NASM backends to be added. There is a new namespace llvm::X86 to replace the anomonous namespace as this does not work accross mutiple .h and .cpp files. Other than that everything is pritty straight forward, t may possibly need tweeking though. It has been built under MS VS2003, but I am not sure how

Hey Zed- I had a user with an app that was leaking memory with mongrel but not lighty/fcgi. I have been doing anything I can to track it down. I already did the Mutex patch to use unshitf and pop instead of shift and push and it didn''t really help much. The mem leak only really shows up when you use the wsess option to httperf. The other day I saw a ruby C extension that