nightly cookbook install guide raises a question

[knacked]

Hi all.

refering to ...http://wiki.codeblocks.org/index.php?title=Nightly_Cookbook

I've just built wxWidgets and am at the point where it tells me to install/extract the winzip executable somewhere into the path.....it states

During the build of Code::Blocks, several resources are going to be zipped in zip files. Therefore, the build process should have access to a zip.exe. We have to download that zip.exe and put it somewhere in our path. A good place is: MingW\bin.
You can download zip.exe for free from this site and this is a direct link(32bit) to the most recent version at the time of this writing.
Once downloaded, simply extract zip.exe to the appropriate location.

First off, I cant get hold of a winzip.exe,and if I am finally able could it be he/she means put the winzip.exe into... C:\MinGW\bin (not C:\MingW\bin) ?

Where do I put the winzip.exe, maybe it means I should add it to the path by putting it into a new folder and typing

set path=%PATH%;C:\ZIPFILE;

at the command line ?

Do I need to worry about flamin winzip.
Would a winzip (version 1) batch file suffice or am I losing it.
?

Oh, one more thing, following said tutorial it states that the \scr folder is in the CodeBlocks master directory.
But it is'nt, it ends up in

C:\Projects

and there is also one in

C:\ProjectsCodeBlocks

.

No scr folder in the codeblocks master dir.

[Biplab]

During the build of Code::Blocks, several resources are going to be zipped in zip files. Therefore, the build process should have access to a zip.exe. We have to download that zip.exe and put it somewhere in our path. A good place is: MingW\bin.
You can download zip.exe for free from this site and this is a direct link(32bit) to the most recent version at the time of this writing.
Once downloaded, simply extract zip.exe to the appropriate location.

First off, I cant get hold of a winzip.exe,and if I am finally able could it be he/she means put the winzip.exe into... C:\MinGW\bin (not C:\MingW\bin) ?

Where do I put the winzip.exe, maybe it means I should add it to the path by putting it into a new folder and typing

set path=%PATH%;C:\ZIPFILE;

at the command line ?

Do I need to worry about flamin winzip.
Would a winzip (version 1) batch file suffice or am I losing it.
?

Did you read the tutorial carefully?? It never asked you to install WinZip. It has a clear instruction. There is even a direct link to download zip.exe file which would solve your problem.

[knacked]

Thanks for your reply Biplab.

I'll re-read the tutorial then.

<edit>oh shit,win.exe not winzip

But...that link to zip.exe is no longer working, at least not for me.

I read a previous post where the op has also had this problem and he said the last chapter of the manual had a working link.
Is the manual currently being re-written or something
,where is the last chapter.

I've been up since 1am working on this and its now 6pm,
the life of a programmer,got a love it.

p.s. codeblocks looks very nice coming from dev-cpp, being all free I got to say thanks alot for all the hard work to the maintainers.
chill.

[killerbot]

I have adjusted the link on the cookbook, but it seems event at sourceforge this either don't work or are extremely slow at the moment.

The mirrors that used to host the download seem no longer to do it anymore, and things have to be downloaded from sourceforge now.

http://switch.dl.sourceforge.net/sourceforge/infozip/zip232.zip

[knacked]

okay thanks alot, by the way sourceforge forums are having some problems at the moment,some of us buggers cant log in without ctd, whether thats got anything to do with all this ?

One last question if you dont mind too much.

The cookbook states

We have to download that zip.exe and put it somewhere in our path. A good place is: MingW\bin.

Can I get some verification where : MingW\bin is supposed to be.

[dje]

The best working place is C:\MinGW
At least avoid the spaces in the path to avoid compiling linking problems.

Dje

[knacked]

Okay Im at the point of building the codeblocks internal workspace.

It exits with one error which is

cannot find -1wxmsw28u

The wxmsw28u_gcc_cb.dll is in C:\codeblocks directory.
The WxWindowsQuickRef guide says its because

You have an incorrect link library in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, determine which version of the library is built and adjust the library name in your build options accordingly.

But I'm still having a hard time here.

I'd really appreciate your help,in 1 hour I will have been trying to set up c::b for 24 hours 

