User forums > General (but related to Code::Blocks)
New unofficial installer for Code::Blocks available for testing!
troels:
--- Quote from: Michael on April 20, 2006, 12:59:57 pm ---GCC 3.4.4 works fine, but I would use instead GCC 3.4.5 with wxWidgets (should be a bit more up to date).
--- End quote ---
Thanks! I'll stick with 3.4.5 for the time being then.
Greetings
Troels
artoj:
--- Quote from: Pharaoh Atem on March 26, 2006, 01:57:20 am ---As far as I know, Inno Setup does not support web patching
--- End quote ---
It does: Inno Setup Download DLL
Though, maybe a better solution would be use this wxWidgets autoupdate project: http://wxcode.sourceforge.net/docs/webupdate/index.html
Conan Kudo:
--- Quote from: artoj on April 20, 2006, 07:18:35 pm ---
--- Quote from: Pharaoh Atem on March 26, 2006, 01:57:20 am ---As far as I know, Inno Setup does not support web patching
--- End quote ---
It does: Inno Setup Download DLL
Though, maybe a better solution would be use this wxWidgets autoupdate project: http://wxcode.sourceforge.net/docs/webupdate/index.html
--- End quote ---
Note that I said, "Web Patching", I did not say, "Web downloading"... I am aware of Inno Setup's Download DLL, however, it has problems with proxies, handlers, and system anonymizers... It seems NSIS's plugin NSISdl seems to work perfectly with it... Although, probably the only component planned for web downloading would be MinGW...
--- Quote from: troels on April 20, 2006, 12:46:26 pm ---
--- Quote from: Pharaoh Atem on April 20, 2006, 02:45:29 am ---I used an ANSI build so our good Windows 9x users can test it...
--- End quote ---
Well, my system is Unicode Windows, running Ansi makes Windows do nonstop string conversions (Ansi<->Unicode<->Ansi), not so great. ['National' chars might even end up garbled.]
Surely the primary target group cannot be Windows 9x users. Secondary target group at best. Deploying one's stuff on Windows 9x is one thing, but to use such an 'operative system' to develop it on is quite another matter. In my experience you cannot expect to do development stuff (esp. running the debugger, a heavyhanded demanding program) [on Windows 9x] - without endless rebooting. IMHO it's better to endorse use of 'proper' operating systems to developers, by providing Unicode builds first, Ansi a - distant - second.
--- End quote ---
The final installation script will contain a unicode build, and I hope by then a libunicows build is made so that there can be one build for both Windows 9x and Windows XP...
--- Quote from: Michael on April 20, 2006, 12:52:55 am ---IMHO, it is better to install MinGW separately :). It is easy and does not require specific knowledge
--- End quote ---
ALL COMPONENTS ARE BEING PACKAGED AS BEING ABLE TO DOWNLOAD FROM THE INTERNET!
I originally planned for only MinGW, but I decided to make everyone's life easier and componentize the packaging itself to allow all the components to be able to be downloaded from the internet and installed...
--- Quote from: Pharaoh Atem on April 16, 2006, 04:39:52 am ---Problems/Planned Features/Unfortunate Side-effects:
* Splash is dithered to 256 colours, working on getting it to work properly
--- End quote ---
I figured out the problem with it, unfortunately, I need the someone to build the C::B transparent logo directly from the source image, because the PNG -> GIF conversion makes it dither to 256 colors... It would be great if whoever originally made the new C::B splash logo could make it as a GIF image that is transparent, because the splash plugin only supports GIF images... I know SOMEONE has the original source, I just do not know who...
EDIT: I am most likely going to leave the splash alone, it seems impossible...
killerbot:
allrigthy some feedback.
this is what I have done :
1) start install (checked codecompletion)
--> noticed some stuff got into Program files\common files\NSIS Installation Data
2) ran installed CB
3) add/remove programs -> uninstall
---> the installation dir is empty but still containes the complete directpry structure --> BUG
---> that NSis stuff is still there
overall impression : looks good, only downloading that weird named files is confusing for the user I think?
Conan Kudo:
--- Quote from: killerbot on April 29, 2006, 07:44:56 pm ---allrigthy some feedback.
this is what I have done :
1) start install (checked codecompletion)
--> noticed some stuff got into Program files\common files\NSIS Installation Data
2) ran installed CB
3) add/remove programs -> uninstall
---> the installation dir is empty but still containes the complete directpry structure --> BUG
---> that NSis stuff is still there
overall impression : looks good, only downloading that weird named files is confusing for the user I think?
--- End quote ---
complete directory stucture bug is fixed, build uploaded shortly... The NSIS Installation Data folder keeps a copy of the installer to retain MSI-level functionality... Clicking on Change or activating the installer manually will cause a special dialog to pop up... The NSIS stuff is being investigated... The names are actually package IDs, the packages have names, but they contain IDs as well... The installer copies them to temp dirs as package IDs...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version