|
|
Home » Developing U++ » Releasing U++ » Releasing in Win32 xp
Re: Releasing in Win32 xp [message #16087 is a reply to message #16083] |
Tue, 27 May 2008 14:31   |
bytefield
Messages: 210 Registered: December 2007
|
Experienced Member |
|
|
luzr wrote on Tue, 27 May 2008 14:00 |
mdelfede wrote on Tue, 27 May 2008 01:54 |
Maybe he meant if he should include mingw on release (which makes it quite big file to download) or without it, not if he should release both mingw and MS compiled versions.
|
FYI, Win32 U++ is ALWAYS compiled with MSC (because it produces much smaller .exe).
Mirek
|
It is always compiled with MSC if maintainer do that(this version is also compiled with MSC), but guess distributing mingw with every svn builds is inutile and guess we cannot have on server more than 15 packages because of low storage space.
Alternatively we can have a single mingw installer near svnbuilds and who need it to can download it from there, and btw which programmer make programs without having a compiler installed on system?!?, let be serious and a new programmer doesn't begin using U++ until he know C++ and he cannot learn C++ without a compiler. And the mainly used compilers on windows are MSC ones and MinGW.
And i think every newcomer to U++ which use windows is reading this, where is explained clearly that you must have installed a compiler on your system.
So my proposal are to have mingw distributed with stable and official releases and one mingw package (installer) in svnbuilds for programmers who use latest svn builds (have it as a separate packages not bundled with upp svn packages), in fact the mingw is always the same, just the upp and theide is changing, so we must provide just the changes.
cdabbd745f1234c2751ee1f932d1dd75
|
|
|
|
|
Re: Releasing in Win32 xp [message #16091 is a reply to message #16089] |
Tue, 27 May 2008 16:27   |
bytefield
Messages: 210 Registered: December 2007
|
Experienced Member |
|
|
Quote: | We have 2GB total, 500MB used. Means there is 1.5GB free...
|
Well, if you say so... But two weeks ago i couldn't upload my package because of space problem until i've removed others older packages.
cdabbd745f1234c2751ee1f932d1dd75
|
|
|
|
Re: Releasing in Win32 xp [message #16094 is a reply to message #16088] |
Tue, 27 May 2008 20:10   |
mdelfede
Messages: 1308 Registered: September 2007
|
Ultimate Contributor |
|
|
luzr wrote on Tue, 27 May 2008 14:56 | I guess you are missing the point here....
I agree that mingw release is somewhat redundant, EXCEPT for testing purposes. We already had situations when everything was OK, but something was broken in mingw release.
By releasing mingw we should be able to catch these bugs early.
Mirek
|
Well, I don't say we must suppress mingw releases, but right the opposite... mingw upp release IS useful for svn.
What I don't see so useful is to deploy complete mingw stuff on each svn build.
I don't know exactly how big is MINGW distrib, but I guess that can be good 10 MB of space... about the same that the complete upp build in linux.
IMHO, mingw should be separated from upp build, as it doesn't belong to it. Also people using wxwidgets usually don't deploy on each build the complete wxwidgets stuffs for the same reason.
Speaking about disk storage, I did find also the problem of disk space 2 weeks ago; for that reason I started to erase old builds when adding news ones. Maybe it's really a quota problem.
Max
|
|
|
|
|
Re: Releasing in Win32 xp [message #16102 is a reply to message #16101] |
Wed, 28 May 2008 00:20   |
 |
mirek
Messages: 14257 Registered: November 2005
|
Ultimate Member |
|
|
[quote title=mdelfede wrote on Tue, 27 May 2008 17:58]luzr wrote on Tue, 27 May 2008 23:19 |
mdelfede wrote on Tue, 27 May 2008 14:10 |
Speaking about disk storage, I did find also the problem of disk space 2 weeks ago; for that reason I started to erase old builds when adding news ones. Maybe it's really a quota problem.
|
Strange, I have just checked, it was at 350MB used and 750MB free.
Readjusted to 1400MB free....
Mirek
|
Really strange... when the problem arose, folder had some 30 64 bit builds plus 5-6 32 bit builds, so about 400 MB maximum.
[quote]
Ops, sorry. Wrong info, I meant it had 750MB TOTAL, so 400MB maximum makes perfect sense....
Quote: |
BTW, how many 'previous' svn releases do you think it'll be wise to keep ?
|
One if everything works 
Mirek
|
|
|
|
Re: Releasing in Win32 xp [message #16105 is a reply to message #16094] |
Wed, 28 May 2008 08:03   |
|
mdelfede wrote on Tue, 27 May 2008 21:10 |
luzr wrote on Tue, 27 May 2008 14:56 | I guess you are missing the point here....
I agree that mingw release is somewhat redundant, EXCEPT for testing purposes. We already had situations when everything was OK, but something was broken in mingw release.
By releasing mingw we should be able to catch these bugs early.
Mirek
|
Well, I don't say we must suppress mingw releases, but right the opposite... mingw upp release IS useful for svn.
What I don't see so useful is to deploy complete mingw stuff on each svn build.
I don't know exactly how big is MINGW distrib, but I guess that can be good 10 MB of space... about the same that the complete upp build in linux.
IMHO, mingw should be separated from upp build, as it doesn't belong to it. Also people using wxwidgets usually don't deploy on each build the complete wxwidgets stuffs for the same reason.
Speaking about disk storage, I did find also the problem of disk space 2 weeks ago; for that reason I started to erase old builds when adding news ones. Maybe it's really a quota problem.
Max
|
Distribution with mingw is 16.8Mb and wothout mingw is 8.4Mb (for svn.270). I thing to separate only mingw reelase or can put documentation how install mingw and add an wizzard in Build Methods, for news user it will helpfull!
John.
|
|
|
|
Re: Releasing in Win32 xp [message #16114 is a reply to message #16107] |
Wed, 28 May 2008 15:36   |
|
luzr wrote on Wed, 28 May 2008 11:29 |
tojocky wrote on Wed, 28 May 2008 02:03 |
Distribution with mingw is 16.8Mb and wothout mingw is 8.4Mb (for svn.270). I thing to separate only mingw reelase or can put documentation how install mingw and add an wizzard in Build Methods, for news user it will helpfull!
|
There already is wizard (Automatic setup).
Also, "our mingw" is way different from regular mingw. Different compiler version, our linker etc... A lot to test.
(BTW, I hope you are getting the "mingw" from U++ beta2 when creating the release).
Mirek
|
For sure I have with "mingw" from 2008.1beta... and when I creating release with "mingw" i get from 2008.1beta. If is other "mingw" for u++ then where can I get?
|
|
|
Re: Releasing in Win32 xp [message #16210 is a reply to message #16114] |
Mon, 02 June 2008 12:43   |
|
When I build svn.277 release I have this error:
Quote: |
D:\upp\MakeInstall\win32\upp.install.final\u\uppsrc\CtrlCore \Win32Wnd.cpp(286) :
error C2556: 'void Upp::Ctrl::IsCompositedGui(void)' : overloaded function diff
ers only by return type from 'bool Upp::Ctrl::IsCompositedGui(void)'
d:\upp\makeinstall\win32\upp.install.final\u\uppsrc\ctrlcore \CtrlCore.h(
1299) : see declaration of 'Upp::Ctrl::IsCompositedGui'
D:\upp\MakeInstall\win32\upp.install.final\u\uppsrc\CtrlCore \Win32Wnd.cpp(286) :
error C2371: 'Upp::Ctrl::IsCompositedGui' : redefinition; different basic types
d:\upp\makeinstall\win32\upp.install.final\u\uppsrc\ctrlcore \CtrlCore.h(
1299) : see declaration of 'Upp::Ctrl::IsCompositedGui'
|
|
|
|
|
|
Re: Releasing in Win32 xp [message #16229 is a reply to message #16225] |
Tue, 03 June 2008 11:56   |
|
masu wrote on Tue, 03 June 2008 11:11 | Another error:
In file included from d:\programs\upp-svn\uppsrc\Core\heapdbg.cpp:7:
d:\programs\upp-svn\uppsrc\Core\HeapImp.h:164: error: thread-local storage not supported for this target
WinXP, Mingw 3.4.5, SVN rev 278
Regards,
Matthias
|
Did you used mingw from u++ release or other?
|
|
|
|
|
Re: Releasing in Win32 xp [message #16347 is a reply to message #16065] |
Mon, 09 June 2008 20:14   |
|
tojocky wrote on Mon, 26 May 2008 15:16 | The modified source code of MakeInstall3 is here or in Attachment!
|
Ok, I commited changes to uvs. I always had 7z and umk in system path that's why there was no way to configgure it from gui.
|
|
|
Goto Forum:
Current Time: Sun May 11 14:58:50 CEST 2025
Total time taken to generate the page: 0.03065 seconds
|
|
|