[killerbot]

It exits with one error which is

cannot find -1wxmsw28u

-1wxmsw28u  ==> -lwxmsw28u    : that is -lllllllllllllllllllllllllllllllllllllll not -'one'

[Jenna]

Okay Im at the point of building the codeblocks internal workspace.

It exits with one error which is

cannot find -1wxmsw28u

The wxmsw28u_gcc_cb.dll is in C:\codeblocks directory.
The WxWindowsQuickRef guide says its because

You have an incorrect link library in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, determine which version of the library is built and adjust the library name in your build options accordingly.

But I'm still having a hard time here.

I'd really appreciate your help,in 1 hour I will have been trying to set up c::b for 24 hours 

If you have wxWidgets build, like the cookbook tells you, you have to make sure that the base-dir of th global variable "wx" points to the base-dir of your wxWidgets install, all other (lib, include ..)  normally don't need to be set. And of course the global variable "cb" must point to the first "src" subdir in the C::B source-tree.

[knacked]

I know thats an -l,I was just copying the build message and that l is displayed as -1.

I hav'nt had to specify the directory the dll resides in.
Should I do that in project->build options->custom variables
WX-CFG= (put the path to the dll here ?)

Your all getting pissed off with me are'nt you,

<edit>the link libraries field has this...wxmsw28$(WX_SUFFIX)
WX_SUFFIX is defined as u, with is correct.
There is nothing defined for WX_CFG though.<edit>

[killerbot]

like Jens said :

If you have wxWidgets build, like the cookbook tells you, you have to make sure that the base-dir of th global variable "wx" points to the base-dir of your wxWidgets install, all other (lib, include ..)  normally don't need to be set. And of course the global variable "cb" must point to the first "src" subdir in the C::B source-tree.

[knacked]

And of course the global variable "cb" must point to the first "src" subdir in the C::B source-tree.

This must be the problem then, the wx variable points to

C:\Projects\wxWidgets-2.6.3

..the wxWidgets directory.

But the cb var points to

C:\projectCodeBlocks\src

.
I'll point it to

C:\Projects\wxWidgets-2.6.3\scr

now and see if that helps.There is no scr folder in the C:\codeblocks directory.

[Jenna]

And of course the global variable "cb" must point to the first "src" subdir in the C::B source-tree.

This must be the problem then, the wx variable points to

C:\Projects\wxWidgets-2.6.3

..the wxWidgets directory.

But the cb var points to

C:\projectCodeBlocks\src

.
I'll point it to

C:\Projects\wxWidgets-2.6.3\scr

now and see if that helps.There is no scr folder in the C:\codeblocks directory.

If you have downloaded the C::B sources ther is a "src" subdir, if not you can't build C::B.

And "cb" has to point to this subdir and not to a wxWidgets subdir !!

And you should give wxWidgets 2.8.7 a try , because 2.6.3 is quite old.

[JGM]

And you should give wxWidgets 2.8.7 a try , because 2.6.3 is quite old.

updated that on the wiki to reflect the new version

[knacked]

If you have downloaded the C::B sources ther is a "src" subdir, if not you can't build C::B.

And "cb" has to point to this subdir and not to a wxWidgets subdir !!

And you should give wxWidgets 2.8.7 a try , because 2.6.3 is quite old.

Jesus, I got the nightly build, obviously I did'nt get the source for cb.

And now I see theres a 12 jan version out and that I had an old version of wxWidgets Im gonna have to delete everything again and restart.

Thanks for updating the link JGM.

So the nightly builds links (in announcements) are not the source code.

I know,I'm a ******* dik.

[knacked]

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]

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.

C:\CB\projects... wx/wx.h: no such file or directory

etc..

In fact all the header files in

C:\Projects\wxMSW-2.8.7\include\wx

are not being detected.

The cb global var points to

C:\CB\projectsCB\src

the wx points to

C:\Projects\wxWidgets-2.6.3

Sorry to darken your door with my shadow.

[killerbot]

the wx points to

C:\Projects\wxWidgets-2.6.3

point it to your wx 287 !

[knacked]

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]

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.