[scribus] 1.3.3.12 no odt support???

[John Culleton]

On Thursday 26 June 2008 10:58:35 am John Culleton wrote:
> On Thursday 26 June 2008 10:05:51 am Plinnell wrote:
> > On Thursday 26 June 2008 14:34:05 John Culleton wrote:
> > > On Wednesday 25 June 2008 03:25:35 am Craig Bradney wrote:
> > > > > ----- Original Message -----
> > > > > Subject: Re: [scribus] 1.3.3.12 no odt support???
> > > > > From: Rolf-Werner Eilert <eilert-sprachen at t-online.de>
> > > > > To: cbradney at zipworld.com.au,"Scribus User Mailing List"
> > > >
> > > > <scribus at lists.scribus.net>
> > > >
> > > > > Date: 25-06-2008 8:40
> > > > >
> > > > > Craig Bradney schrieb:
> > > > > > Theres nothing wrong with the source that I can see...
> > > > > >
> > > > > > before you run configure, please run
> > > > > > make -f Makefile.svn
> > > > > >
> > > > > > as per:
> > > > > > http://docs.scribus.net/index.php?lang=en&page=install3
> > > > > >
> > > > > > I have just gone through and tested many scenarious of
> > > > > > code, missing
> > > >
> > > > includes,
> > > >
> > > > > > incorrect autohell versions etc, with the tarball and had
> > > > > > all of the mentioned issues. Running the make -f line
> > > > > > fixed it in one go with no workarounds.
> > > > > >
> > > > > > Craig
> > > > >
> > > > > Even if it's not the svn version, Craig? I got the ordinary
> > > > > source of the stable 1.3.3.12 to compile.
> > > >
> > > > Having not used autohell for awhile it took me awhile to go
> > > > through the elimination process last night. I finally
> > > > remembered we had issues like this in the past and it was
> > > > because the person had not run make -f Makefile.svn. It will
> > > > depend on your system as to whether you need this or not, I
> > > > found I always had to run it in the past.
> > > >
> > > > Use cmake.. you hair wont go grey, and you wont be pulling it
> > > > out at every call to configure. No nasty spells required
> > > > either.
> > > >
> > > > Craig
> > >
> > > The instructions for cmake describe a more complex and for me
> > > at least confusing process than the traditional process. I
> > > recognize that the developers see virtues in cmake. But perhaps
> > > after development is completed the install process could be
> > > boiled down to the usual method for us busy folks that keep
> > > many Open Source products on our systems.  If every product
> > > develops its own unique installation software then life becomes
> > > unnecessarily complex.  I have seen other products (Inkscape as
> > > I recall) follow other paths looking for the ideal installation
> > > system. But for the end user the ideal method is something that
> > > works and is reasonably simple and universal.
> >
> > Yes, and that is why Inkscape has started to migrate to Cmake as
> > well. :)
> >
> > > Other Open Source products (e.g Gimp) compile and install
> > > nicely with ./configure
> > > make
> > > make install
> > > and have for many years.  And Scribus used to.
> >
> > Hmm..
> >
> > cmake -DCMAKE_INSTALL_PREFIX:PATH=/path/whereyouwant/scribus
> > make
> > make install
> >
> > Not so complicated to me and the error messages are readable by
> > mere humans.
> >
> > > I keep multiple versions of Scribus installed by the simple
> > > expedient of putting the source of each version in a separate
> > > directory and renaming the executable of the older versions
> > > with e.g. scribus11. So I don't see any virtue in cmake to the
> > > end user.
> >
> > For starters:
> > Faster
> > Better clearer error messages
> > Cross platform It works on Windows/OSX/Linux
> > Easier to maintain for developers, so we can spend more time
> > coding
> >
> > :) Prevents developers hair loss and temporary bouts of insanity.
> > :)
> > :
> > > After running
> > > make -f Makefile.svn
> > > Scribus 1.3.3.12 compiles but can't find its plugins on
> > > execution. Given this degree of uncertainty I will stick with
> > > 1.3.3.11 as the stable version and wait for the next major
> > > version. I have wasted too much time on 1.3.3.12 already.  It
> > > is only a minor release.
> >
> > <snipped>
> >
> > Excepting this issue, there are important fixes in 1.3.3.12.
> >
> > Peter
>
> Sorry. I forget the rather verbose incantation from release to
> release.  And the cmake instructions don't describe the simple
> case. So how about this:
> Include with the release a file called e.g., configure. The
> contents would be as follows:
>
> cmake -DCMAKE_INSTALL_PREFIX:PATH=.
> make
> make install
>
> That way the end user won't have to look it all up every time, or
> bother the list.
>
> I lost all my hair years ago, struggling with JCL.

Well, here is the latest report on 1.3.3.12 after using cmake as 
described above.

The number of missing items is down a little. I moved the executable 
to /usr/local/bin and executed:
/usr/local/bin/scribus
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libsvgimplugin.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libsvgexplugin.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscriptplugin.so.0.0.0: 
undefined symbol: _ZTI10PrefsPanel
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscribusshortwords.so.0.0.0: 
undefined symbol: _ZN14ScActionPlugin3runEP9QIODevice
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscribusexportpixmap.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscribus13format.so.0.0.0: 
undefined symbol: ScCore
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscribus134format.so.0.0.0: 
undefined symbol: ScCore
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscribus12format.so.0.0.0: 
undefined symbol: ScCore
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libsaveastemplateplugin.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//liboodrawimp.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//liboldscribusformat.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libnewfromtemplateplugin.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libimportps.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libfontpreview.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libcolorwheel.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libbarcodegenerator.so.0.0.0: 
undefined symbol: 
_ZN8ScPlugin19newPrefsPanelWidgetEP7QWidgetRP10PrefsPanelR7QStringR7QPixmap

So I dug into the 1.3.312 directory and moved some subdirectories 
to /usr/share and /usr/local/lib. Ran ldconfig.
Ran /usr/local/bin/scribus
Got approximately the same list of missing stuff.

Ran scribus directly from the bin directory found in my 1.3.3.12 
directory. Now it can't find icons. 

OTOH I run scribus 1.3.3.11 and I get only three missing item 
messages, probably explainable by having more than one version on my 
system:

              Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscribus13format.so.0.0.0: 
undefined symbol: ScCore
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscribus134format.so.0.0.0: 
undefined symbol: ScCore
Cannot find 
plugin: /usr/local/lib/scribus/plugins//libscribus12format.so.0.0.0: 
undefined symbol: ScCore
                                                                      
You guys are playing with me, right?  

What do you use for a prefix path for cmake? That is the only variable 
in play. 

-- 
John Culleton
Resources for every author and publisher:
http://wexfordpress.com/tex/shortlist.pdf
http://wexfordpress.com/tex/packagers.pdf
http://www.creativemindspress.com/newbiefaq.htm
http://www.gropenassoc.com/TopLevelPages/reference%20desk.htm