User forums > Using Code::Blocks

SVN 10000 : congratulations

<< < (2/2)

sorinev:
I've been building C::B from source for over a year now and about 9 times out of 10, the svn number on the splash and help menu does update. It's just that weird once in a while that it doesn't. My build process has always been the same.

Linux:
After the first time building it, to update I just do the following

--- Code: ---svn update
make -j4
sudo make install
--- End code ---

Windows:
Right click folder, svn update.
Open .cpb project, then build.
Open contrib plugins workspace, then build workspace.
Run update.bat.
Copy contents of output folder to where my "installation" of C::B is.


As I said above, it does update 90% of the time. Instructions in the wiki for how to do the initial build are more or less clear, but for updating there aren't really any clear steps, so it took some trial and error for my first times doing updates on each architecture. Never occurred to me to just delete autorevision.h and rebuild, thanks. 

oBFusCATed:
sorinev: You're skipping the ./bootstrap and ./configure steps both of these are required if you doesn't follow the commit very closely.

sorinev:
bootstrap and configure every single time, even for updating, not only on the initial build? Meaning, I have to remember my list of configure options every single time...

Alpha:

--- Quote from: sorinev on October 21, 2014, 08:45:56 pm ---Meaning, I have to remember my list of configure options every single time...

--- End quote ---
No, just Ctrl-R, then type nf (for ./configure).  If you only rarely run a ./configure, then the your command will already appear, or will appear if you tap Ctrl-R a few times.  If you spend all day every day running ./configure then you will have to memorize some (probably 3 letter) unique string from the flags you send to ./configure.  Repeat previous steps with said unique string instead of "nf".  (You can even cheat and design your own unique id, such as CB and manually enter it at the end of your command once, in a shell comment.)
Hit enter to execute.

sorinev:
Thanks for the command history search tip. I do occasionally have to do configure for other applications, but it's a small and rare enough situation that it should be a pretty easy search. It appeared to me that bootstrap and configure weren't necessary (which apparently is wrong), so I tried to avoid it because the first time I updated C::B after building, I used bootstrap and configure before make and it screwed my install up pretty badly. It looks to have been some pretty big differences in the options I passed to configure that did it (i.e. forgotten options).

The ^r trick should help keep things straight.

Navigation

[0] Message Index

[*] Previous page