Can`t build C::B IDE from latest svn revision 12240

[omlk]

Since, you do not want help why are you still posting on this website?

You either need to have a Windows zip command first in the path or edit the CB project to use the MSys2 zip command.
This is NOT a CB problem!

Tim S.

So I want codeblocks to work correctly, and I show that there are bugs in codeblocks, and you claim that this is not a problem - and what do you think it is then?

I can not help you! If you can not read and understand what you quoted then no one can help you on this website!

Tim S.

Tell me then who can help me? Are you a codeblocks developer?

[stahta01]

Since, you do not want help why are you still posting on this website?

You either need to have a Windows zip command first in the path or edit the CB project to use the MSys2 zip command.
This is NOT a CB problem!

Tim S.

So I want codeblocks to work correctly, and I show that there are bugs in codeblocks, and you claim that this is not a problem - and what do you think it is then?

I can not help you! If you can not read and understand what you quoted then no one can help you on this website!

Tim S.

Tell me then who can help me? Are you a codeblocks developer?

No, I am not a Code::blocks developer; but, since you can not understand what is the problem no one can help you!!!

As I told you already the problem is you are not using a Windows standard zip command!!!
Either you must use a Windows standard zip command or you must edit the CB Project!
This is NOT the fault of the CB Project! It is your fault for not installing an Windows standard zip command in the path before it finds the  MSys2 zip command!

Do you understand the problem?

If you still do not understand the problem; please get some to explain my post to you.

After you install the Windows standard zip command, you can add the path to it in the CB Compiler global setting.

Tim S.

[stahta01]

I have likely built Code::Blocks over a hundred times using the MinGW64 GCC from MSys2.

I can help you; but, you have to understand what you are trying to do and you have to explain it to me.

I have built C::B using the standard CB Projects about 3 or more times; but, it seemed better to me to edit the CB Projects instead of trying to use the CB projects without changes.

I normally build C::B using an custom build of wxWidgets via one of two ways.
1. The C::B standard win32 way of mingw makefile
2. The MSys2 standard way of an MSys2 package

Under way 1 (mingw makefile) I have used monolithic builds with standard CB Projects or multilib with highly edited CB Projects.

My past tries of build CB via the configure/make required major edits to CB source code and the resulting binary failed to work.

My current use of highly customized CB projects that use wxWidgets msys2 package results in a binary that seems to work.
But, that project of mine was also to test CB source code changes.
And, I really have not tested the produced binary enough to say it works.

Tim S.

[omlk]

It is you who are incompetent in this problem. I have already found the cause of the problem and it is that too many parameters are passed for the zip, you need to use a template.

h:\i\msys64\usr\bin\zip.exe -0 ../../devel31_64/share/CodeBlocks/manager_resources.zip images/*.png images/??x??/*.png

[omlk]

In this post I wrote 5 steps how to compile codeblox 32/64 bits and config, + it is necessary to correct really parameter in a file H:\I\CB_src\wxgtk\include\wx\msw\setup.h
Codeblock has compiled, but there are still problems with executing pre / post commands to copy files to the appropriate directory devel31

from
#define wxUSE_GRAPHICS_DIRECT2D 0

to in the #else case as well.
#define wxUSE_GRAPHICS_DIRECT2D 1

[stahta01]

I hope in time you can get a clue.

Tim S.

[omlk]

 

[oBFusCATed]

[omlk]

Okay, it was interesting to get through all the obstacles on the way to getting a C::B IDE

[oBFusCATed]

I have not idea, why you think posting patches as images is something worth doing.
Posting patches without explanation what problem do they fix is even bigger waste of your time.

[omlk]

I have not idea, why you think posting patches as images is something worth doing.
Posting patches without explanation what problem do they fix is even bigger waste of your time.

An interesting question, I think others should learn to fix bugs in codeblocks and graphic information is better perceived than a fix that no one sees except the developers.
 

[sodev]

I don't know in which world you are living, but in my world "others" are failing to wear a simple face mask or stay at home. I have yet to meet someone who want's to fix stuff in third party code who doesn't call himself developer. As a developer looking at pictures (or even worse videos) to fix code is quite a huge waste of time for me, but maybe it's just me getting old and refusing to adapt to the new style of doing coding work

[omlk]

If anyone wants to test my codeblocks build, here is the link

• CB12240_gcc10.2.0_wxWidgets3.1.4_64bit.zip

[stahta01]

For those like me that wonder which files are in the zip; here is the output of the tree command.

One file that likely should not be in the zip is codeblocks.RPT

Tim S.

[omlk]

For those like me that wonder which files are in the zip; here is the output of the tree command.

One file that likely should not be in the zip is codeblocks.RPT

Tim S.

You're right, I'm more interested in how my build works, do you have any comments?