News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

nightly cookbook install guide raises a question

Started by knacked, January 12, 2008, 07:43:17 AM

Previous topic - Next topic

knacked

#15
Okay,

one final question and I'm ready to become a codeBlocks user.

When I download the codeBlocks sources via the vcs,
Must I download them to an empty folder in my codeBlocks directory,
so that I get a scr folder in the codeBlocks dir.

JGM

Quote from: knacked on January 13, 2008, 04:47:12 AM
When I download the codeBlocks sources via the vcs,
Must I download them to an empty folder in my codeBlocks directory,
so that I get a scr folder in the codeBlocks dir.

Actually codeblocks use svn not cvs. In case you're at sourceforge the current development site is http://developer.berlios.de/projects/codeblocks. And yes, to an empty folder like codeblocks-head where you like.

knacked

Well I got that sorted but it ends the build with many errors.
QuoteC:\CB\projects... wx/wx.h: no such file or directory
etc..

In fact all the header files in
QuoteC:\Projects\wxMSW-2.8.7\include\wx
are not being detected.

The cb global var points to
QuoteC:\CB\projectsCB\src
the wx points to
QuoteC:\Projects\wxWidgets-2.6.3

Sorry to darken your door with my shadow.

killerbot


knacked

#19
jeez,
a bit odd since I copy/pasted the dir path straight from the folders properties panel.

Thanks for the heads up Killerbot.

I've finally got the core workspace built, I tried to do the contrib_plugins workspace too but that failed, so I rebuilt the core and executed the update.bat

And all is good.

I want to get the devpaks plugin though,if I manage to do this will I have to rebuild and update both the core and contrib workspaces again ?

Anyway, thanks alot for your patience,I'll see if I can't donate some cash your way.

Also the C:\CB\projectsCB file and its subfolder \src have exclamation marks on them,
I take it thats bad ?
peace.

Jenna

#20
You mean exclamation marks in windows explorer ?
If you have (for example) TortoiseSVN installed, that means you have changed these files, what is not a good idea unless you know what you do, and I don't think you do so.

Right click the C::B sources base-folder and from the TortoiseSVN submenu chose "revert" and redo all the changes.
Then delete the "devel" and the "output" folder under "src" (there is normally no need to do so, but it makes sure no miscompiled dll or plugin remains there).
After that right-click "CodeBlocks.cbp" and chose "Build" or "Rebuild(Clean)", in your case the second might be more secure. If everything is ready, right-click "ContribPlugins.workspace" and again chose "Build" ore "Rebuild(Clean)".
And if that also ended you can start "update.bat".
Test the new C::B executable in "output", if it works you can either copy it to your original C::B executables folder (delete the content there before) or use it as standard.

knacked

Thanks for that jens,

It still is not working like it should, though I can compile and run my own c++ projects.

I'm gonna clean it out and try for the year+ old stable version instead of the nightly builds, I'm having trouble setting the path for codeblocks to the C:\MinGW\bin folder (for that .dll there) and the zip folder that resides there also.

In fact that seems to be my only problem but I've spent days trying to get it to work and I've quietly lost all my hair.

The stable version, its way way behind the nightly builds,
I might have to comprimise though.

respects

killerbot

I have the feeling you are mixing up things all the time.

Yes, try again from scratch, but read carefully every step !!!! Once you are very sure about a step, carry it out. When you have questions about a step, ask them here before performing that step untill you have no questions and you fully understand what you are doing .

It works without any problem. Don't use RC2, really don't.