Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

svn rev 13798 issue?

<< < (3/3)

gd_on:
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!

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

ollydbg:

--- Quote from: gd_on on February 27, 2026, 09:39:24 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!

--- End quote ---

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)" />
--- End code ---



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

--- End quote ---

Let me fix them, I can find them by search the $(CODEBLOCKS) in all the *.cbp files.

incorrectpa:
I agree that the CODEBLOCKS macro seems unnecessary here if it isn't actually needed. Keeping the changes simple and consistent would make the code easier to maintain. Thanks for pointing this out!

Miguel Gimenez:
Profile spammer reported to moderator.

Navigation

[0] Message Index

[*] Previous page