On Sun, Sep 1, 2013 at 11:27 PM, Sergey 'Jin' Bostandzhyan wrote:
> Interesting opinion, however, just an opinion and not a fact.
>
An opinion of a distro packager who's been dealing with similar stuff for
years...
> I've been
> using the same "build" approach in MediaTomb and we got packaged
On Sun, Sep 01, 2013 at 10:53:26PM +0100, Diego Elio Pettenò wrote:
> I wonder why the authors of automake would try to restrict different and
> actually valid usage scenarios? I've been using this setup for over 5
> years
> in different projects, I'd be really disappointed if I had to
Don't get me wrong - I have nothing against your approach. And the automake
maintainers are certainly not purposely trying to make things more
difficult for you. I merely suggest that you may run into more issues down
the road simply because supporting your setup is not a current goal of the
tool.
On Sun, Sep 1, 2013 at 10:36 PM, Sergey 'Jin' Bostandzhyan wrote:
> I wonder why the authors of automake would try to restrict different and
> actually valid usage scenarios? I've been using this setup for over 5 years
> in different projects, I'd be really disappointed if I had to switch to a
>
John,
On Sun, Sep 01, 2013 at 03:11:11PM -0600, John Calcote wrote:
> I'm curious as to why it's important to you that build products not land in
> the
> source tree, especially in light of the fact that you're clearly aware of
> automake's support for out-of-tree builds. Out-of-tree builds exist
Sergey,
I'm curious as to why it's important to you that build products not land in
the source tree, especially in light of the fact that you're clearly aware
of automake's support for out-of-tree builds. Out-of-tree builds exist to
solve the very problem you're trying so hard to fix.
Be aware th
Hi,
OK, never mind, problem solved. It seems that $(top_srcdir) simply did not
expand anymore in _SOURCES. Keeping my structure with the build/Makefile.am
but replacing $(top_srcdir) with '..' did the trick, it works
like a charm now, including in and out of tree builds.
No more warnings, no more
Hi,
thanks for your reply, some more questions though:
On Sun, Sep 01, 2013 at 03:08:37PM +0100, Diego Elio Pettenò wrote:
> Is it possible to keep the logic with the in-tree build directory with
> automake 1.14? I did try to move all the logic from build/Makefile.am into
> the top le
On Sat, Aug 31, 2013 at 11:50 PM, Sergey 'Jin' Bostandzhyan <
j...@mediatomb.cc> wrote:
>
> Is it possible to keep the logic with the in-tree build directory with
> automake 1.14? I did try to move all the logic from build/Makefile.am into
> the top level Makefile.am and removing build/Makefile.am
On Sat, Aug 31, 2013 at 11:36 PM, Kerrick Staley
wrote:
> git checkout with-subdir-objects
> git clean -dfx
> ./autogen.sh
> make
> find . > /tmp/with-subdir-objects-tree
> git checkout without-subdir-objects
> git clean -dfx
> ./autogen.sh
> make
> find . > /tmp/without-subdir-objects-tree
> diff
Hi,
I have a project that compiles perfectly under automake 1.11 and 1.12,
but the scripts give warnings with 1.14, complaining that source file
xyz is in a subdirectory, but option 'subdir-objects' is disabled.
So, I simply enabled the above option, thinking that this would do the trick,
however
Hi,
I'm having trouble understanding what the subdir-objects option does. The
project I'm building [1] prints a warning when building without
subdir-objects:
libgd/Makefile.am:29: warning: source file 'libgd/gd-types-catalog.c' is in
a subdirectory,
libgd/Makefile.am:29: but option 'subdir-object
12 matches
Mail list logo
