Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
General (but related to Code::Blocks) / Re: CodeBlocks on Linux
« Last post by Ender4rmy on May 26, 2026, 04:54:05 pm »
Ah alright. Weirdly some people told me that the Flatpak works for them without issue.

Also I dont think I need to change any credentials. As far as I know I set them up as they should be
52
General (but related to Code::Blocks) / Re: CodeBlocks on Linux
« Last post by Miguel Gimenez on May 26, 2026, 04:17:57 pm »
C::B in Flatpak has some problems due to the folder protection set by the Flatpak creator; some needed folders are not accesible to C::B.

Quote
Also dont understand what you mean with "Forum Credentials"

The user name and password you use when logging in this forum. While you are logged in the forum you can go to the Wiki page and edit it.
53
General (but related to Code::Blocks) / Re: CodeBlocks on Linux
« Last post by Ender4rmy on May 26, 2026, 03:22:21 pm »
Sorry for the late reply. Great to hear that the freeze has been fixed on Arch and Fedora. I guess Sourceforge confused me a bit there. When I was on the svn page of Code::Blocks my Kdevelop sorta popped up and told me it can just download it for me so I did.
Hope the AUR was also, or is being fixed.
On a freshly installed release of CachyOS and PikaOS, while I was able to install Code::Blocks via flatpak(on PikaOS even using the Gnome Store), I wasnt able to install the Contrib Plugins on either System, which is kinda why I got to the point of building from Source and which is why I made this Post.

Also dont understand what you mean with "Forum Credentials", sorry I am quite new to using a Forum
54
Development / Re: Force X11 compatibility mode
« Last post by Miguel Gimenez on May 25, 2026, 09:58:10 am »
Thanks for testing.

Applied in r13848.
55
Development / Re: which standard to use, both for building wx and CB
« Last post by christo on May 25, 2026, 05:57:54 am »
Quote from: Wkerry on May 25, 2026, 12:57:23 am
Is the ax_cxx_compile_stdcxx.m4 file a copy from the following repo or equivalent file from some other place a this file is availabel from a number of places?
https://github.com/autoconf-archive/autoconf-archive/blob/master/m4/ax_cxx_compile_stdcxx.m4
You are correct @Wkerry, the file is copied from autoconf-archive master
56
Development / Re: which standard to use, both for building wx and CB
« Last post by Wkerry on May 25, 2026, 12:57:23 am »
Is the ax_cxx_compile_stdcxx.m4 file a copy from the following repo or equivalent file from some other place a this file is availabel from a number of places?
https://github.com/autoconf-archive/autoconf-archive/blob/master/m4/ax_cxx_compile_stdcxx.m4
57
Development / Re: which standard to use, both for building wx and CB
« Last post by christo on May 24, 2026, 06:14:58 pm »
I've been using c++20 for a while with autotools. m4/ax_cxx_compile_stdcxx.m4 has to be updated. Attaching patch to avoid duplicate effort when we switch to c++20
58
Development / Re: Force X11 compatibility mode
« Last post by blauzahn on May 23, 2026, 03:00:32 pm »
With that patch, docking is fixed under Arch Linux Wayland as well, e.g. open-files-list dock.

Wonderful! Thank you.
59
Development / Re: Force X11 compatibility mode
« Last post by Miguel Gimenez on May 23, 2026, 10:53:40 am »
With this patch Aui docking works on Ubuntu 24.04/Wayland:

Code
Index: src/src/app.cpp
===================================================================
--- src/src/app.cpp	(revision: 13846)
+++ src/src/app.cpp	(copia de trabajo)
@@ -367,8 +367,19 @@
 
 } // namespace
 
-IMPLEMENT_APP(CodeBlocksApp) // TODO: This gives a "redundant declaration" warning, though I think it's false. Dig through macro and check.
+#ifdef __WXGTK__
+wxIMPLEMENT_APP_NO_MAIN(CodeBlocksApp);
 
+int main(int argc, char **argv)
+{
+    setenv("GDK_BACKEND", "x11", 1);
+    wxDISABLE_DEBUG_SUPPORT();
+    return wxEntry(argc, argv);
+}
+#else
+wxIMPLEMENT_APP(CodeBlocksApp);
+#endif
+
 BEGIN_EVENT_TABLE(CodeBlocksApp, wxApp)
     EVT_ACTIVATE_APP(CodeBlocksApp::OnAppActivate)
     EVT_TASKBAR_LEFT_DOWN(CodeBlocksApp::OnTBIconLeftDown)
60
Development / Force X11 compatibility mode
« Last post by Miguel Gimenez on May 22, 2026, 02:38:14 pm »
Currently most Linux distributions are removing X11 support forcing Wayland usage.

C::B relies heavily on Aui, and currently Aui does not work correctly with Wayland. Forcing XWayland, if it is available, would make Aui work again on these systems (this is the method used by KiCAD).

Adding these lines to OnInit() should be enough:

Code
#ifdef __WXGTK__
    wxSetEnv("GDK_BACKEND", "x11");
#endif

Opinions?

EDIT: The change does not work, while "GDK_BACKEND=x11 ./codeblocks" works. Looks like the variable must be set using setenv() just before the App object is created, i.e., before the call to wxEntry()

Pages: 1 2 3 4 5 [6] 7 8 9 10