weft qda users - Nov 2006 - [Weft QDA users] weft-qda on Mandriva (2006.0), incl. wxruby 0.6 and gcc 4.0 problem

Dear All,

try to get weft-qda-1.0.1 to run on GNU/Linux Mandriva,
I ran into problems with a newer g++ compiler.
A "dirty" install package for Mandriva 2006.0 (i586)
can be found at https://ftp.intevation.de/users/bernhard/weft-qda-20060mdk/ .
I am pasting in the analysis part below.

Maybe this is helpful for somebody.
There is no warantee, your milage might vary, it might break things.

My suggestion for weft-qda development is to port to wxruby2 if possible or
help to fix wxruby 0.6, otherwise it will be hard for somebody
to get weft-qda to run.

I cannot say if newer gcc version will make it better.
Using 4.0.3 to build wxruby (without recompiling wxGTK which was build
with gcc 4.0.1) did not help. Maybe gcc 4.1.x will behave differently,
I cannot say.

Regards,
Bernhard
ps.: Please copy me on relevant replies, I might not be permanently
subscribed to the list.


Background or how and why was this dirty build produced?
-----------------------------------

The first approach is:
Installing the packages that come with Mandriva main and contrib.
Install ruby''s PageTemplates and build wxruby 0.6.0.

Trying to run any wxruby application, e.g.
	ruby wxruby-0.6-src/samples/controls/controls.rb
there is an error:
[..]src/wxruby.so: undefined symbol: _ZTV12wxRbListCtrl - [..]/src/wxruby.so
(LoadError)

The error was reported on Fedora with gcc 4 as well,
but the developers do not want to fix it.
http://rubyforge.org/tracker/index.php?func=detail&aid=2153&group_id=35&atid218

Thesis: There is a difference between older g++ compilers and version 4.0.

Constructive proof:
	Fortunately Mandriva has a package for an old version of gcc as well.
	Install:
		gcc3.3-cpp-3.3.6-2mdk
		gcc3.3-c++-3.3.6-2mdk
		gcc3.3-3.3.6-2mdk
	Recompile wxruby with g++-3.3.6.

	This alone produces more errors, probably because the binaries
	are incompatible.

	So rebuild wxGTK-2.4.2 as well and then rebuild wxruby again.
	To do this additionally install:
		libgtk+1.2-devel-1.2.10-41mdk

		export CC=gcc-3.3.6
		export CXX=g++-3.3.6
		#set LD_LIBRARY_PATH and PATH accordingly before
		# building wxruby

	This build also has wx/html/htmlproc.h copied to the right place
	and the removal lines deactivated in extconf.rb.

--
Managing Director - Owner, www.intevation.net       (Free Software Company)
Germany Coordinator, fsfeurope.org       (Non-Profit Org for Free Software)
www.kolab-konsortium.com   (Email/Groupware Solution, Professional Service)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/weft-qda-users/attachments/20061113/403390b5/attachment.bin

Hi Bernhard

Thank you for your message and for trying Weft.
> A "dirty" install package for Mandriva 2006.0 (i586)
> can be found at https://ftp.intevation.de/users/bernhard/weft-qda-20060mdk/
.
> I am pasting in the analysis part below.
>   
This is useful - sorry you had such a job getting it to work.
> My suggestion for weft-qda development is to port to wxruby2 if possible or
> help to fix wxruby 0.6, otherwise it will be hard for somebody
> to get weft-qda to run.
>   
You are right that wxruby 0.6.0 is now old and doesn''t work well with 
modern Linux distros (b/c it requires old WxWidgets version, old GTK 
version and old gcc).

weft qda + wxruby2 will be very good - when wxruby2 is finished. It will 
look a lot better on Linux, work on OS X, support multi-lingual 
projects, and offer a more professional and usable interface on all 
platforms(eg a better way of working with the ''Documents and
Categories''
window). Unfortunately wxruby2 is not yet quite stable enough to use for 
Weft QDA.

One of the main reasons I haven''t released a newer version of Weft QDA 
is to spend time  contributing to wxruby2. We are making a lot of progress.

The good news is that a lot of great features have already been added to 
Weft QDA - editable documents, stored ''live'' searches and
queries,
document attributes, nicer icons, scripting.

I am wondering about whether to release an intermediate version of Weft 
QDA that has some of these features. The downside is that it will take 
some time away from working on other things, and will mean users having 
to upgrade their projects twice. But maybe the perfect is the enemy of 
the good ... what do users on this list think?
> I cannot say if newer gcc version will make it better.
> Using 4.0.3 to build wxruby 
For info - wxruby2 works perfectly with gcc 4. I think it''s unlikely 
that anyone will fix wxruby 0.6.0 so that it works with that version though.

Thanks again
Alex

