|
From: Keith M. <kei...@us...> - 2011-05-08 16:59:58
|
On 08/05/11 14:59, stn021 wrote: > For a portable MinGW the launcher of portableapps is a very elegant > solution, and it would be my first choice too. I am surprised to see > that portableapps.com so far offers only very rudimentary support for > portable MinGW. I am sure that a lot of people would have use for > that. I wasn't even aware that the PortableApps.com folks offered their own flavour of MinGW/MSYS. I just did a search on their site, and sure enough, yes, there is something there, (although they seem to have dropped MSYS from their offering, which appears from reading their development notes, to be focussed on GCC3). While I applaud their efforts, it is a shame that they have just ploughed in on their own, without so much as a heads-up here; I'm sure that, with appropriate dialogue and co-operation, the end result could be so much better. FWIW, I am not using their build. Barring the drive letter mapping, putting things in the correct location within the PortableApps.com directory framework just works, without needing any heavy development, (such as they suggest is needed). Even the drive letter mapping, I'm convinced, is easily and quickly soluble, (with an entirely MSYS based solution). IMO, their development plan is overkill, but then, perhaps their objectives differ from mine -- for me, MSYS as a foreign app within the PortableApps.com framework seems completely sufficient, (but I have no interest in Code::BlocksPortable or EclipsePortable integration, or some such, which may be their goal). -- Regards, Keith. |