User forums > Nightly builds
The 27 April 2007 build is out.
TheTuxKeeper:
--- Quote from: Shade37337 on April 28, 2007, 12:45:11 pm ---Hi
I repeat my qeustion because now it's nearly two months since the last nightly build for suse has been released.
Why don't you release anymore a nightly build for suse (and fedora) ?
Or why do you alsways list a link with "not yet" behind for these release?
if you don't release these packages, you can remove these links, i think .....
shade->greetz();
--- End quote ---
I'm quite busy atm (studying and working). The last suse nightly is from the 19th. I think I forgot killerbot to write that it's uploaded.
If you take a look at the project files (https://developer.berlios.de/project/showfiles.php?group_id=5358), you'll see that there's only one month between the last two releases (14th march and 19th april) ;)
The last builds failed because some Makefiles had some typos. The ubuntu builds worked because I use a make dist tarball. Not all required headers/files came into the tarball and building failed (that's why I take this way building the packages to see these errors) ;) Additionally my little time to fix the issues. I hope I'll have more time from now on :) Have to switch the build machine, too (atm I still build on a machine that's 150km away from me ;) )
nice weekend and more frequently suse and fedora packages from now on :D
MVP:
--- Quote from: wxLearner on April 27, 2007, 10:17:41 pm ---Portable version for windows, including many libs, is here.
It includes:
* MinGW (Ogre edition, but with the new w32api-3.9 and the new mingw-runtime-3.12, and gdc-0.23 to allow compiling D programs)
* wxWidgets-2.8.3 (monolithic unicode shared/static/debug/release; ready to create projects with Code::Blocks and wxSmith)
* boost 1.33.1 (compiled as static and shared libraries against libstdc++ and against STLport-5.1.3)
* STLport-5.1.3
* Irrlicht 1.3
* cURL 7.16.2
* OpenSSL 0.98eand many other libraries.
This version of Code::Blocks is modified to allow portable "user templates" and the configuration files aren't stored directly near the exe, but in a folder, that is near the exe and is called config. If you have your own configuration of Code::Blocks (in your profile), your own configuration will be used. BACKUP your configuration and try the files from the config folder or use cb_share_config for importing. The config folder contains a configuration, that uses everything relatively (mostly by using the global variables feature of Code::Blocks and the builtin variables). All the extra libraries are in a folder, that is called extra-libs and resists in the MinGW directory.
If you want to use an usb-stick, you might want to look into the MinGW\extra-libs folder and delete the libraries, you don't need.
Happy coding :D
--- End quote ---
Awesome thanks, but can you find a different file host? That one is terrible.
dwelty:
Hey guys, I've been using 1.0rc2 ever since it came out, and I just tried a nightly (this one) yesterday for the first time. All I can say is wow! Nice job. :D
There are so many great improvements, and I'm really glad I made the switch.
I did want to mention one annoying bug though :P
Whenever I right click on a ".py" file and try to "Open With" -> "codeblocks", it doesn't work. CodeBlocks starts up, but does not open the file. I can change the extension to any number of other things (like ".oogabooga" or even ".txt") and it still won't work. However, when I change the extension to one CodeBlocks is associated with (like ".cpp"), CodeBlocks starts up and opens the file as intended.
I'm using Windows XP Pro SP2, and the April 27, 2007 nightly
Thanks for all your hard work guys! :D
Ceniza:
That's a well known issue, specially for Linux users. When I was trying to pinpoint the cause of the DDE problem I found the reason for that one too but I was a bit "afraid" to touch that piece of code, and now I lack the time to do so.
I'll try to get some time to work on it between tomorrow and the day after tomorrow.
Grom:
cool. BUT would be grate to have an installation. :?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version