similar to: printf in GUI App?

How do I remove all my Wine/Darwine versions (from Mac)? Should I run "make uninstall" from the last wine-0.9.33 and then delete the /Users/.../wine* folders? A search for windows.h gives: /Developer/Headers/Wine/include/wine/windows/windows.h (Darwine?) /Users/me/Documents/downloads/wine-0.9.15/include/windows.h (Wine) /Users/me/Documents/downloads/wine-0.9.16/include/windows.h (Wine)

Dee Ayy wrote: > On Sun, Aug 24, 2008 at 10:33 PM, vitamin <wineforum-user at winehq.org> wrote: > > > It can only work from cmd.exe. However I'm not sure if it's properly implemented there yet. > > Of course your app have to be console app not gui. > > > > My app is console. But this is an MSVC++ compiled app which runs on > MS Windows cmd.exe

Dee Ayy wrote: > On Sun, Aug 24, 2008 at 9:14 PM, vitamin <wineforum-user at winehq.org> wrote: > > > No this is impossible. If you do that most every program will brake. > > > > So what steps can I take to avoid this error? It can only work from cmd.exe. However I'm not sure if it's properly implemented there yet. Of course your app have to be console

IMHO, the CMake-based build system is almost complete enough to replace current MSVC++ project files (modulo some community review and bug-fixing). Is this enough for adding it to the LLVM repo? >From the point of view of a MSVC++ user, the new build system is trivial to maintain: you can add a new library or tool executable in less time that it takes to open the project file on MSVC++, it

Dmitri Makarov <nebraskin at yahoo.com> writes: >> Is it reasonable to ask > > Yes, it's reasonable. Since this is open source we depend on contributions from the community, etc... You know how the song goes. Seriously, I'll like to see a healthy MSVS build as much as you, but someone must do the work. > Moreover, I'd be content with a build system that

On Tue, 12 Jul 2005, Aaron Gray wrote: >>> Right, presumably Wndows does not set the TT. Should Windows or MSVC++ >>> have one ? If so how do I go about it. Maybe Jeff should be involved ? >> >> It should/will. Currently there is no C/C++ front-end that works on native >> windows, but that doesn't really matter. In the future, we want to key off

>>> 1. Please send patches instead of full files. The best way to do this >>> is >>> to use CVS like this: 'cvs diff -u' in the directory that you care >>> about. You can also specify specific files to diff as well. >> >> Okay, I will do this in future, our posts crossed so I have not done that >> for the MASM backend. I will

Dee Ayy wrote: > How can I insure that it gets unlocked? > What you describe indicates that something has gone wrong because a critical section has not been released in a reasonable amount of time. Normally one might be entered for a few milliseconds, if that. Try turning on debug flags to look at the logs to see what calls have been made but have not returned before the

This thread is odd to me. It seems that the gist of your guys' argument is that you don't know if we will ever get full support, therefore we don't welcome progress towards that (very useful) goal/feature. If the specific proposal doesn't make make sense from a design standpoint, that's one thing, but saying we shouldn't take it because of licensing issues with MFC or

On Sep 20, 2008, at 2:22 PM, Óscar Fuentes wrote: > IMHO, the CMake-based build system is almost complete enough to > replace > current MSVC++ project files (modulo some community review and > bug-fixing). Is this enough for adding it to the LLVM repo? Yes. >> From the point of view of a MSVC++ user, the new build system is >> trivial > to maintain: you can add a

Chandler Carruth <chandlerc at google.com> writes: >> And here there is no "Windows ABI" here at all. Because every compiler >> (MSVC, gcc / clang, Borland) does its own stuff. This is why I said >> that the proposal naming is confusing. >> > > I don't know anything about Borland, and I don't think that matters. But I > think that the

On Jul 31, 2013 10:16 AM, "Stephen Lin" <swlin at post.harvard.edu> wrote: > > Oh, well, I don't actually have any objection to the patch (I'm not > sure if Oscar does) or work in this direction. (So apologies for > hijacking, it's just I wanted to back up the sentiment that Oscar > expressed initially.) > > I'm honestly just trying to

Oh, well, I don't actually have any objection to the patch (I'm not sure if Oscar does) or work in this direction. (So apologies for hijacking, it's just I wanted to back up the sentiment that Oscar expressed initially.) I'm honestly just trying to understand why the engineering focus is where it is, and wonders if anyone has put any thought into supporting our own (or possibly

> Quite the contrary, knowing that Clang's C++ ABI is completely > incompatible with MS is a maintenance *simplification*. Yes, for example, as explained by Bjarne once, incompatible name mangling schemes for ABIs that are not guaranteed to be 100% binary compatible is a _feature_, not a bug, since it prevents anyone from even beginning to develop a workflow that relies upon linking

Hello everybody, I sent something about this before, but this bug is still there, so... If you call ov_time_seek(vf, 0); it will fail, returning OV_EFAULT (from ov_pcm_seek_page). I think this must be a bug, because seeking to 0 seconds *should* be OK. Another thing, when ov_time_seek fails with OV_EFAULT, you cannot continue playing (because of the goto seek_error). This is not clear from

Hello I was hoping to get some advice regarding teaching R in an academic environment. What are the best choices with respect to textbooks? When this question was asked a few years back, people were primarily recommending ?Modern Applied Statistics with S? and ?Introductory Statistics with R? as two good choices. I?ve also heard some good thinks regarding ?An R Companion to Applied

I'm receiving the following error in a custom app: err:ntdll:RtlpWaitForCriticalSection section 0x110048 "heap.c: main process heap section" wait timed out in thread 001a, blocked by 001c, retrying (60 sec) wine: Critical section 00110048 wait failed at address 0x7bc3ad00 (thread 001a), starting debugger... err:ntdll:RtlpWaitForCriticalSection section 0x110048 "heap.c: main

Charles Davis <cdavis5x at gmail.com> writes: > Huh? Intel CC supports the MSVC++ ABI. Zortech (Digital Mars) supports > it, too (though the guy who wrote it isn't too proud of that fact--or > the fact that he even wrote that compiler to begin with). Heck, even > CodeWarrior supported it (as Howard Hinnant might well remember), > before Metrowerks sold off their x86

On Mar 28, 2013, at 1:35 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: Oscar, just FYI, your wording is very strong, and that is often not the most productive way to make your point. That said, to address some of the things you've raised in a couple of threads: >> If you think these are irrelevant points then you need to state why >> and should back it up with less

On Jul 30, 2013, at 12:41 PM, Stephen Lin wrote: >> Right. What's the point of all the effort devoted to MSVC++ ABI >> compatibility when Clang doesn't need it for being a top-notch C++ >> compiler on Windows? > > I brought up a similar point a little bit earlier, too.... > > It seems like the only necessary condition for being a first-class >