======= 2006-11-14 04:25:54 ????????======
>Hi Bernhard
>Thank you for your message and for trying Weft.
>> A "dirty" install package for Mandriva 2006.0 (i586)
>> can be found at
https://ftp.intevation.de/users/bernhard/weft-qda-20060mdk/ .
>> I am pasting in the analysis part below.
>>   
>This is useful - sorry you had such a job getting it to work.
>
>> My suggestion for weft-qda development is to port to wxruby2 if
possible or
>> help to fix wxruby 0.6, otherwise it will be hard for somebody
>> to get weft-qda to run.
>>   
>You are right that wxruby 0.6.0 is now old and doesn''t work well
with
>modern Linux distros (b/c it requires old WxWidgets version, old GTK 
>version and old gcc).
>
>weft qda + wxruby2 will be very good - when wxruby2 is finished. It will 
>look a lot better on Linux, work on OS X, support multi-lingual 
>projects, 
This is a very good news, and I am looking forward that Weft QDA will support 
multi-linguage.
>and offer a more professional and usable interface on all 
>platforms(eg a better way of working with the ''Documents and
Categories''
>window). Unfortunately wxruby2 is not yet quite stable enough to use for 
>Weft QDA.
>
>One of the main reasons I haven''t released a newer version of Weft
QDA
>is to spend time  contributing to wxruby2. We are making a lot of progress.
>
>The good news is that a lot of great features have already been added to 
>Weft QDA - editable documents, stored ''live'' searches and
queries,
>document attributes, nicer icons, scripting.
>
>I am wondering about whether to release an intermediate version of Weft 
>QDA that has some of these features. The downside is that it will take 
>some time away from working on other things, and will mean users having 
>to upgrade their projects twice. But maybe the perfect is the enemy of 
>the good ... what do users on this list think?
If releasing an intermediate version will not take you lots of time, I would
prefer to support the idea.

I think releaseing new version regularly is a sign of active development, and it
is a way to keep the user community active.

I am willing to hear the different views of the lister:)
>> I cannot say if newer gcc version will make it better.
>> Using 4.0.3 to build wxruby 
>For info - wxruby2 works perfectly with gcc 4. I think it''s
unlikely
>that anyone will fix wxruby 0.6.0 so that it works with that version though.
>
>Thanks again
>Alex
>_______________________________________________
>weft-qda-users mailing list
>weft-qda-users at rubyforge.org
>http://rubyforge.org/mailman/listinfo/weft-qda-users
= = = = = = = = = = = = = = = = = = = 
???
2006-11-14
------
Deparment of Sociology
Fudan University,Shanghai,China PRC
My current Email: ronggui.huang at gmail.com

Hi Alex!
Hi Huang!

On Tuesday 14 November 2006 03:16, ??? wrote:
> ======= 2006-11-14 04:25:54 ????????======
> >> A "dirty" install package for Mandriva 2006.0 (i586)
> >> can be found at
> >> https://ftp.intevation.de/users/bernhard/weft-qda-20060mdk/ . I am
> >> pasting in the analysis part below.
> >
> >This is useful - sorry you had such a job getting it to work.
I have quite a bit of experience getting software to work,
but I expect that more people out of the potential user group
will have major trouble.

BTW: I am unsure if the HTML export works in my build.
> >> My suggestion for weft-qda development is to port to wxruby2 if
possible
> >> or help to fix wxruby 0.6, otherwise it will be hard for somebody
> >> to get weft-qda to run.
> >The good news is that a lot of great features have already been added
to
> >Weft QDA - editable documents, stored ''live'' searches
and queries,
> >document attributes, nicer icons, scripting.
> >
> >I am wondering about whether to release an intermediate version of Weft
> >QDA that has some of these features. The downside is that it will take
> >some time away from working on other things, and will mean users having
> >to upgrade their projects twice. But maybe the perfect is the enemy of
> >the good ... what do users on this list think?
>
> If releasing an intermediate version will not take you lots of time, I
> would prefer to support the idea.
I agree that an intermediate version can be helpful
if the effort is reasonable.
> >> I cannot say if newer gcc version will make it better.
> >> Using 4.0.3 to build wxruby
> >
> >For info - wxruby2 works perfectly with gcc 4. I think it''s
unlikely
> >that anyone will fix wxruby 0.6.0 so that it works with that version
> > though.
For weft-qda it would be helpful, the fix cannot be hard for someone
that is into wxruby development, so my suggestion is to publish a patch
for it as many GNU/Linux distributions contain older versions of wxWidgets
and GTK still, so deployment of weft-qda would be much easier if wxruby 
would be fixed in this regard.

Best Regards,
Bernhard
-- 
Managing Director - Owner, www.intevation.net       (Free Software Company)
Germany Coordinator, fsfeurope.org       (Non-Profit Org for Free Software)
www.kolab-konsortium.com   (Email/Groupware Solution, Professional Service)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/weft-qda-users/attachments/20061114/54e5d6db/attachment.bin