User forums > Nightly builds
The 03 November 2018 build (11508) is out.
killerbot:
at the moment we still use : http://tdm-gcc.tdragon.net/
I think I use the TDM64 bundle.
sodev:
His problem sounds more like he simply forgot to add all the required MinGW DLLs to the application directory. Applications compiled with standard MinGW require a bunch of DLLs to run, basically almost all DLLs you can find in its bin directory, you can check the exact dependencies with your favorite dependency checker.
eckard_klotz:
Dear All.
Thanks for your replies.
I have already downloaded MinGW 8.1.0 from http://mingw-w64.org and installed the 64 bit version as well as the 32 bit version. For my development I prefer the 32 bit version since timing problems occure more drastically.
My initial interest was to get to know what binaries I have to choose as tool-chain executables:
* Do I have to use the binaries with the names traditionally provided by Code::Blocks?
* Or Do I have to use the binaries with names like i686-w64-mingw32-c++?
* both sets seem to be available.
In my first experiment I have chosen the i686-w64-mingw32-c++ binaries. With this I was able to build and run the Code::Blocks Hello World project but not my project-sources https://sourceforge.net/projects/moritz/?source=directory.
But thanks to Sodev, since I have now an idea why. I was able to start my application from Code::Blocks but not without Code::Blocks as before with a tdm-build. I assume now that Code::Blocks is already running the necessary DLLs and that's why it was possible to start my application from it with the run-button.
Is there a documentation existing that describes what additional DLLs or a-files have to be added?
Best regards,
Eckard.
eckard_klotz:
Dear Developers
I have one additional but different topic:
Today I build Code::Blocks by my self from the latest sources (SVN revision 11509). Due to our company fire-wall I was not able to update a sandbox from source-forge as I do it at home. Thus I created at source-forge a snapshot from your SVN archive.
Unfortunately this snapshot contains no revision-information and thus the build shows the revision-number 0 (zero).
Is it possible to change this manually?
Best Regards,
Eckard.
blauzahn:
--- Quote ---[...] revision-information [...} shows the revision-number 0 (zero). Is it possible to change this manually?
--- End quote ---
The way I clone/update might be of help for you. I do it with a Makefile which resides a directory above local trunk
and automates the steps described in the wiki (quite convenient when you do this weekly for wxWidgets, codeblocks, cppcheck etc).
Way more primitive like e.g. cmake but that keeps it simple. The relevant lines are:
--- Code: ---.PHONY: clone update updateChangelog
clone:
svn checkout svn://svn.code.sf.net/p/codeblocks/code/trunk
update:
(cd trunk && svn update)
updateChangelog:
(cd trunk && ./updateChangeLog.sh && ./update_revision.sh)
--- End code ---
Executing thes steps manually or via make you can e.g. create at home a new snapshot including revision, zip it and transfer it to the other machine.
If you can not go this way, please have a look into ./update_revision.sh. Until now, I had no need to examine this script myself. At the end, I have a file Changelog and a file revision.m4 containing e.g.:
--- Code: ---m4_define([SVN_REV], 11509)
m4_define([SVN_REVISION], 17.12svn11509)
m4_define([SVN_DATE], 2018-11-04 02:49:39)
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version