-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-02-21 17:15, Hans-Christoph Steiner wrote: >> - - should /usr/include/m_pd.h be handled likewise, using >> update-alternatives? again, i'm not sure whether this is good style and >> cannot find such a thing on my system.... > > Pd-extended's headers are in /usr/include/pdextended only. If anything > depends on them, that should be explicit, i.e. #include > <pdextended/s_stuff.h>. This also allows for a parallel installation of the > puredata headers, so no need to mix the two up. >
hmm, but this will prevent the external to be buildable without having a full installation of pdextended (e.g. both the external-code and pd-extended are only available as a vcs-checkout) is this by design? while auto-building pd-extended, do you add an include-path that allows <pdextended/m_pd.h> to be included? it also means, that you cannot make an external that builds for both pd-vanilla and pd-extended without some #ifdef trickery and user interaction (or some build-system (like autoconf) that detects whether pd and/or pd-extended is present). finally, the pdextended.pc pkg-config snippet is nevertheless broken. fgmasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9DxZoACgkQkX2Xpv6ydvQ/1QCeN4Q9OFXTezbVvZmhfIzoawwW c4kAoMEplGqK/8nt1tsltN3DCV7AUIyC =R6Jv -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
