Re: [PATCH 2/4] configure.ac: Explicitly enable subject-objects for automake 1.11

Hi, 

I was googling through to understand this subdir-objects concept and found some useful links which I thought worth of sharing it.
http://curl.haxx.se/mail/lib-2013-07/0053.html
In the above link, for older versions of automate < < 1.14) configure script is generated without 'subdir-objects' and for automake versions
>=1.14 version, during congifure script generation time, automake initialization will make use 'subdir-objects'. 

For further information we can see, "git diff aff245b360444b11f47c1d04246cc45ef81e5de3 fe7e3229f8d43d678bb0d335a091ad1657b408d4"
from "https://github.com/bagder/curl" git repo.

I'd like to take up this task, and provide some workarounds.

Thanks and Best Regards, 
N Ravi

------- Original Message -------
Sender : Uli Schlachter<[email protected]>
Date : Jul 10, 2014 13:12 (GMT+05:30)
Title : Re: [cairo] [PATCH 2/4] configure.ac: Explicitly enable subject-objects for automake 1.11

Hi,

On 10.07.2014 09:02, Bryce W. Harrington wrote:
[..]
> (I'm noticing a lot of misc. new warnings building with gcc 4.8,
> particularly with --enable-qt as g++ seems fussier about things.  But
> I've only given attention to a couple of the really noisy warnings so
> far).

Thanks for looking into this. Debian testing recently gave me a new GCC version 
and I've just been ignoring the fact that I can't build cairo any more. If only 
the day had more hours...

From

[...]
>    https://bugs.freedesktop.org/show_bug.cgi?id=69874

"Yeah.  And subdir-objects is broken for the way we have our build set up at the 
moment (libdricore built from a separate directory, on the same .c files as core)."

That's exactly what cairo is doing with cairo-time.c. Eric Anholt didn't say in 
his comment what exactly can go wrong, but I still think that we need to "hack 
this up differently" before we can go to subdir-objs.

[...]
> So yeah, looks like you're right.  I'll withdraw this patch.
[...]

Any ideas how we could fix things properly?
We could move all of cairo-time.c into cairo-time.h, but that seems like a hack.
We could create a libtool convenience library containing cairo-time.c and link 
it into both places that need it, but that seems like too much work for too 
little gain.
We could make the _cairo_time functions part of cairo's API, but obviously 
that's a bad idea.

Cheers,
Uli
-- 
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo
-- 
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo