Hm, you are right. for static linking, --static option would helps and that would be right solution in this case except it was missing Requires. On Fri, Jul 12, 2013 at 1:09 PM, Daniel Macks <dmacks@xxxxxxxxxxxx> wrote: > This solution does not seem correct. The whole point of the ".private" > fields in the .pc file is to distinguish things that are used internally > (such as libxml and libiconv) from things that are part of the public > interface (#include in the public headers, etc.). In a shared-library > system, one does *not* want to publish the flags for internal-use-only > details (a program or library that uses fontconfig should not care about or > want to link directly against them). > The original problem is because in a *static* world, one does need to link > against all the internal-use libraries because static libs obviously do not > have dynamic-loader links. One can have pkg-config emit the .private fields > along with the normal ones (the user can control this feature). Or else a > library author can have the data go in .private vs regular by checking > whether a shared library is being built. I don't know any modern packages > that do so, but some older/legacy ones do, back when static libs were more > popular. > dan > > > On Fri, 12 Jul 2013 12:41:18 +0900, Akira TAGOH <akira@xxxxxxxxx> wrote: > Thanks. fixed in git. >> >> >> On Fri, Jul 12, 2013 at 12:15 AM, 宮村 公男 <xanadu@xxxxxxxxxxxxxxxxx> wrote: >> > Hi, I am newly joined to this mailing list. > >> > I'm not a kind of people who is related with fontconfig development. >> > Just >> > joined to inform a issue with package-config file of fontconfig, i.e. > >> > fontconfig.pc. > >> > I build fontconfig to build ffmpeg with subtitle support. Even though, >> > I >> > build fontconfig correctly, I get "fontconfig not found" error from >> > ffmpeg >> > configure script. > >> > I searched how to solve this issue and found the answer finally!! >> > >> > The answer is found in following URL. > >> > http://einguste.hatenablog.com/entry/2013/03/23/131352 >> > >> > I build fontconfig 2.10.93 with "./configure --prefix=prefix >> > --disable-shared --disable-docs --enable-static --enable-iconv" >> > configure >> > option. > >> > And make a correction to fontconfig.pc which is installed into >> > prefix/lib/pkgconfig. > >> > --- fontconfig.pc.orig >> > +++ fontconfig.pc.correction >> > >> > Version: 2.10.93 >> > +++ Requires: freetype2 expat >> > --- Libs: -L${libdir} -lfontconfig >> > +++ Libs: -L${libdir} -lfontconfig -liconv >> > >> > >> > Hope that this information will help your development of fontconfig. > >> > Cheers! >> > >> > >> > _______________________________________________ >> > Fontconfig mailing list >> > Fontconfig@xxxxxxxxxxxxxxxxxxxxx >> > http://lists.freedesktop.org/mailman/listinfo/fontconfig >> > >> >> >> >> -- Akira TAGOH >> _______________________________________________ >> Fontconfig mailing list >> Fontconfig@xxxxxxxxxxxxxxxxxxxxx >> http://lists.freedesktop.org/mailman/listinfo/fontconfig >> >> > > -- > Daniel Macks > dmacks@xxxxxxxxxxxx > > > > _______________________________________________ > Fontconfig mailing list > Fontconfig@xxxxxxxxxxxxxxxxxxxxx > http://lists.freedesktop.org/mailman/listinfo/fontconfig -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
