User forums > Help

Linux build - Tools Node Regression?

<< < (3/7) > >>

digifuzzy:
 ;D ;D ;D ;D ::) ::) :P
touchdown...crowd goes wild!!!

@oBFusCATed - patch worked great
and you were right about the wx-config switch. again, my bad. apologies

build successful
wx-widgets

--- Code: ---/opt/wx30/bin/wx-config --version-full
3.1.0.0

--- End code ---
(latest from github)

code::blocks - Revision: 9760

found references for using PCH and bad build environment
ended up building and installing own wxW version using  linux source build instructions

wxWidgets configure (bad):

--- Code: ---../configure --prefix=/opt/wx30 --with-sdl --with-opengl --enable-stl --enable-xrc --enable-unicode --enable-mediactrl --enable-webview --enable-precomp-headers
--- End code ---

applied wx3.stl.patch
C::B configure:

--- Code: ---./configure --with-wx-config=/opt/wx30/bin/wx-config
--- End code ---
configure would run to the end, but make would fail with all sorts of errors about undefined references to wx containers ( and there were vast numbers and varying types ).

I rebuilt wx but this time without STL
wxWidgets configure (good):

--- Code: ---../configure --prefix=/opt/wx30 --with-sdl --with-opengl --enable-xrc --enable-unicode --enable-mediactrl --enable-webview --enable-precomp-headers
--- End code ---

cleaned out C::B and the patch, used the same C::B configure line as above.
make ran to the end without errors (although a couple of warnings about deprecated wxFont scrolled by really fast  ;) )

The two big differences noticed:
- STL containers flag
- the need to explicitly set pre-compiled headers. C::B make would fail on building the SDK - the error I was encountering after applying the patch
-> the first link hints at the need to explicitly set WX_PRECOMP value.

Once the configure lines were set up. Everything ran well.

Of note, someone did file a bug report in late March about wxGTK using "--enable-stl".
The maintainer's answer was that another application needed the flag. I can't see Arch having two versions of the same library with different flag settings...

stahta01:

--- Quote from: digifuzzy on May 01, 2014, 09:28:01 am ---Of note, someone did file a bug report in late March about wxGTK using "--enable-stl".
The maintainer's answer was that another application needed the flag. I can't see Arch having two versions of the same library with different flag settings...


--- End quote ---

FYI: IIRC, there is 2 to 4 options selecting STL in multiple ways.

Macros

--- Code: ---wxUSE_STD_CONTAINERS
wxUSE_STD_IOSTREAM
wxUSE_STD_STRING
wxUSE_STL

--- End code ---

The first option "--enable-stl" sets the other three.
Configure options.

--- Code: -----enable-stl
--enable-std_containers
--enable-std_iostreams
--enable-std_string

--- End code ---

I remember one more weird testing macro that I could NOT find to add to this post had something to do with STL and archive streams.
Edit: Found the test macro WX_TEST_ARCHIVE_ITERATOR.

Edit: It is likely that the app did NOT need all three options set; you might try to research it. I would see if just --enable-std_iostreams and --enable-std_string was enough to fix it. This part of wxWidgets is poorly documented so I can see it being missed.

Tim S.

digifuzzy:
Tim,
Thanks!
wxGTK maintainer is Eric Belanger
The affected application is poedit maintained by Sergej Pupykin.
Not sure how to broach this one...I'm not a wxW dev, so I'm curious how my approach would be received.
Suggestions?

stahta01:
You have to find out what poedit needs to build correctly.

Tim S.

digifuzzy:

--- Quote from: stahta01 on May 03, 2014, 10:28:06 pm ---You have to find out what poedit needs to build correctly.
Tim S.

--- End quote ---

Grabbing source from github now. Will look.

Its almost like we need an "Office of wxWidgets Coordination" to keep all these configurations up to date :P ::) ;) :D

Navigation

[0] Message Index

[#] Next page

[*] Previous page