Recent Posts

61

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by Miguel Gimenez on March 01, 2026, 09:20:13 pm »

In the first code tag the path is incorrect, FortranProject is not in trunk but in trunk/src/plugins/contrib

62

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by Pecan on March 01, 2026, 08:57:07 pm »

What can I do about this error?

Neither TortoiseSVN nor svn will let me do that.

Code

PS F:\usr\Proj\cbDevel328WrkCC> cd .\trunk\
PS F:\usr\Proj\cbDevel328WrkCC\trunk> svn delete FortranProject
svn: E200005: Use --force to override this restriction (local modifications may be lost)
svn: E200005: 'F:\usr\Proj\cbDevel328WrkCC\trunk\FortranProject' is not under version control
PS F:\usr\Proj\cbDevel328WrkCC\trunk>

And a clean update gets the error.

Code

PS F:\usr\Proj\cbDevel328WrkCC\trunk> svn update
Updating '.':

Fetching external item into 'src\plugins\contrib\FortranProject':
svn: warning: W155035: The external 'https://svn.code.sf.net/p/fortranproject/code/trunk' defined in svn:externals at 'F:\usr\Proj\cbDevel328WrkCC\trunk\src\plugins\contrib' cannot be checked out because 'F:\usr\Proj\cbDevel328WrkCC\trunk\src\plugins\contrib\FortranProject' is already a versioned path.

At revision 13804.
svn: E205011: Failure occurred processing one or more externals definitions
PS F:\usr\Proj\cbDevel328WrkCC\trunk>

Even using --force does not work.

Code

PS F:\usr\Proj\cbDevel328WrkCC\trunk> svn delete FortranProject --force
svn: E125001: 'F:\usr\Proj\cbDevel328WrkCC\trunk\FortranProject' does not exist
PS F:\usr\Proj\cbDevel328WrkCC\trunk> svn update
Updating '.':

Fetching external item into 'src\plugins\contrib\FortranProject':
svn: warning: W155035: The external 'https://svn.code.sf.net/p/fortranproject/code/trunk' defined in svn:externals at 'F:\usr\Proj\cbDevel328WrkCC\trunk\src\plugins\contrib' cannot be checked out because 'F:\usr\Proj\cbDevel328WrkCC\trunk\src\plugins\contrib\FortranProject' is already a versioned path.

At revision 13804.
svn: E205011: Failure occurred processing one or more externals definitions
PS F:\usr\Proj\cbDevel328WrkCC\trunk>

63

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by Miguel Gimenez on March 01, 2026, 08:29:26 pm »

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

64

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by Pecan on March 01, 2026, 07:42:30 pm »

What can I do about this error?

65

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by Miguel Gimenez on March 01, 2026, 04:57:04 pm »

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

66

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by gd_on on March 01, 2026, 02:30:23 pm »

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.

67

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by ollydbg on March 01, 2026, 01:28:41 pm »

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.

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?

68

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by gd_on on March 01, 2026, 12:10:49 pm »

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.

69

Development / Re: unified workspace and cbp under Windows for different wxWidgets versions

« Last post by ollydbg on March 01, 2026, 03:47:04 am »

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.

70

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

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.