From: Frank H. <fr...@ph...> - 2010-08-27 14:11:16
|
Niklas Holsti wrote: > One reason for "minority-language" users to install the C compiler, in > addition to their favourite language, is that it is often necessary to > write C-code wrappers in order to call library functions that depend > heavily on C #include files and macros in their interfaces. And there are languages (Oberon/OOC) which are compiled to C as intermediate code. -- Frank Hrebabetzky Tel. (48) 3239 2258 Photonita Ltda. http://www.photonita.com.br Brazil |
From: Charles W. <cwi...@us...> - 2010-08-30 05:56:55
Attachments:
mingw-get-inst-src.tar.gz
|
On 8/26/2010 11:59 AM, Charles Wilson wrote: > That's > why I proposed a simple GUI wrapper whose job is to: > > 1) install mingw-get in the user-selected location > (note: using the %R mechanism, we don't even need to modify > the profile.xml) > > 2) execute mingw-get itself with the desired arguments, driven > by gui selections. For this stop-gap, I propose something VERY > simple, without a lot of flexibility. Notwithstanding the > capabilities of mingw-get to (once Cesar is done) install either > gcc3 or gcc4, the stop-gap GUI installer will be only able to > install one: gcc4-latest [1]. But, the user can select which > major languages to install: > > MinGW GCC Version 4 C compiler: always installed > MinGW GCC Version 4 C++ compiler: optional > MinGW GCC Version 4 Fortran compiler: optional > MinGW GCC Version 4 Objective C compiler: optional > MinGW GCC Version 4 Ada compiler: optional > MinGW Make: optional > MSYS Base Package: optional > > Note that MSYS is not very granular. You either don't install it, > or you get the entire msys-base meta package. Nothing in between, > and no GUI mechanism to add other elements. > > So, if all elements are selected, the GUI would invoke mingw-get as: > 'mingw-get gcc g++ gfortran objc ada make msys-base' > and report status back to the user. It could then create a desktop > shortcut for msys if it was installed, and update the system $PATH (most > GUI installer toolkits allow this sort of thing fairly easily). I have a working prototype of this installer. I've attached the source code; you can follow the instructions in the .iss file to build it yourself. I'm not publishing the actual binary installer yet, because: First, I'm using some hacked-together .xml manifests that aren't official. These are also in the attached tarball (basically use 'mingw-get update' to download the official ones, then copy these over the top). Second, I'm using a CVS version of mingw-get, which calls itself 0.1-alpha-3, but Keith hasn't officially blessed current CVS *as* 0.1-alpha-3, so... The point is, once the manifests are finalized, and mingw-get-0.1-a-3 is released, this installer can be rolled out very quickly. -- Chuck |
From: Keith M. <kei...@us...> - 2010-08-30 21:27:43
|
On Monday 30 August 2010 06:55:58 Charles Wilson wrote: > I have a working prototype of this installer. I've attached the > source code; you can follow the instructions in the .iss file to > build it yourself. > > I'm not publishing the actual binary installer yet, because: ... > [...snip...] > ... I'm using a CVS version of mingw-get, which calls itself > 0.1-alpha-3, but Keith hasn't officially blessed current CVS *as* > 0.1-alpha-3, so... I have now :) -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2010-08-30 22:04:54
|
On Monday 30 August 2010 06:55:58 Charles Wilson wrote: > I'm using some hacked-together .xml manifests that aren't official. A word of caution... At least some of these hacked manifests lack proper replacements for the issue number template (issue="@YYYYMMDDNN@"). If loaded as they are, into an installed mingw-get tree, mingw-get will refuse to update them when the official releases are provided, and indeed forever :( -- Regards, Keith. |
From: Charles W. <cwi...@us...> - 2010-08-30 22:19:35
|
On 8/30/2010 6:04 PM, Keith Marshall wrote: > On Monday 30 August 2010 06:55:58 Charles Wilson wrote: >> I'm using some hacked-together .xml manifests that aren't official. > > A word of caution... > > At least some of these hacked manifests lack proper replacements for > the issue number template (issue="@YYYYMMDDNN@"). If loaded as they > are, into an installed mingw-get tree, mingw-get will refuse to update > them when the official releases are provided, and indeed forever :( I know, that's why I want to get something (with the @YYYYMMDDNN@ stuff correctly in place) committed, and then published to mingw.org with the correct 2010090100 or whatever replacement. Then I'll use THOSE files in the InnoSetup installer. You've basically hit on the reason I didn't post the .exe of my InnoSetup package. -- Chuck |
From: Erwin W. <wat...@xs...> - 2010-08-29 19:54:14
|
Keith Marshall schreef, Op 26-8-2010 17:19: > My biggest concern, with *any* of these so-called wizard style GUI installer > frameworks, is that they lack scalability. There is considerably more to > MinGW than just GCC-4, (or GCC-3). Will any user, contributing such an > installer, do so in a format which can deliver *every* package available > from MinGW? Including optional add-ons? And, respecting the dependencies > which each has on others? While retaining the flexibility and scalability > to add new, perhaps previously unknown packages to the distributable > inventory at short notice? That's the promise of mingw-get, (and from > a download and install perspective it *already* delivers reasonably well); > it is comparitively much easier to write a few lines of XML to describe a > new package to mingw-get, than to recode an NSIS type installer script. > > I like Cygwin's setup.exe very much. Can't this be reused for MinGW/MSYS? It has everything we are looking for, isn't it? It seems to be open source: http://sourceware.org/cygwin-apps/setup.html regards, -- Erwin Waterlander |
From: Charles W. <cwi...@us...> - 2010-08-29 20:21:17
|
On 8/29/2010 3:53 PM, Erwin Waterlander wrote: >> > I like Cygwin's setup.exe very much. Can't this be reused for > MinGW/MSYS? It has everything we are looking for, isn't it? Not really. It does not support multiple installation roots (which we need to support installs of MinGW proper, and MSYS installations). It also can't support using multiple remote repositories simultaneously -- which we (will) need for installing 3rd-party libraries and such. Cygwin is a self-contained little world; notwithstanding the cygwin-ports project, they don't like "3PP's" (Third Party Perverts^WProviders). We do. Or we would, if we had any -- and hopefully mingw-get and its GUI successor will support, encourage, and enable that. > It seems to be open source: http://sourceware.org/cygwin-apps/setup.html Sure, it's GPL. In the past, XEmacs used an adaptation of it to install their system; now it seems they have switched to InnoSetup. -- Chuck |
From: Keith M. <kei...@us...> - 2010-08-29 20:23:31
|
On Sunday 29 August 2010 20:53:56 Erwin Waterlander wrote: > I like Cygwin's setup.exe very much. Can't this be reused for > MinGW/MSYS? Perhaps it could be, but I don't like it at all; IMO it is utterly hideous. -- Regards, Keith. |
From: Andy K. <and...@gm...> - 2010-08-29 21:39:01
|
On 29 August 2010 20:53, Erwin Waterlander wrote: > Keith Marshall schreef, Op 26-8-2010 17:19: >> My biggest concern, with *any* of these so-called wizard style GUI installer >> frameworks, is that they lack scalability. There is considerably more to >> MinGW than just GCC-4, (or GCC-3). Will any user, contributing such an >> installer, do so in a format which can deliver *every* package available >> from MinGW? Including optional add-ons? And, respecting the dependencies >> which each has on others? While retaining the flexibility and scalability >> to add new, perhaps previously unknown packages to the distributable >> inventory at short notice? That's the promise of mingw-get, (and from >> a download and install perspective it *already* delivers reasonably well); >> it is comparitively much easier to write a few lines of XML to describe a >> new package to mingw-get, than to recode an NSIS type installer script. >> >> > I like Cygwin's setup.exe very much. Can't this be reused for > MinGW/MSYS? An attempt at that exists at http://sourceforge.net/projects/takeoffgw. The "Cygwin-like package manager" mentioned there is just a mildly patched version of Cygwin's setup.exe. A lot of work appears to have gone into repackaging MinGW, MSYS and lots of third-party stuff for setup.exe, but there've been no updates in the last couple of months. I think that makes it three partially working MinGW/MSYS install solutions, plus the manual download and various hacks based around that ... Andy |