User forums > General (but related to Code::Blocks)

[Work In Progress] Patches to Compile C::B against wxWidgets 2.9.0

(1/9) > >>

stahta01:
This a work in Progress

I am working on adding the Patches needed to Build Code::Blocks linking against the soon to be released,
wxWidgets 2.9.0 development build.

Tim S

Current Status is: 3. Code::Blocks Opens and Closes without crashing using safe-mode option

The Status Testing:

--- Code: ---1. Code::Blocks Source Code Compilers and Links against wxWidgets 2.9.0 with POD Warnings
2. Code::Blocks Source Code Compilers and Links against wxWidgets 2.9.0 with-out POD Warnings
3. Code::Blocks Opens and Closes without crashing using safe-mode option
4. Code::Blocks Opens and Closes without crashing without using safe-mode option
5. Code::Blocks Compiles Itself.

--- End code ---


Types of Patches

--- Code: ---1. Code::Blocks Design Change Patches
2. Code::Blocks Implementation Change Patches
3. wxWidgets 2.9 required POD Warning Fixes Patches
4. wxWidgets 2.9 required design Change Patches
5. wxWidgets 2.9 optional deprecation Change Patches

--- End code ---

Biplab:
I've committed a large number of patches to trunk in this regard. I've patched most of the core plugins (will patch today). Now Code::Blocks compiles without warnings. However, Compiler & Code-Completion plugins are creating runtime issues. I'm Investigating them. You can have a look at the patches and let me know if anything differs from your patch. :)

stahta01:

--- Quote from: Biplab on May 03, 2009, 04:08:15 am ---I've committed a large number of patches to trunk in this regard. I've patched most of the core plugins (will patch today). Now Code::Blocks compiles without warnings. However, Compiler & Code-Completion plugins are creating runtime issues. I'm Investigating them. You can have a look at the patches and let me know if anything differs from your patch. :)

--- End quote ---

That explains why my patches needed updating; last updated them about two months ago.

The Compiler is likely crashing because it is trying to open an GUI window before the GUI event handler is finished being initialized. Never, took the time to trace the cause; was hoping it would go away before 2.9.0 release, but not going to happen.

Tim S

stahta01:
Command, I Used, to build wxWidgets 2.9.0 RC2
http://biolpc22.york.ac.uk/pub/2.9.0-rc2/

Still Testing These Options, but should work.

While working on Patches to Source Code will be using wxUSE_STC=0 and USE_STC=0 to avoid Build Errors because of two wxscintilla libs.



--- Code: ---mingw32-make -f makefile.gcc USE_PROPGRID=1 USE_OPENGL=0 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 CPPFLAGS="-Wmissing-include-dirs"

--- End code ---

Optional: CPPFLAGS="-Wmissing-include-dirs"
Required: CXXFLAGS="-fno-strict-aliasing"
Not Certain: LDFLAGS="-enable-stdcall-fixup"

Required for wxSmith: USE_PROPGRID=1

Patch to Code::Blocks needed if NOT wxUSE_STC=0 and USE_STC=0
Edit: Changed Patch to see if this one works better, than last one.

--- Code: ---Patch Fails to work too often to be maintained.

--- End code ---

Biplab:

--- Quote from: stahta01 on May 03, 2009, 04:52:56 am ---Command, I Used, to build wxWidgets 2.9.0 RC2

Still Testing These Options, but should work.


--- Code: ---mingw32-make -f makefile.gcc USE_PROPGRID=1 USE_OPENGL=0 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 LDFLAGS="-enable-stdcall-fixup" CXXFLAGS="-fno-strict-aliasing" CPPFLAGS="-Wmissing-include-dirs"

--- End code ---

Optional: CPPFLAGS="-Wmissing-include-dirs"
Required: CXXFLAGS="-fno-strict-aliasing"
Not Certain: LDFLAGS="-enable-stdcall-fixup"

Required for wxSmith: USE_PROPGRID=1


--- End quote ---

Didn't notice that RC2 is out.

I did build wx without the required CXXFLAGS. Will download RC2 later and use it to build C::B.

Navigation

[0] Message Index

[#] Next page