I can still try to build on my spare, don't hesitate to ask me if needed
I made my test on
https://github.com/pure-data/pure-data/commit/d8d637b6c53833c49c47c60ff78e3fbfd0d596c7
(currently 0.50-2 tag)
Le mer. 29 janv. 2020 à 16:00, Miller Puckette via Pd-list <
pd-list@lists.iem.at> a écrit :
>
Sure enough - I added binarymsg.c since my last Max-compile attempt, and
yes, things like A_FLOAT will conflict with Max. I'll get in and patch
that up at least.
cheers
Miller
On Wed, Jan 29, 2020 at 10:43:07AM +0100, cyrille henry wrote:
> most redefinition are a conflict between liboscia and
You could also consider using [mrpeach/slipenc] and [mrpeach/slipdec]
around the [comport] object, which allows you to perform OSC style
communication using [mrpeach/packOSC] and [mrpeach/unpackOSC]. Just
check the examples in the mrpeach library.
Le 29/01/2020 à 11:00,
btw, you can still try it on your own thanks to some macos vagrant box.
Le mer. 29 janv. 2020 à 11:23, Antoine Villeret
a écrit :
> > most redefinition are a conflict between liboscia and m_pd.h
>
> I don't think so, libossia appears in the log because this is where the
> max-sdk is and that's
> most redefinition are a conflict between liboscia and m_pd.h
I don't think so, libossia appears in the log because this is where the
max-sdk is and that's all.
If I move the max-sdk to another folder I got exactly the same redefinition
errors.
> But I don't know if m_ph.h should be included
>
most redefinition are a conflict between liboscia and m_pd.h
I would try to remove liboscia from your compilled path.
But I don't know if m_ph.h should be included :
it is removed for max from pd~ source thanks to a #define line 54 :
#ifdef PD
#include "m_pd.h"
#include "s_stuff.h"
static
Hi,
I just give a try without much success.
There are lots of symbol redefinition errors.
Here is the full output :
https://gist.github.com/avilleret/19bfb74c84cc49b27bd8610545748044
I need some hint to go further with this.
Cheers
a
Le mar. 28 janv. 2020 à 09:52, Alexandre Torres Porres a
