|
|
Home » Community » U++ community news and announcements » Getting ready 2/2015
|
Re: Getting ready 2/2015 [message #45164 is a reply to message #45037] |
Mon, 21 September 2015 16:09 |
timsky
Messages: 3 Registered: September 2015 Location: Uzbekistan
|
Junior Member |
|
|
mirek wrote on Sun, 23 August 2015 11:18I would like to make another release this year.
- mingw-w64 should come with it (to create better out-of-box experience)
Will you add MinGW to nightly builds too? Probably MinGW will significantly increase installer size. Right now it is great that U++ is so small and there is no need to wait for hours donloading it on slow connections.
mirek wrote on Sun, 23 August 2015 11:18- To simplify things, I am considering to remove some toolchains from Win32 auto-setup. Ideally, only VS2015 and SDK7 (which is the only SDK still coming with C++ compiler) should be supported. Detection method should also be changed to rather scan directories than read from registry.
Are you going to remove build methods for VS 2005 - 2013?
Please do not do that
[Updated on: Mon, 21 September 2015 16:10] Report message to a moderator
|
|
|
Re: Getting ready 2/2015 [message #45167 is a reply to message #45164] |
Mon, 21 September 2015 16:23 |
|
mirek
Messages: 14039 Registered: November 2005
|
Ultimate Member |
|
|
timsky wrote on Mon, 21 September 2015 16:09mirek wrote on Sun, 23 August 2015 11:18I would like to make another release this year.
- mingw-w64 should come with it (to create better out-of-box experience)
Will you add MinGW to nightly builds too? Probably MinGW will significantly increase installer size. Right now it is great that U++ is so small and there is no need to wait for hours donloading it on slow connections.
Yes. I think mingw will add about 30MB to the download. I do not think it is a problem. But I can be persuaded to have "mingw-free" version...
Quote:
mirek wrote on Sun, 23 August 2015 11:18- To simplify things, I am considering to remove some toolchains from Win32 auto-setup. Ideally, only VS2015 and SDK7 (which is the only SDK still coming with C++ compiler) should be supported. Detection method should also be changed to rather scan directories than read from registry.
Are you going to remove build methods for VS 2005 - 2013?
Please do not do that
I am not going to remove build methods, just automatic setup. Or, as things are developing, "portable setup" (it looks like there will be no install, theide will reconfigure upon starting).
OTOH, at some point in the future, C++11 will likely lure us to require C++11 compiler. At that point, U++ will not be able to compile with pre VS2015 MS compilers...
Mirek
[Updated on: Mon, 21 September 2015 16:23] Report message to a moderator
|
|
|
|
Re: Getting ready 2/2015 [message #45170 is a reply to message #45167] |
Mon, 21 September 2015 19:29 |
Tom1
Messages: 1242 Registered: March 2007
|
Senior Contributor |
|
|
mirek wrote on Mon, 21 September 2015 17:23timsky wrote on Mon, 21 September 2015 16:09mirek wrote on Sun, 23 August 2015 11:18I would like to make another release this year.
- mingw-w64 should come with it (to create better out-of-box experience)
Will you add MinGW to nightly builds too? Probably MinGW will significantly increase installer size. Right now it is great that U++ is so small and there is no need to wait for hours donloading it on slow connections.
Yes. I think mingw will add about 30MB to the download. I do not think it is a problem. But I can be persuaded to have "mingw-free" version...
Quote:
mirek wrote on Sun, 23 August 2015 11:18- To simplify things, I am considering to remove some toolchains from Win32 auto-setup. Ideally, only VS2015 and SDK7 (which is the only SDK still coming with C++ compiler) should be supported. Detection method should also be changed to rather scan directories than read from registry.
Are you going to remove build methods for VS 2005 - 2013?
Please do not do that
I am not going to remove build methods, just automatic setup. Or, as things are developing, "portable setup" (it looks like there will be no install, theide will reconfigure upon starting).
OTOH, at some point in the future, C++11 will likely lure us to require C++11 compiler. At that point, U++ will not be able to compile with pre VS2015 MS compilers...
Mirek
Hi!
I'm all for portable installation, but I'm still dependent on MSC9: As I recall it, the Protect package from Max is dependent on that, and I'm dependent on Protect package... Is there any way to solve this issue? Looking forward, it would be great to have 64-bit support for Protect, but that's not possible with the current protection mechanism because of the compiler not supporting it.
Best regards,
Tom
|
|
|
Re: Getting ready 2/2015 [message #45171 is a reply to message #45170] |
Tue, 22 September 2015 11:57 |
|
mirek
Messages: 14039 Registered: November 2005
|
Ultimate Member |
|
|
Tom1 wrote on Mon, 21 September 2015 19:29mirek wrote on Mon, 21 September 2015 17:23timsky wrote on Mon, 21 September 2015 16:09mirek wrote on Sun, 23 August 2015 11:18I would like to make another release this year.
- mingw-w64 should come with it (to create better out-of-box experience)
Will you add MinGW to nightly builds too? Probably MinGW will significantly increase installer size. Right now it is great that U++ is so small and there is no need to wait for hours donloading it on slow connections.
Yes. I think mingw will add about 30MB to the download. I do not think it is a problem. But I can be persuaded to have "mingw-free" version...
Quote:
mirek wrote on Sun, 23 August 2015 11:18- To simplify things, I am considering to remove some toolchains from Win32 auto-setup. Ideally, only VS2015 and SDK7 (which is the only SDK still coming with C++ compiler) should be supported. Detection method should also be changed to rather scan directories than read from registry.
Are you going to remove build methods for VS 2005 - 2013?
Please do not do that
I am not going to remove build methods, just automatic setup. Or, as things are developing, "portable setup" (it looks like there will be no install, theide will reconfigure upon starting).
OTOH, at some point in the future, C++11 will likely lure us to require C++11 compiler. At that point, U++ will not be able to compile with pre VS2015 MS compilers...
Mirek
Hi!
I'm all for portable installation, but I'm still dependent on MSC9.
Best regards,
Tom
Builder is not going anywhere. Most likely even AutoSetup will be hidden somewhere in the menu....
Mirek
|
|
|
|
Goto Forum:
Current Time: Fri Sep 20 16:02:13 CEST 2024
Total time taken to generate the page: 0.03219 seconds
|
|
|