User forums > General (but related to Code::Blocks)

New unofficial installer for Code::Blocks available for testing!

(1/8) > >>

Conan Kudo:
I realized something that could help distribute C::B updates better: patching system. As far as I know, Inno Setup does not support web patching, so I am devising an installer with a nightly that could be modified to accept patches from the Code::Blocks site or from a file locally... Still working on getting the filesize down to 13MB as it is for the RC2. While I am working that out, I have a question: Does the nightlies contain anything extra in their binaries that would not be in the final version? Because its worrying me that the lowest I can get it, with the MinGW toolkit included is 23MB.... Although there might be enough benefit with the patching system, I doubt I will even attempt to send in my installer source if I cannot figure out a way to justify that additional 10MB in there.... If I can, and the patching system works, then I will submit my installer source... Otherwise, it probably will remain a secret on my computer forever....

sethjackson:
Uhhh I think this is planned for the next release.  :? A C::B version of DevPacks or something. Maybe I'm confused here.....  :P

EDIT:

Or do you mean source code diffs/patches instead of binary "patches".......

Conan Kudo:
I mean both... The devpak thing is a great idea, but there is certain restrictions, such as the fact that it requires Code::Blocks to be running, so patching the actual program is out of the question, along with the DevPak plugin, etc. My idea uses the installer I am developing to connect to the website, or use a patchfile locally to apply directly to the program or anything else. The advantage of this is that it is impossible to have filelocks on it, and nonadmins can hotpatch C::B right in, while only the HIGH ADMIN can override locks, and its easier in Vista, but difficult in XP. DevPaks are great for plugins, but not for the core or the MinGW toolkit, except for includes, apis, libs, etc. the actual core files would be handled by the patching system... It is also possible to diff source code and have autobuild as well... The advantage of the web patch system is that nightlies could be applied to older nightlies with simply running the installer and telling it to update... Code::Blocks could be hooked to start the autoupdater from a menu item, making it easier to update essential parts of Code::Blocks....

P.S: I'm not really good at C/C++ programming, so I figure I can help out the development in this way...

idcarlos:
Hi.

NSIS have a plugins to connect to Internet and make patches.
I have made some NSIS instalers to other tools, but never with Internet update.


--- Code: ---Code::Blocks could be hooked to start the autoupdater from a menu item, making it easier to update essential parts of Code::Blocks....
--- End code ---
Maybe If I have free time, I'll made a .bat to execute this http://csautoupdater.sourceforge.net/. Easy to implement, no need programing, only configuration. But need .NET framework to run.

sethjackson:

--- Quote from: idcarlos on March 26, 2006, 10:54:24 am ---But need .NET framework to run.

--- End quote ---

I think that is a no go. .NET is not cross-platform.

Navigation

[0] Message Index

[#] Next page