fluid-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] fluidsynth 1.1.3 build troubles with cmake


From: Heinz Wiesinger
Subject: Re: [fluid-dev] fluidsynth 1.1.3 build troubles with cmake
Date: Fri, 15 Oct 2010 21:26:34 +0200
User-agent: KMail/1.13.3 (Linux/2.6.36-rc7; KDE/4.4.3; x86_64; ; )

On Friday 15 October 2010 19:41:23 Pedro Lopez-Cabanillas wrote:
> On Friday 15 October 2010, Heinz Wiesinger wrote:
> > On Friday 15 October 2010 17:04:40 Pedro Lopez-Cabanillas wrote:
> > > On Friday 15 October 2010, Heinz Wiesinger wrote:
> > > > linux/4.4.4/../../../../lib64/libreadline.so:
> > > > undefined reference to `tgetstr'
> > > > collect2: ld returned 1 exit status
> > > > make[2]: *** [src/fluidsynth] Error 1
> > > > make[1]: *** [src/CMakeFiles/fluidsynth.dir/all] Error 2
> > > > make: *** [all] Error 2
> > > > 
> > > > I tried adding -lcurses, -lncurses and/or -ltermcap to the list of
> > > > libraries to link, but nothing seemed to help.
> > > 
> > > To link the transitive dependency, add some arguments to CMake. For
> > > instance: $ cmake \
> > > 
> > >   -DCMAKE_EXE_LINKER_FLAGS=-lncurses \
> > >   -DCMAKE_SHARED_LINKER_FLAGS=-lncurses \
> > >   ...
> > 
> > Thanks, that one worked. I still think that if autotools can do it
> > automatically, cmake should be able to do it too (IMHO).
> 
> FluidSynth doesn't use any termcap-API functions, why should we link one of
> the libraries providing those functions? It is the readline package in your
> distro that should be fixed, IMHO.

Well, I get your point. Nonetheless I don't see readline getting "fixed" in 
Slackware anytime soon. I had a quick try on building readline in a way to 
link against ncurses and it requires some build system hackery to accomplish, 
which hints at an upstream problem. The upstream problem is afair a licensing 
one, so it probably won't be fixed. And Slackware has a long history of not 
fixing upstream issues (contrary to a lot of other distros out there).

Anyway, the main point is, you won't fix it, Slackware won't fix it and I need 
to include that hack to be able to build fluidsynth, or continue using the 
autotools build system for as long as it is available. Don't know which one is 
more appealing right now.

> > However, that issue being resolved, I ran into another, although more
> > minor one. The installation path for manual pages is hardcoded to
> > "PREFIX/share/man/man1", which is an issue for me since Slackware puts
> > man pages in "PREFIX/man/man1" instead.
> > Now I know I can simply move the files there, but I would much rather
> > have a cmake switch for that. Something like -DINSTALL_MAN_DIR or so.
> > Would it be possible to include such a switch with the next release?
> 
> Sure. Please add a ticket as remainder.
> https://sourceforge.net/apps/trac/fluidsynth/newticket

Done, thanks!

Grs,
Heinz

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]