On Sun, Jul 10, 2011 at 9:08 PM, Igor Stasenko <[hidden email]> wrote:
yes, please. |
In reply to this post by Igor Stasenko
Igor I think you have to separate out the folks who want the one-click-experience from the folks who want to know all the steps involved. You and I fit into the "know all the steps" But oddly and this at times seems strange to me, there are people who want to do the build, yet from the 'one-click-experience' Those from my past experience out-number us. So yes, one fat archive and punch GO. Obviously you can temper this by saying, look if you want to do it all manually then these are the steps, and expect at any point in time they will fail as the third parties involved will move the carpet from under you. On Sun, Jul 10, 2011 at 9:08 PM, Igor Stasenko <[hidden email]> wrote: > > On 11 July 2011 03:25, John McIntosh <[hidden email]> wrote: >> >> Igor, I am reminded that about 8 years back building the Mac VM took >> about 20 steps. That I found was about 19 steps too long for an >> "average" user to follow. >> No disrespect to the folks attempt to build this, but when you have 20 >> steps then there is just too much chance for a human to fail or for >> the other third parties to >> throw cold water on you. >> >> Unfortunately solving this can take a while, I'm sure I struggled for >> a month or more refactoring the process into a more simple number of >> steps. >> So at each point ask youself what can go wrong, and why do I need to >> have something manual here? Should there just be a sole command to do >> it all? >> > Look, there are only 4 steps for installing mingw on windows > (http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-using-git-and-cmakevmmaker/) > > And JJ Stevens refers to step 5.. so i really don't have any clue what > he's doing. > > As for simplifying even more.. One could package everything in big fat > archive and make it downloadable. > But then it is not 'from scratch' , it will be 'from fat archive'. :) > > -- > Best regards, > Igor Stasenko AKA sig. > -- =========================================================================== John M. McIntosh <[hidden email]> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com =========================================================================== |
On 11 July 2011 04:28, John McIntosh <[hidden email]> wrote: > > Igor I think you have to separate out the folks who want the > one-click-experience from the folks who want to know all the steps > involved. > You and I fit into the "know all the steps" > But oddly and this at times seems strange to me, there are people who > want to do the build, yet from the 'one-click-experience' > Those from my past experience out-number us. > So yes, one fat archive and punch GO. > > Obviously you can temper this by saying, look if you want to do it all > manually then these are the steps, and expect at any point in time > they will fail as the third parties involved will move the carpet from > under you. > Yeah. World is moving, everything changes. Ones who cannot adopt to changes won't survive. So, making it in stone is not my goal. That's why i don't like an idea with fat archive. -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by JJ Stevens
On 11 July 2011 04:24, JJ Stevens <[hidden email]> wrote: > > > > On Sun, Jul 10, 2011 at 9:08 PM, Igor Stasenko <[hidden email]> wrote: >> >> As for simplifying even more.. One could package everything in big fat >> archive and make it downloadable. >> But then it is not 'from scratch' , it will be 'from fat archive'. :) >> > > > yes, please. > > managed by mine. as well as cmake and git. There is already prepackaged files.. why i should duplicate effort and do it myself? i tried to install everything from scratch.. it works. Download this: http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20110530/mingw-get-inst-20110530.exe/download Here what i have installed: Installing: mingw-get pkginfo C Compiler C++ Compiler MSYS Basic System MingGW developer kit Using pre-packaged repository catalogues (20110530) Destination location: g:\MinGW -- Best regards, Igor Stasenko AKA sig. |
On 11 July 2011 05:41, Igor Stasenko <[hidden email]> wrote: > On 11 July 2011 04:24, JJ Stevens <[hidden email]> wrote: >> >> >> >> On Sun, Jul 10, 2011 at 9:08 PM, Igor Stasenko <[hidden email]> wrote: >>> >>> As for simplifying even more.. One could package everything in big fat >>> archive and make it downloadable. >>> But then it is not 'from scratch' , it will be 'from fat archive'. :) >>> >> >> >> yes, please. >> >> > no, im not going to do that. MSys is a separate project which are not > managed by mine. as well as cmake and git. > There is already prepackaged files.. why i should duplicate effort and > do it myself? > > > > i tried to install everything from scratch.. it works. > > Download this: > http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20110530/mingw-get-inst-20110530.exe/download > > Here what i have installed: > > Installing: > mingw-get > pkginfo > C Compiler > C++ Compiler > MSYS Basic System > MingGW developer kit > > Using pre-packaged repository catalogues (20110530) > > Destination location: > g:\MinGW > To make it clear: so, this is all you need to get going with msys + mingw + gcc. Next step is installing cmake and git. NO extra sub-sub-steps from msys wiki page :) > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig. |
Mariano, can you please change the instructions to avoid further confusion. To install mingw+msys using single, painless step, one should download latest installer from here: http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/ Today, the mingw-get-inst-20110530 is latest one. -- Best regards, Igor Stasenko AKA sig. |
On Mon, Jul 11, 2011 at 3:19 PM, Igor Stasenko <[hidden email]> wrote:
Done. I've added those last 2 sentences. -- -- Mariano http://marianopeck.wordpress.com |
Free forum by Nabble | Edit this page |