On Mon, Mar 10, 2008 at 7:31 PM, Udo Richter <[EMAIL PROTECTED]> wrote:
> clemens kirchgatterer wrote:
> > structure bin, lib, include, share, ... if i want to compile software
> > using the libs (and headers) of opt1 i only have to do
> > "PKG_CONFIG_PATH=/opt1 make" and to start that program
On Monday 10 March 2008, Udo Richter wrote:
> clemens kirchgatterer wrote:
> > structure bin, lib, include, share, ... if i want to compile software
> > using the libs (and headers) of opt1 i only have to do
> > "PKG_CONFIG_PATH=/opt1 make" and to start that program
> > "LD_LIBRARY_PATH=/opt1 prog"
clemens kirchgatterer wrote:
> structure bin, lib, include, share, ... if i want to compile software
> using the libs (and headers) of opt1 i only have to do
> "PKG_CONFIG_PATH=/opt1 make" and to start that program
> "LD_LIBRARY_PATH=/opt1 prog". given the Makefile of prog uses
> pkg-config properl
Hi,
Am Montag, den 10.03.2008, 11:39 +0100 schrieb clemens kirchgatterer:
> there is another argument for pkg-config we havent talked about yet.
> the link dependencies. type 'freetype-config --libs' and it will most
> likly print '-lfreetype -lz' but only if you have compiled freetype
> with zlib
On Sun, Mar 9, 2008 at 10:50 AM, Udo Richter <[EMAIL PROTECTED]> wrote:
> There is _one_ currently installed default version of the headers for
> this machine, and the question is why these headers are not at a default
> location, esp. since the binaries seem to be at a default location, or?
n
On Sat, 2008-03-08 at 19:12 +0100, Clemens Kirchgatterer wrote:
> Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
>
> > I still believe, though, that freetype2's include files are broken.
> > A simple '#include ' should be enough. If their header
> > file(s) would behave like the rest, we wouldn't h
Clemens Kirchgatterer wrote:
>> But would it kill anybody to simply have all header files at
>> a standard place (/usr/include and /usr/local/include)?
>
> yes it would. how would you install different versions of the same
> libraries (with their headers) if it wasn't in different paths? and
> wha
Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> On 03/08/08 19:12, Clemens Kirchgatterer wrote:
> > Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> >
> >> I still believe, though, that freetype2's include files are broken.
> >> A simple '#include ' should be enough. If their header
> >> file(s) wou
On 03/08/08 19:12, Clemens Kirchgatterer wrote:
> Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
>
>> I still believe, though, that freetype2's include files are broken.
>> A simple '#include ' should be enough. If their header
>> file(s) would behave like the rest, we wouldn't have this discussion.
Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> I still believe, though, that freetype2's include files are broken.
> A simple '#include ' should be enough. If their header
> file(s) would behave like the rest, we wouldn't have this discussion.
no. pkg-config and freetype-config have absolutly not
Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> On 03/08/08 15:01, Clemens Kirchgatterer wrote:
> > Udo Richter <[EMAIL PROTECTED]> wrote:
> >
> >> #>pkg-config --libs freetype2 fontconfig
> >> -bash: pkg-config: command not found
> >>
> >> - no comment -
> >
> > i could as easily argue with:
> >
On 03/08/08 15:01, Clemens Kirchgatterer wrote:
> Udo Richter <[EMAIL PROTECTED]> wrote:
>
>> #>pkg-config --libs freetype2 fontconfig
>> -bash: pkg-config: command not found
>>
>> - no comment -
>
> i could as easily argue with:
>
>> make
> bash: make: command not found
How do you build VDR wi
On 03/08/08 17:43, Udo Richter wrote:
> Clemens Kirchgatterer wrote:
>> pkg-config is no exotic dependency that we have good reason to avoid.
>
> I know that its easy to install that package. (Though I wonder whether
> the linvdr guys agree.)
> My point is just that its not a change-one-line-and-
Udo Richter <[EMAIL PROTECTED]> wrote:
> Or even better: Is there a third way that works for both?
as i have written in my RFC there is:
freetype-config
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Clemens Kirchgatterer wrote:
> pkg-config is no exotic dependency that we have good reason to avoid.
I know that its easy to install that package. (Though I wonder whether
the linvdr guys agree.)
My point is just that its not a change-one-line-and-all-will-be-happy,
it does add one more to the b
Udo Richter <[EMAIL PROTECTED]> wrote:
> #>pkg-config --libs freetype2 fontconfig
> -bash: pkg-config: command not found
>
> - no comment -
i could as easily argue with:
> make
bash: make: command not found
pkg-config is no exotic dependency that we have good reason to avoid.
clemens
___
Joerg Pulz wrote:
> What do you think why we have tools like pkg-config or autotools and so
> many projects make use of it? Because its funny? I don't think so!
>
> What's the big deal with Villa's proposal to change two lines in the
> Makefile when it breaks nothing for you and makes life easie
On 03/08/08 11:54, Clemens Kirchgatterer wrote:
> Ville Skyttä <[EMAIL PROTECTED]> wrote:
>
>> FWIW, I think providing a pkgconfig file is very much a "root"
>> solution (ditto $foo-config scripts, but *.pc are much simpler to
>> write and read and have a unified interface). Lots of library
>> pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 8 Mar 2008, Clemens Kirchgatterer wrote:
Ville Skyttä <[EMAIL PROTECTED]> wrote:
FWIW, I think providing a pkgconfig file is very much a "root"
solution (ditto $foo-config scripts, but *.pc are much simpler to
write and read and have a un
Ville Skyttä <[EMAIL PROTECTED]> wrote:
> FWIW, I think providing a pkgconfig file is very much a "root"
> solution (ditto $foo-config scripts, but *.pc are much simpler to
> write and read and have a unified interface). Lots of library
> packages (and also some others) provide them nowadays whic
On 03/07/08 18:48, Ville Skyttä wrote:
> On Friday 07 March 2008, Klaus Schmidinger wrote:
>
>> Instead of having all applications work around freetyp2's weird include
>> macro stuff, why not complain to the freetype2 people and have them
>> provide just a plain old that can be included like any
On Friday 07 March 2008, Klaus Schmidinger wrote:
> Instead of having all applications work around freetyp2's weird include
> macro stuff, why not complain to the freetype2 people and have them
> provide just a plain old that can be included like any other
> header file?
>
> Sorry for being ignor
On 03/07/08 13:17, Joerg Pulz wrote:
> Content-ID: <[EMAIL PROTECTED]>
>
> On Thu, 6 Mar 2008, Klaus Schmidinger wrote:
>
>> On 03/06/08 20:37, Ville Skyttä wrote:
>>> Hello,
>>>
>>> The attached patch makes VDR's Makefile use pkgconfig for finding
>>> libs and
>>> include dirs of freetype and fo
On 03/07/08 08:44, Luca Olivetti wrote:
> En/na Klaus Schmidinger ha escrit:
>> On 03/06/08 20:37, Ville Skyttä wrote:
>>> Hello,
>>>
>>> The attached patch makes VDR's Makefile use pkgconfig for finding libs and
>>> include dirs of freetype and fontconfig instead of making assumptions.
>> How abo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-ID: <[EMAIL PROTECTED]>
On Thu, 6 Mar 2008, Klaus Schmidinger wrote:
On 03/06/08 20:37, Ville Skyttä wrote:
Hello,
The attached patch makes VDR's Makefile use pkgconfig for finding libs and
include dirs of freetype and fontconfig instead
En/na Klaus Schmidinger ha escrit:
> On 03/06/08 20:37, Ville Skyttä wrote:
>> Hello,
>>
>> The attached patch makes VDR's Makefile use pkgconfig for finding libs and
>> include dirs of freetype and fontconfig instead of making assumptions.
>
> How about putting that stuff at the same place every
On 03/06/08 20:37, Ville Skyttä wrote:
> Hello,
>
> The attached patch makes VDR's Makefile use pkgconfig for finding libs and
> include dirs of freetype and fontconfig instead of making assumptions.
How about putting that stuff at the same place everywhere?
Why must it have to be somewhere else
Hello,
The attached patch makes VDR's Makefile use pkgconfig for finding libs and
include dirs of freetype and fontconfig instead of making assumptions.
--- Makefile~ 2008-02-29 23:43:03.0 +0200
+++ Makefile 2008-03-06 21:29:58.0 +0200
@@ -20,8 +20,8 @@
MANDIR = $(PREFIX)/share
28 matches
Mail list logo
