Menu
▾
▴
mingw-users
|
From: Kirk J. <kir...@gm...> - 2013-07-15 19:49:22
|
>> for the impatient user >> how wishes to down- >> load the installer w/o >> digging into the Navigation >> menu. > >Again, you must mean www.mingw.org? That's the page I started with and I too found it a little annoying that it wasn't obvious where to download the files. Not really a big deal but easy to fix probably. |
|
From: Felipe G. N. <fgn...@gm...> - 2013-07-15 14:34:05
|
mingw-get-setup.exe shouldn't expand input path "C:\progra~1\MinGW" into "C:\program files\MinGW". |
|
From: Kirk J. <kir...@gm...> - 2013-07-15 14:42:31
|
> mingw-get-setup.exe shouldn't > expand input path "C:\progra~1\MinGW" > into "C:\program files\MinGW". What should it be? |
|
From: Earnie B. <ea...@us...> - 2013-07-15 19:37:45
|
On Mon, Jul 15, 2013 at 10:33 AM, Felipe G. Nievinski wrote: > mingw-get-setup.exe shouldn't > expand input path "C:\progra~1\MinGW" > into "C:\program files\MinGW". Even if it didn't there is no guarantee that some other program is not going to be confused. Bottom line, DO NOT INSTALL INTO PATHS WITH SPACES. You have been warned, it will most likely come a bite you at some point during your development process. -- Earnie -- https://sites.google.com/site/earnieboyd |
|
From: Keith M. <kei...@us...> - 2013-07-15 21:14:03
|
On 15/07/13 15:33, Felipe G. Nievinski wrote: Posted without an appropriate subject header: please read the discourse on etiquette, at http://www.mingw.org/lists.shtml I normally delete such messages, without reading them. I presume that you intended this for the mingw-get maintainer, and I am he; you are extremely lucky that I noticed that this was related, and didn't deal with as I normally would. > mingw-get-setup.exe shouldn't > expand input path "C:\progra~1\MinGW" > into "C:\program files\MinGW". Complain to Microsoft. It isn't mingw-get-setup.exe which does this, explicitly; it is a feature of Microsoft's SHBrowseForFolder API. Yes, mingw-get-setup.exe does use this API; that is not going to change. FWIW, mingw-get-setup.exe does not prohibit installation into the 'C:\Program Files\...' hierarchy; however, this is such a bad idea, that mingw-get-setup.exe does strenuously discourage it. -- Regards, Keith. |
|
From: Greg C. <chi...@mi...> - 2000-10-23 02:53:31
|
camilo ramos wrote: > > I have trouble compiling OLE support for vim-5.6 with mingw gcc > -2.95.2. The object must be compiled with g++. > The errors are of the form: > > oaidl.h:86: syntax error before `;' > oaidl.h:94: syntax error before `*' > oaidl.h:98: syntax error before `*' > oaidl.h:109: `VT_ERROR' was not declared in this scope > oaidl.h:109: enumerator value for `SF_ERROR' not integer constant [...] > > so my question is, are there any flags or defines that could be usesd > to prevent this? Can g++ do it at all? I don't use OLE, but my understanding is that you need -fvtable-thunks to use it--yet that option can cause severe problems with multiple inheritance, which won't be fixed before gcc version 3.0 . However, the errors you report seem to suggest a missing header. |
|
From: Paul M. <gu...@mo...> - 2000-10-23 19:49:52
|
From: Greg Chicares > I don't use OLE, but my understanding is that you need > -fvtable-thunks > to use it--yet that option can cause severe problems > with multiple inheritance, which won't be fixed before > gcc version 3.0 . However, the errors you report seem > to suggest a missing header. Are there any timescales yet for gcc 3.0, and more importantly for the mingw version of gcc 3.0? Thanks, Paul. |
|
From: Jeff S. <jef...@ap...> - 2000-10-23 22:53:21
|
Paul Moore wrote: > Are there any timescales yet for gcc 3.0 There are several major milestones to complete before 3.0. See the release criteria at: http://gcc.gnu.org/gcc-3.0/criteria.html The new C++ ABI is the most significant of these... I'm hoping to see 3.0 appear within six months, but who knows? > and more importantly for the mingw version of gcc 3.0? Win32 changes are merged into the CVS trunk. Hopefully nothing will be necessary besides download & build. If you look at the criteria page, you'll see Cygwin is one of the secondary testing platforms. Mingw is not listed, but that doesn't prevent anyone from testing and providing feedback, it just means mingw won't be an important consideration for release. If anybody has mingw patches for gcc devel sources, now is the time to submit them. -- Jeff Sturm jef...@co... |
Thanks for helping keep SourceForge clean.
X