[PD-dev] definitions in m_pd.h that aren't present in pd (and vice versa)
Hi, I'm trying to use SWIG in my work on a Lua external for Pd, and had to comment out the following definitions in m_pd.h to get code generated by SWIG to load without "undefined symbol" errors: EXTERN t_symbol *pd_getfilename(void); EXTERN t_symbol *pd_getdirname(void); EXTERN void pd_anything(t_pd *x, t_symbol *s, int argc, t_atom *argv); EXTERN t_parentwidgetbehavior *class_parentwidget(t_class *c); EXTERN int sys_isreadablefile(const char *name); EXTERN float garray_get(t_garray *x, t_symbol *s, t_int indx); EXTERN void c_extern(t_externclass *cls, t_newmethod newroutine, t_method freeroutine, t_symbol *name, size_t size, int tiny, t_atomtype arg1, ...); EXTERN void c_addmess(t_method fn, t_symbol *sel, t_atomtype arg1, ...); I guess these have either been removed from pd, or aren't declared with the right visibility in the source. It would be great if this could be fixed. Also, the following are visible in pd, but undeclared in m_pd.h, meaning I have to declare them myself: typedef int (*loader_t)(t_canvas *, char *); void sys_register_loader(loader_t loader); Would be super if this could be fixed too. Tested with pd-0.40-2 from Miller's site. Claude -- http://claudiusmaximus.goto10.org ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] add_string_support.patch
Hans-Christoph Steiner wrote: > I just noticed this in the build logs. Looks like the patch isn't > applied at all. I think the problem is that there is a relative path > in the filenames, while the working ones just have the filename, i.e. > this doesn't work: > > |--- pd/src/g_text.c 4 Oct 2006 19:35:06 - 1.15 > |+++ pd/src/g_text.c 12 Feb 2007 03:45:43 - > > > This works: > > > --- g_rtext.c 6 Sep 2004 20:20:34 - 1.4 > +++ g_rtext.c 14 Dec 2005 03:59:31 - > > > .hc > > > > > Applying /home/pd/auto-build/pd-extended/packages/patches/ > add_string_support.patch > can't find file to patch at input line 8 > Perhaps you used the wrong -p or --strip option? so perhaps you used the wrong -p or --strip option... try "-p 2" fmga.sdr IOhannes ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] add_string_support.patch
I just noticed this in the build logs. Looks like the patch isn't applied at all. I think the problem is that there is a relative path in the filenames, while the working ones just have the filename, i.e. this doesn't work: |--- pd/src/g_text.c4 Oct 2006 19:35:06 - 1.15 |+++ pd/src/g_text.c12 Feb 2007 03:45:43 - This works: --- g_rtext.c 6 Sep 2004 20:20:34 - 1.4 +++ g_rtext.c 14 Dec 2005 03:59:31 - .hc Applying /home/pd/auto-build/pd-extended/packages/patches/ add_string_support.patch can't find file to patch at input line 8 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: pd/src/g_text.c |=== |RCS file: /cvsroot/pure-data/pd/src/g_text.c,v |retrieving revision 1.15 |diff -u -w -r1.15 g_text.c |--- pd/src/g_text.c4 Oct 2006 19:35:06 - 1.15 |+++ pd/src/g_text.c12 Feb 2007 03:45:43 - -- File to patch: Skip this patch? [y] Skipping patch. 3 out of 3 hunks ignored can't find file to patch at input line 49 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: pd/src/m_atom.c |=== |RCS file: /cvsroot/pure-data/pd/src/m_atom.c,v |retrieving revision 1.4 |diff -u -w -r1.4 m_atom.c |--- pd/src/m_atom.c11 Aug 2006 20:09:07 - 1.4 |+++ pd/src/m_atom.c12 Feb 2007 03:45:43 - -- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 71 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: pd/src/m_binbuf.c |=== |RCS file: /cvsroot/pure-data/pd/src/m_binbuf.c,v |retrieving revision 1.13 |diff -u -w -r1.13 m_binbuf.c |--- pd/src/m_binbuf.c 4 Oct 2006 19:35:06 - 1.13 |+++ pd/src/m_binbuf.c 12 Feb 2007 03:45:44 - -- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 89 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: pd/src/m_class.c |=== |RCS file: /cvsroot/pure-data/pd/src/m_class.c,v |retrieving revision 1.7 |diff -u -w -r1.7 m_class.c |--- pd/src/m_class.c 15 Aug 2006 04:54:15 - 1.7 |+++ pd/src/m_class.c 12 Feb 2007 03:45:44 - -- File to patch: Skip this patch? [y] Skipping patch. 9 out of 9 hunks ignored can't find file to patch at input line 206 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: pd/src/m_imp.h |=== |RCS file: /cvsroot/pure-data/pd/src/m_imp.h,v |retrieving revision 1.4 |diff -u -w -r1.4 m_imp.h |--- pd/src/m_imp.h 19 Aug 2005 23:28:03 - 1.4 |+++ pd/src/m_imp.h 12 Feb 2007 03:45:44 - -- File to patch: Skip this patch? [y] Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 229 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: pd/src/m_obj.c |=== |RCS file: /cvsroot/pure-data/pd/src/m_obj.c,v |retrieving revision 1.4 |diff -u -w -r1.4 m_obj.c |--- pd/src/m_obj.c 18 May 2005 04:28:51 - 1.4 |+++ pd/src/m_obj.c 12 Feb 2007 03:45:44 - -- File to patch: Skip this patch? [y] Skipping patch. 6 out of 6 hunks ignored can't find file to patch at input line 334 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: pd/src/m_pd.c |=== |RCS file: /cvsroot/pure-data/pd/src/m_pd.c,v |retrieving revision 1.4 |diff -u -w -r1.4 m_pd.c |--- pd/src/m_pd.c 28 Nov 2004 21:20:42 - 1.4 |+++ pd/src/m_pd.c 12 Feb 2007 03:45:44 - -- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 354 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |Index: pd/src/m_pd.h |=== |RCS file: /cvsroot/pure-data/pd/src/m_pd.h,v |retrieving revision 1.17 |diff -u -w -r1.17 m_pd.h |--- pd/src/m_pd.h 22 Oct 2006 21:46:11 - 1.17 |+++ pd/src/m_pd.h 12 Feb 2007 03:45:44 - -- File to patch: Skip this patch? [y] Skipping patch.
