[scribus] 1.3.3.12 no odt support???

John Culleton john at wexfordpress.com
Thu Jun 26 18:13:04 CEST 2008


On Thursday 26 June 2008 11:17:02 am Craig Bradney wrote:
> > 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.
>
> People need to learn cmake, many other apps are moving to it,
> Scribus was one of the early adopters when it was clear cmake would
> become a prominent build system over a year ago. Replacing
> "configure" by a script that does those instructions would be
> completely incorrect. cmake replaces make -f + ./configure..
>
> Craig
>
>
>


Well if cmake replaces 
make -f Makefile.svn 
and
./configure
what then is the error in my script?  But forget about the script for 
the moment. 

Apparently there is some magic in specifying the path for cmake.  I 
tried the current directory (dot) and at the end of the process 
Scribus failed spectacularly.   I am willing to learn, but I need 
some more guidance. What addy can/should go on the end of the cmake 
command?   That is the only variable that I can see. And I don't much 
care whereinhell it goes, so long as it runs afterwards.  If there is 
a location that works please share it.  

I run slackware 12, which is about as plain vanilla as you can get. 



-- 
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




More information about the scribus mailing list