Code::Blocks Forums
User forums => Nightly builds => Topic started by: killerbot on February 16, 2015, 08:13:23 pm
-
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
Before you use a nightly make sure you understand how it works (http://forums.codeblocks.org/index.php/topic,3232.0.html).
A link to the unicode windows wxWidget dll for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw28u_gcc_cb_wx2812_gcc481-TDM.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/mingwm10_gcc481-TDM.7z
The 16 February 2015 build is out.
- Windows :
http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2015/CB_20150216_rev10120_win32.7z
- Linux :
none
The current SDK version is : 1.25.0
Resolved Fixed:
- fixed #123 HeaderFixup: use istream/ostream directly Move Edit
- compiler framework: add support for dedicated resource compiler options
- compiler framework: added support to disable dependency checks for #includes (intended ONLY for on C/C++ compilers!)
- at least report if loading an XRC resource failed
- FileManager: adds support for viewing diffs and browsing the history of a version controlled folder (currently supports GIT, SVN, BZR and HG)
- FileManager: 'show changed files only' -- flattens the tree of a directory under version control and shows only the files that have changed (currently only works for the working copy and still need to prune some of the right click menu options and disable drag n drop)
- FileManager: fixed crash if setting a folder to root which is under version control and where the VCS executables could not be run
- Compiler: applied patch by LETARTARE so misc. compiler events also provide the source ID of the wx event that caused the compiler operation
- FileManager: support for showing only commits with changes to a particular file
Regressions/Confirmed/Annoying/Common bugs:
-
as long as you see this message in full glory , it means the upload is not there yet. Once again SF is complete crap.
It's alive.
-
Svn r10118 is out since some days (rpm-builds only, debian-repo has 10111), r10120 is currrently compiling (status of rpm-build: https://copr.fedoraproject.org/coprs/jenslody/codeblocks/monitor/ (https://copr.fedoraproject.org/coprs/jenslody/codeblocks/monitor/) ).
There are no functional changes between these revision, just changes in comments and C:B project-files for wx2.8.
Debian stable packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo (https://apt.jenslody.de/).
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc19, fc20, fc21 and rawhide), RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) and RedHat/CentOS 7 packages (only 64-bit at the moment) can be found in my rpm-repo (https://copr.fedoraproject.org/coprs/jenslody/).
I recently switched to copr (https://copr.fedoraproject.org/) to build and host my Fedora and CentOS packages.
Instructions how to use it can be found on my server (https://rpm.jenslody.de/) (easier) or on copr (https://copr.fedoraproject.org/coprs/jenslody/) (a little more handwork needed).
By the way:
users who did not add my rpm-repo manually but by downloading the appropriate rpm (with my repo-file inside) should get an automatic update to the new repo.
-
its now 9:14pm, Monday February 16th 2015..
and the SF link is still NO SHOW >:( :'(
when you dev's compile for the nightly release (usually functional url/link is located in 1st post... ;D)
how do you get it to compile with the svn commit revision #? showing as the build version?
ps:
has anyone taken a look at my bug report?
https://sourceforge.net/p/codeblocks/tickets/133/
-
on the note of Nightly downloads is there any other site where I can download it?
oohh say FTP ^_^ FTP means LOVE in the binary language ;D lol
as of 2:29am SF has the file finally. ^_^
-
INFO : next nightly will be build with TDM-GCC 4.9.2
-
INFO : next nightly will be build with TDM-GCC 4.9.2
ooh really?
I have noticed TDM seem to keep it self up to date more often with GCC then MinGW does ;_;
my MinGW(32bit) setup is.... v4.8.1
I haven't seen an update to MinGW for a long time... =(
-
Until now, no archive repository. Interestingly, there has been corrected checking Russian spelling encoded Win-1251.
>:( - Again misery and refund on 9958 version. Here, too, Russian orthography is faulty.
I couldn't understand what is your problem.
Can you paraphrase this in a more understandable way?
-
Packages for openSUSE (http://codeblocks.esy.es) (binaries and sources) for 32-bit and 64-bit.
-
INFO : next nightly will be build with TDM-GCC 4.9.2
Did you know that 4.9.2 requires a license distribution? Does this mean we have to distribute the license for every CB executable we develope?
Hi! Sorry for the interruption, but you may want to take at least a few seconds
to look into some recent license changes for the software you're about to
install.
Parts of the "winpthreads" library will be compiled into every binary file (EXE
or DLL) you create. It's a necessary evil that is currently required in order to
provide support for threads and concurrency in programs compiled by GCC.
The license for winpthreads requires you to reproduce its text in every copy or
substantial portion of the winpthreads library that you distribute. This means
that even if you just want to distribute a single small executable, created with
TDM-GCC (or any winpthreads-based GCC release), you must include a copy of that
license.
Check the license out in the file "COPYING.winpthreads.txt", which will be
installed along with TDM-GCC. Consult with a lawyer if you have any concerns
about how you can use this software.
Does this new license hurt your usage of GCC? Let the developers know!
File a feature request asking them to change the winpthreads license or get rid
of GCC's winpthreads requirement, at:
https://sourceforge.net/p/mingw-w64/feature-requests/new/
Send an email to the MinGW-w64 mailing list, at:
mingw-w64-public@lists.sourceforge.net
-
for sure we will have to show this message somewhere in our CB messages ourselves. For the rest we should check with John.
-
this seems like an ADDITIONAL HEADACHE ;_;
in that case I will stick with good old MinGW for compiling as I was considering using tdm because it is up to date with gcc...
as MinGW is only gcc v4.8.1 as I know...