Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: rolandixor on June 10, 2007, 11:25:40 pm
-
They don't work. full stop. :P :P :P :P :P :P :D :D :D :D 8)
-
User error. Full stop. :roll:
It's a good point though; everyone who uses the devpak module has to first press a little drop-down arrow in the Update Server box, and then select "devpaks.org Community Devpaks". There is also an issue that requires the "Use Cache" checkbox to be checked.
It would probably make a lot more sense to re-order the drop-down list so that devpaks.org is the default on top choice. It is the only one that works.
-
It should be noted that devpaks aren't precisely a top priority, either :)
This is visible from the fact that most recent non-api-change update to this non-core plugin dates 14 months back. Eventually, devpak support will probably make its way to core functionality, but only as a second-class priority.
-
I was going to make a DevPak but want to make sure that I'm using the latest tool for creating it. I also have DevC++ and it's PakMaker is only on version 0.4 . Is there a plan make an updated PakMaker equivalent?
The ./configure process for the Agar graphical user interface doesn't work very well with MSYS or Cygwin so I'd like to know what I'm supposed to do to make an archive of the binaries that people can use. SDL and OpenGL are some of the most portable code I know of.
-
DevPaks are special .tar.bz2 archive. Special in the sense they contain one file description file.
So you can create a .tar.bz2 archive with that special file and then rename it as .devpak file. No special creator is needed.