Help Compiling Taglib: missing 'config.h'
setosha at gmail.com
Thu Jul 21 02:32:19 CEST 2011
2011/7/21 Pris Matic <prismatic.project at gmail.com>
> Hi all,
> Thanks for the replies. I'm trying to keep my app source as 'portable' as
> possible (outside of using Qt :p) and I want to include any external libs
> like TagLib statically (ie not install them in the system).
Belive me, adding all lib sources to your repo can't guarantee
successful build on every OS. Even with QT.
So it's realy bad idea. (I try it ~3 month ago)
As alternative you can use *git **submodule*. You can also write some
scripts to build dependences and install it to correct (local) places.
Scott, what did you mean by setting up includes for *all* the source dirs?
> I'm not directly including each taglib source file in like main.cpp or
> anything, I compiled the TagLib source as a static lib which I then link to.
> In this case shouldn't I just have to link to 'tag.h' and 'fileref.h'?
you can += all src subfolders to INCLUDEPATH in .pro or .pri
> On Wed, Jul 20, 2011 at 6:42 PM, Scott Wheeler <wheeler at kde.org> wrote:
>> On Jul 21, 2011, at 12:08 AM, Pris Matic wrote:
>> > tstring.h: No such file or directory // from tag.h., line 30, which
>> is "#include tstring.h"\
>> If you want to use taglib that way, you'll need to set up includes for
>> each of the source directories. However, since you're developing on Ubuntu,
>> I don't understand why you wouldn't just use the system packages. (i.e. get
>> your taglib by doing apt-get install libtag1-dev libtag1c2a) It's much
>> easier to incorporate into a project that way since then you just have to
>> tell QtCreator to look for the pkgconfig file and it'll set up the rest.
>> taglib-devel mailing list
>> taglib-devel at kde.org
> taglib-devel mailing list
> taglib-devel at kde.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the taglib-devel