On Oct 19, 2011, at 2:14 PM, IOhannes m zmölnig wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/19/2011 06:31 PM, Hans-Christoph Steiner wrote:
If pd/src/m_pd.h is the only thing that loads pd/src/config.h and
m_pd.h
does #include "config.h", this is not a problem.
"GCC looks for headers requested with #include "file" first in the
directory containing the current file".
http://gcc.gnu.org/onlinedocs/cpp/Search-Path.html
please keep in mind that it should work not only on gcc.
config.h is the standard name for the header generated by ./
configure.
I think they probably have thought of the above issues.
sure. i think you misunderstood me.
i'm totally fine with Pd using config.h for the normal configuration
output.
however, i am strongly opposed to distributing and installing a
generic
config.h as generated by configure.
no sane project i know does this.
the only project i ever encountered where a generated config.h file
was
shipped was libavifile on debian.
it severaly broke other builds that used autoconf/config.h
so to reiterate:
please do ship a file that contains the correct PD_FLOAT_PRECISION
define.
please never ship a file that contains generic autoconf definitions
from
the build machine, like HAVE_SYS_IOCTL_H.
therefore, please do NOT put the defines for PD_FLOAT_PRECISION into
the
same file as the generic defines as HAVE_SYS_IOCTL_H.
I don't really understand what you're saying here. I am proposing
that ./configure generate a config.h that includes a
PD_FLOAT_PRECISION definition and m_pd.h includes that config.h. As
far as I know the is standard procedure with autoconf.
.hc
----------------------------------------------------------------------------
"Making boring techno music is really easy with modern tools, but with
live coding, boring techno is much harder." - Chris McCormick
_______________________________________________
Pd-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/pd-dev
