Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
You can revert the change by ollydbg indicated in my previous message: Change to the plugins/contrib folder and run

Code
svn delete FortranProject
svn commit
52
What can I do about this error?
53
I have just added FortranProject_cbsvn_Windows.cbp to the FortranProject repository, please remove the folder and the CBP from the C::B repository so they do not clash (i.e., revert this)

Code
add 	/trunk/src/plugins/contrib/FortranProject
add /trunk/src/plugins/contrib/FortranProject/FortranProject_cbsvn_Windows.cbp
54
Quote
So, the way it to "remove" the FortanProject plugin's cbp file from the svn trunk?
Probably, but add the cbp to the original repos and restore the link to this repository.
55
Thanks for this publication.
Just a small remark: why almost all these cbp have linux end lines (LF). That's not a problem, but as they are for Windows, my original work has windows endlines (CR LF).
I use "git svn" command. I mean I first add the cbp to the git repo, and later I use the git svn dcommit to push the changes to the remote svn server. I'm not sure how to fix this issue.


Quote
More, I think there is a problem with FortanProject plugin, because as it's located outside C::B svn repository, it causes a problem when I try to update my svn synchro.

So, the way it to "remove" the FortanProject plugin's cbp file from the svn trunk?
56
Thanks for this publication.
Just a small remark: why almost all these cbp have linux end lines (LF). That's not a problem, but as they are for Windows, my original work has windows endlines (CR LF).

More, I think there is a problem with FortanProject plugin, beacuse as it's located outside C::B svn repository, it causes a problem when I try to update my svn synchro.
57
Hi, guys, I have committed the unified cbps to our svn repo, revision 13804. Thanks for the contribution, @gd_on.

Also, if you see some issues, you can report here, we can discuss and adjust. Thanks.
58
Development / Re: svn rev 13798 issue?
« Last post by ollydbg on March 01, 2026, 02:24:51 am »
I have seen that inside ....\src\tools\test\macrosmanager there is a macrosmanager.cbp file. It can display variables in the C::B log window if you launch a build or full rebuild command. The display is a little bit heavy/confusing, but it exists!

Oh, yes, this is a command like project, I see there are a lot of command line statement when you "build"(actually you do no build the project, but just run the command) the project.
Code
					<Add before="echo Code::Blocks location: $(CODEBLOCKS)" />
<Add before="echo Code::Blocks APP_PATH: $(APP_PATH)" />
<Add before="echo Code::Blocks DATA_PATH: $(DATA_PATH)" />
<Add before="echo Code::Blocks PLUGINS: $(PLUGINS)" />
<Add before="echo Code::Blocks LANGUAGE: $(LANGUAGE)" />
<Add before="echo Code::Blocks ENCODING: $(ENCODING)" />


Quote
PS: in some of the clangd_client_wx*.cbp, the $(CODEBLOCKS) variable is still used.

Let me fix them, I can find them by search the $(CODEBLOCKS) in all the *.cbp files.
59
Nightly builds / Re: The 09 February 2026 build (13785) is out.
« Last post by Miguel Gimenez on February 28, 2026, 12:08:22 pm »
Change applied in r13802, thank you.
60
Nightly builds / Re: The 09 February 2026 build (13785) is out.
« Last post by Miguel Gimenez on February 28, 2026, 11:15:57 am »
Thank you, I will integrate this.
Pages: 1 2 3 4 5 [6] 7 8 9 10