build bot in the github, I see one nice project

[Grit Clef]

Oh, when I tried your command:
The result is, first 13571 came out and then an error:
Error: Process completed with exit code 141.

The method already works in my fork, see here:

my fork's main branch

Oh, the command worked, thanks.

[ollydbg]

Oh, when I tried your command:
The result is, first 13571 came out and then an error:
Error: Process completed with exit code 141.

The method already works in my fork, see here:

my fork's main branch

Oh, the command worked, thanks.

I see your github action failed:

https://github.com/zxunge/x86-codeblocks-builds/actions/runs/11081484299/job/30793287105

Code

+ mv '/opt/codeblocks/lib/*.dll' /opt/codeblocks/bin/
mv: cannot stat '/opt/codeblocks/lib/*.dll': No such file or directory

You should comment out this line. I have comment out already, and should solved this issue.

[ollydbg]

I'm going to commit some the patches I used(mainly from Tim) to support building C::B release under github action.

I'm thinking some new idea:

We have a lot of third part plugin development in github, and maybe we can enough them to build those plugins under github action, and in our C::B, we may need to find a simple way to install/update the plugin.

Any comments?

I don't think the plugin developer need to build the whole C::B again, maybe they can just download/copy some prebuild C::B release from other code repo, and build there own plugin release.

[stahta01]

I'm going to commit some the patches I used(mainly from Tim) to support building C::B release under github action.

I'm thinking some new idea:

We have a lot of third part plugin development in github, and maybe we can enough them to build those plugins under github action, and in our C::B, we may need to find a simple way to install/update the plugin.

Any comments?

I don't think the plugin developer need to build the whole C::B again, maybe they can just download/copy some prebuild C::B release from other code repo, and build there own plugin release.

Please submit the update of "ax_cxx_compile_stdcxx.m4" because it likely needs done for more than Msys2 mingw building.
I am just too tired to try submitting any more patches; since, I see little gain from the effort.

Tim S.

[ollydbg]

I'm going to commit some the patches I used(mainly from Tim) to support building C::B release under github action.

I'm thinking some new idea:

We have a lot of third part plugin development in github, and maybe we can enough them to build those plugins under github action, and in our C::B, we may need to find a simple way to install/update the plugin.

Any comments?

I don't think the plugin developer need to build the whole C::B again, maybe they can just download/copy some prebuild C::B release from other code repo, and build there own plugin release.

Please submit the update of "ax_cxx_compile_stdcxx.m4" because it likely needs done for more than Msys2 mingw building.
I am just too tired to try submitting any more patches; since, I see little gain from the effort.

Tim S.

Hi, Tim, all your patches for the github action build under msys2/shell/configure/make methods were commited to svn now, many thanks for your contribution.

I see little gain from the effort.

Your contribution is so important for C::B, so it has great gain for C::B. 

EDIT:

I'd like to thank other guys like:

Carsten Arnholm(I forgot his nick name in our forum, sorry) create this git repo, https://github.com/arnholm/codeblocks_sfmirror
Grit Clef: create the github action to create C::B, https://github.com/zxunge/x86-codeblocks-builds

[Grit Clef]

Great. Now the build process of CB would be more easier.

[Miguel Gimenez]

Do these changes fix this ticket?

[stahta01]

Do these changes fix this ticket?

A quick scan of that ticket shows that these patch, yet to be applied to codeblocks SVN, fixes the issue in a different way that was only tested using the MSys2 MinGW GCC toolchain. My patches did nothing on how the codeblocks installation went; but, patches other than mine was used. The ticket implied the installation was changed; I did not examine the patch files myself.

Since, the two recent patches I submitted went no where; I do not plan to submit any more to codeblocks patch system. I posted the very important one in the nightly build. I figure I will wait on the others till I see movement or after the next release. After the release, maybe they will start taking patches and applying them in a faster time frame.

Edit: That ticket appears to have aged poorly and I suggest closing it because of age. The git repo linked no longer exists.
Edit2: It looks like he used my many year old changes and edited them and some of those edit made it into Code::Blocks SVN and he gave up doing more work because of how long it took. I can relate. So, I think closing that ticket would be the correct thing to do.

Tim S.

[ollydbg]

Since, the two recent patches I submitted went no where; I do not plan to submit any more to codeblocks patch system. I posted the very important one in the nightly build. I figure I will wait on the others till I see movement or after the next release. After the release, maybe they will start taking patches and applying them in a faster time frame.

Which ones? This one: Re: The 25 September 2024 build (13571) is out.?

I see your mentioned patches were in svn repo now.

[Miguel Gimenez]

Edit: That ticket appears to have aged poorly and I suggest closing it because of age. The git repo linked no longer exists.
Edit2: It looks like he used my many year old changes and edited them and some of those edit made it into Code::Blocks SVN and he gave up doing more work because of how long it took. I can relate. So, I think closing that ticket would be the correct thing to do.

Thank you, I have just closed it.

[stahta01]

Since, the two recent patches I submitted went no where; I do not plan to submit any more to codeblocks patch system. I posted the very important one in the nightly build. I figure I will wait on the others till I see movement or after the next release. After the release, maybe they will start taking patches and applying them in a faster time frame.

Which ones? This one: Re: The 25 September 2024 build (13571) is out.?

I see your mentioned patches were in svn repo now.

Wow, the patches are now being applied in the last 24 hours.
Thanks for the work. Looks like movement is happening.
Edit: It looks like all the patches have made it to SVN.
Edit2: I am now going to look at scripted wizard changes for MSys2 MinGW GCC changes; those are not important enough that moving to SVN is needed and can just be copied to folder till they get approved by people who are using them.

Tim S.

[ollydbg]

Edit2: I am now going to look at scripted wizard changes for MSys2 MinGW GCC changes; those are not important enough that moving to SVN is needed and can just be copied to folder till they get approved by people who are using them.

Tim S.

I have 2 patches in my fork, one for wx, the other is for opencv.

Most of the libraries can be used by the pkg-config command in compiler or linker opinion.

[stahta01]

Edit2: I am now going to look at scripted wizard changes for MSys2 MinGW GCC changes; those are not important enough that moving to SVN is needed and can just be copied to folder till they get approved by people who are using them.

Tim S.

I have 2 patches in my fork, one for wx, the other is for opencv.

Most of the libraries can be used by the pkg-config command in compiler or linker opinion.

I added your changes to my repo I will ignore those for now.

Tim S.

[ollydbg]

Edit2: I am now going to look at scripted wizard changes for MSys2 MinGW GCC changes; those are not important enough that moving to SVN is needed and can just be copied to folder till they get approved by people who are using them.

Tim S.

I have 2 patches in my fork, one for wx, the other is for opencv.

Most of the libraries can be used by the pkg-config command in compiler or linker opinion.

I added your changes to my repo I will ignore those for now.

Tim S.

Fill free to modify my two patches about wx and opencv demo, I don't think they are very good, I think it is my hack to the wizard script code.

[reckless]

great