News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Doesn't detect changes that should cause build.

Started by dfatcb, May 31, 2012, 08:43:19 PM

Previous topic - Next topic

dfatcb

A lot of times if I just update the master library (the .lib files change date) the code::blocks says nothing to do, but it should at least link.  Are there options to have it look a little deeper?

stahta01

CB Version is what?

The nightlys has improved external dependency that might fix your issue.

Tim S. 
C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]

dfatcb

Version 10.05.

Is there a newer official/stable release?

ollydbg

Quote from: dfatcb on June 02, 2012, 07:57:09 AM
Version 10.05.

Is there a newer official/stable release?
Try a nightly build version of Codeblocks. see: Nightly builds
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

dfatcb

ok, thanks, but can't you just take the nightly files and put them in the folder where code::blocks is already installed and be done with it, basically upgrading to the latest version?  they should just create an innosetup installer for the nightly updates and then it be easy/clear.

zabzonk

Quotebut can't you just take the nightly files and put them in the folder where code::blocks is already installed and be done with it

Yes you can - this is basically what I do. Just unzip the nightly over the top of your existing installation (after backing it up), saying "yes" to "replace existing files". This may not be the most kosher way of installing a nightly, but it's convenient and has always worked for me.

Alpha

Quote from: dfatcb on June 06, 2012, 08:44:52 PM
they should just create an innosetup installer for the nightly updates and then it be easy/clear.
(Assuming you are on Windows) you could use the unofficial installer.

Radek

I have made the same experience. The project is a (static) library. Along with the library, I have a project with a small testing program which tests new changes made in the library. If the library changes, the test program must be rebuilt, remaking the test program results in "nothing to do". I am using SVN builds of Code Blocks (Debian, Gnome).

Well, does not matter too much, the testing program is small, rebuilding is as quick as remaking, but ...

MortenMacFly

Quote from: Neil Butterworth on June 06, 2012, 08:50:59 PM
but it's convenient and has always worked for me.
Be careful: Sooner or later it won't. Its best to delete all files except the own ones before.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

zabzonk

QuoteBe careful: Sooner or later it won't.

Care to outline a scenario where it wouldn't work?

oBFusCATed

Removed plugin for example or some left xrc file...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]