[PD] putting m_imp.h into /usr/local/include

Miller Puckette mpuckett at man104-1.ucsd.edu
Tue Oct 29 06:20:39 CET 2002

Hi all,

It's quite possible that things in m_imp.h will change incompatibly with
new versions of Pd... all that is in m_pd.h is in principle stable.  So
if you write externs using m_imp.h just be prepared for them to have to get 
re-written now and then...!


On Mon, Oct 28, 2002 at 08:29:21PM -0500, Marc Lavallée wrote:
> Le lun 28/10/2002 à 19:46, Hans-Christoph Steiner a écrit :
> > 
> > Is there any reason why it would be bad to put the m_imp.h file from pd
> > into the include path?  I guess technically these are not suppossed to be
> > 'public' definitions, yet it seems that many externals need to include
> > this file. Its not stuck in the $PREFIX/include directory.
> Because PD needs a root directory, usually "/usr/lib/pd", it makes sense
> to leave everything related to pd in that directory. There's many other
> headers file, so in the case you'd like to put them under
> "/usr/include", it'd be better to put them in a "/usr/include/pd"
> subdir, which is not better than "/usr/lib/pd/include". If you really
> want to, create a "/usr/include/pd" symbolic link to
> "/usr/lib/pd/include". The "pd", "pdsend" and "pdreceive" binaries
> better be in "/usr/bin", since they are executables.
> --
> Marc
> _______________________________________________
> PD-list mailing list
> PD-list at iem.kug.ac.at
> http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list

More information about the Pd-list mailing list