Hi all,
it seems that some people still have doubts about building externals for Mac OS X... so, last week I successfully compiled a few externals for Mac OS X Intel and PPC. Here are the important parts from one of my makefiles (Intel Mac):
MACOSXCFLAGS = -DMACOSX -DPD
OPTIM = -O2
PARANOID = -Wall -W -Wstrict-prototypes
-Wno-unused -Wno-parentheses -Wno-switch
MACOSXSOUNDINCLUDE = -I$(RESOS)/modal_object -I$(RESOS)/waveguide_object
-I$(RESOS)/inertial_object
-I$(INTERS)/impact_interactor -I$(INTERS)/linpact_interactor
-I$(INTERS)/friction_interactor
CFLAGS = $(MACOSXCFLAGS) $(MACOSXINCLUDE) $(MACOSXSOUNDINCLUDE) $(OPTIM) $(PARANOID)
TARGET = friction_2modalb~
OBJ = friction_interactor.o modal_obj_b.o matrix_calc.o
all: $(TARGET).pd_darwin install
$(TARGET).pd_darwin: $(TARGET).o $(OBJ)
cd $(OBJDIR) ;
$(CC) -arch i386 -bundle -undefined suppress -flat_namespace
-o $(TARGET).pd_darwin $(TARGET).o $(OBJ) -lm
$(TARGET).o: $(TARGET).c
pd_modules.h
friction_interactor.h
modal_obj_b.h
matrix_calc.h
install: -strip -x $(OBJDIR)/$(TARGET).pd_darwin -mv $(OBJDIR)/$(TARGET).pd_darwin $(MACOSXBINDIR)
%.o: %.c
pd_modules.h
[ -d $(TOP)/obj_macosx ] || mkdir $(TOP)/obj_macosx
$(CC) -g $(CFLAGS) -c -o $(OBJDIR)/$@ $<
and to compile on a G4 I just changed -arch i386 to -arch ppc. They work great!
Hope this helps.
Greetings, Stefano
Is the -arch required? Could you build a native build by omitting
the -arch flag? How about building fat binaries?
It looks to me that the only thing different from the old style is
the -arch flag.
.hc
On Sep 21, 2006, at 2:56 AM, Stefano Papetti wrote:
Hi all,
it seems that some people still have doubts about building
externals for Mac OS X... so, last week I successfully compiled a few externals
for Mac OS X Intel and PPC. Here are the important parts from one of my makefiles (Intel Mac):MACOSXCFLAGS = -DMACOSX -DPD
OPTIM = -O2 PARANOID = -Wall -W -Wstrict-prototypes
-Wno-unused -Wno-parentheses -Wno-switchMACOSXSOUNDINCLUDE = -I$(RESOS)/modal_object -I$(RESOS)/ waveguide_object -I$(RESOS)/inertial_object
-I$(INTERS)/impact_interactor -I$(INTERS)/linpact_interactor -I$(INTERS)/friction_interactorCFLAGS = $(MACOSXCFLAGS) $(MACOSXINCLUDE) $(MACOSXSOUNDINCLUDE) $ (OPTIM) $(PARANOID)
TARGET = friction_2modalb~
OBJ = friction_interactor.o modal_obj_b.o matrix_calc.o
all: $(TARGET).pd_darwin install
$(TARGET).pd_darwin: $(TARGET).o $(OBJ) cd $(OBJDIR) ;
$(CC) -arch i386 -bundle -undefined suppress -flat_namespace
-o $(TARGET).pd_darwin $(TARGET).o $(OBJ) -lm$(TARGET).o: $(TARGET).c
pd_modules.h
friction_interactor.h
modal_obj_b.h
matrix_calc.hinstall: -strip -x $(OBJDIR)/$(TARGET).pd_darwin -mv $(OBJDIR)/$(TARGET).pd_darwin $(MACOSXBINDIR)
%.o: %.c
pd_modules.h [ -d $(TOP)/obj_macosx ] || mkdir $(TOP)/obj_macosx $(CC) -g $(CFLAGS) -c -o $(OBJDIR)/$@ $<and to compile on a G4 I just changed -arch i386 to -arch ppc. They work great!
Hope this helps.
Greetings, Stefano
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
The arc of history bends towards justice. - Dr. Martin Luther
King, Jr.
Hi,
I'm sorry but at present time our MacBook is away so I can't try it out.
I'd like to build universal binaries in the near future but I have to study Apple's documentation about them... It should be pretty simple: compile 2 kind of file object (one with the -arch i386 flag and the other with ppc) and them merge them at linking time. If I'm not wrong, the makefiles provided with Pd 0.40 for Mac OS X 10.4, do exactly that.
Best, Stefano
Is the -arch required? Could you build a native build by omitting the -arch flag? How about building fat binaries?
It looks to me that the only thing different from the old style is the -arch flag.
.hc
On Sep 21, 2006, at 2:56 AM, Stefano Papetti wrote:
Hi all,
it seems that some people still have doubts about building externals for Mac OS X... so, last week I successfully compiled a few externals for Mac OS X Intel and PPC. Here are the important parts from one of my makefiles (Intel Mac):
MACOSXCFLAGS = -DMACOSX -DPD
OPTIM = -O2 PARANOID = -Wall -W -Wstrict-prototypes
-Wno-unused -Wno-parentheses -Wno-switchMACOSXSOUNDINCLUDE = -I$(RESOS)/modal_object -I$(RESOS)/ waveguide_object -I$(RESOS)/inertial_object
-I$(INTERS)/impact_interactor -I$(INTERS)/linpact_interactor -I$(INTERS)/friction_interactorCFLAGS = $(MACOSXCFLAGS) $(MACOSXINCLUDE) $(MACOSXSOUNDINCLUDE) $ (OPTIM) $(PARANOID)
TARGET = friction_2modalb~
OBJ = friction_interactor.o modal_obj_b.o matrix_calc.o
all: $(TARGET).pd_darwin install
$(TARGET).pd_darwin: $(TARGET).o $(OBJ) cd $(OBJDIR) ;
$(CC) -arch i386 -bundle -undefined suppress -flat_namespace
-o $(TARGET).pd_darwin $(TARGET).o $(OBJ) -lm$(TARGET).o: $(TARGET).c
pd_modules.h
friction_interactor.h
modal_obj_b.h
matrix_calc.hinstall: -strip -x $(OBJDIR)/$(TARGET).pd_darwin -mv $(OBJDIR)/$(TARGET).pd_darwin $(MACOSXBINDIR)
%.o: %.c
pd_modules.h [ -d $(TOP)/obj_macosx ] || mkdir $(TOP)/obj_macosx $(CC) -g $(CFLAGS) -c -o $(OBJDIR)/$@ $<and to compile on a G4 I just changed -arch i386 to -arch ppc. They work great!
Hope this helps.
Greetings, Stefano
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
The arc of history bends towards justice. - Dr. Martin Luther King, Jr.
oh, and most importantly, my Mac Intel externals ONLY work within Pd 0.40
Stefano
Hi,
I'm sorry but at present time our MacBook is away so I can't try it out.
I'd like to build universal binaries in the near future but I have to study Apple's documentation about them... It should be pretty simple: compile 2 kind of file object (one with the -arch i386 flag and the other with ppc) and them merge them at linking time. If I'm not wrong, the makefiles provided with Pd 0.40 for Mac OS X 10.4, do exactly that.
Best, Stefano
Is the -arch required? Could you build a native build by omitting the -arch flag? How about building fat binaries?
It looks to me that the only thing different from the old style is the -arch flag.
.hc
On Sep 21, 2006, at 2:56 AM, Stefano Papetti wrote:
Hi all,
it seems that some people still have doubts about building externals for Mac OS X... so, last week I successfully compiled a few externals for Mac OS X Intel and PPC. Here are the important parts from one of my makefiles (Intel Mac):
MACOSXCFLAGS = -DMACOSX -DPD
OPTIM = -O2 PARANOID = -Wall -W -Wstrict-prototypes
-Wno-unused -Wno-parentheses -Wno-switchMACOSXSOUNDINCLUDE = -I$(RESOS)/modal_object -I$(RESOS)/ waveguide_object -I$(RESOS)/inertial_object
-I$(INTERS)/impact_interactor -I$(INTERS)/linpact_interactor -I$(INTERS)/friction_interactorCFLAGS = $(MACOSXCFLAGS) $(MACOSXINCLUDE) $(MACOSXSOUNDINCLUDE) $ (OPTIM) $(PARANOID)
TARGET = friction_2modalb~
OBJ = friction_interactor.o modal_obj_b.o matrix_calc.o
all: $(TARGET).pd_darwin install
$(TARGET).pd_darwin: $(TARGET).o $(OBJ) cd $(OBJDIR) ;
$(CC) -arch i386 -bundle -undefined suppress -flat_namespace
-o $(TARGET).pd_darwin $(TARGET).o $(OBJ) -lm$(TARGET).o: $(TARGET).c
pd_modules.h
friction_interactor.h
modal_obj_b.h
matrix_calc.hinstall: -strip -x $(OBJDIR)/$(TARGET).pd_darwin -mv $(OBJDIR)/$(TARGET).pd_darwin $(MACOSXBINDIR)
%.o: %.c
pd_modules.h [ -d $(TOP)/obj_macosx ] || mkdir $(TOP)/obj_macosx $(CC) -g $(CFLAGS) -c -o $(OBJDIR)/$@ $<and to compile on a G4 I just changed -arch i386 to -arch ppc. They work great!
Hope this helps.
Greetings, Stefano
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
The arc of history bends towards justice. - Dr. Martin Luther King, Jr.
Just so everyone knows, I've had almost no problems building externals on an intel mactel using the existing Pd-extended framework and replacing the source with the latest. (so "make flext", "make zexy" in the externals dir, etc.)
With much thanks to H-C!
David
On 21/09/06, Stefano Papetti papetti@sci.univr.it wrote:
Hi all,
it seems that some people still have doubts about building externals for Mac OS X... so, last week I successfully compiled a few externals for Mac OS X Intel and PPC. Here are the important parts from one of my makefiles (Intel Mac):
MACOSXCFLAGS = -DMACOSX -DPD
OPTIM = -O2 PARANOID = -Wall -W -Wstrict-prototypes
-Wno-unused -Wno-parentheses -Wno-switchMACOSXSOUNDINCLUDE = -I$(RESOS)/modal_object -I$(RESOS)/waveguide_object -I$(RESOS)/inertial_object
-I$(INTERS)/impact_interactor -I$(INTERS)/linpact_interactor -I$(INTERS)/friction_interactorCFLAGS = $(MACOSXCFLAGS) $(MACOSXINCLUDE) $(MACOSXSOUNDINCLUDE) $(OPTIM) $(PARANOID)
TARGET = friction_2modalb~
OBJ = friction_interactor.o modal_obj_b.o matrix_calc.o
all: $(TARGET).pd_darwin install
$(TARGET).pd_darwin: $(TARGET).o $(OBJ) cd $(OBJDIR) ;
$(CC) -arch i386 -bundle -undefined suppress -flat_namespace
-o $(TARGET).pd_darwin $(TARGET).o $(OBJ) -lm$(TARGET).o: $(TARGET).c
pd_modules.h
friction_interactor.h
modal_obj_b.h
matrix_calc.hinstall: -strip -x $(OBJDIR)/$(TARGET).pd_darwin -mv $(OBJDIR)/$(TARGET).pd_darwin $(MACOSXBINDIR)
%.o: %.c
pd_modules.h [ -d $(TOP)/obj_macosx ] || mkdir $(TOP)/obj_macosx $(CC) -g $(CFLAGS) -c -o $(OBJDIR)/$@ $<and to compile on a G4 I just changed -arch i386 to -arch ppc. They work great!
Hope this helps.
Greetings, Stefano
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hey David,
Just so everyone knows, I've had almost no problems building externals on an intel mactel using the existing Pd-extended framework and replacing the source with the latest. (so "make flext", "make zexy" in
does it mean even flext compiled ok for you? I'm wondering because i got reports concerning some problem with assembly code used for atomic operations. greetings, Thomas
Hi Thomas,
Yep, absolutely. Flext, pool, I think even dyn~. Now, I'm not sure if maybe some of the make settings should actually be changed for the compilation. But I can confirm that they do compile and work in Pd.
Cheers, David
On 22/09/06, Thomas Grill gr@grrrr.org wrote:
Hey David,
Just so everyone knows, I've had almost no problems building externals on an intel mactel using the existing Pd-extended framework and replacing the source with the latest. (so "make flext", "make zexy" in
does it mean even flext compiled ok for you? I'm wondering because i got reports concerning some problem with assembly code used for atomic operations. greetings, Thomas
David NG McCallum schrieb:
Hi Thomas,
Yep, absolutely. Flext, pool, I think even dyn~. Now, I'm not sure if maybe some of the make settings should actually be changed for the compilation. But I can confirm that they do compile and work in Pd.
hmmm, great... did you use the current cvs versions?
thanks, Thomas
CVS versions, I think. I'm not sure if I had problems with pool and downloaded the package or not... I can't remember.
GCC :i686-apple-darwin8-gcc-4.0.1
The one that comes with the machine.
David
On 22/09/06, Thomas Grill gr@grrrr.org wrote:
ah, and which gcc version?
David NG McCallum schrieb:
Hi Thomas,
Yep, absolutely. Flext, pool, I think even dyn~. Now, I'm not sure if maybe some of the make settings should actually be changed for the compilation. But I can confirm that they do compile and work in Pd.
David NG McCallum a écrit :
Hi Thomas,
Yep, absolutely. Flext, pool, I think even dyn~. Now, I'm not sure if maybe some of the make settings should actually be changed for the compilation. But I can confirm that they do compile and work in Pd.
hello, did you by chance try pyext?
v
Cheers, David
On 22/09/06, Thomas Grill gr@grrrr.org wrote:
Hey David,
Just so everyone knows, I've had almost no problems building externals on an intel mactel using the existing Pd-extended framework and replacing the source with the latest. (so "make flext", "make zexy" in
does it mean even flext compiled ok for you? I'm wondering because i got reports concerning some problem with assembly code used for atomic operations. greetings, Thomas
Nope! I haven't tried that external for a while...
D
On 22/09/06, vincent rioux vincent.rioux@no-log.org wrote:
David NG McCallum a écrit :
Hi Thomas,
Yep, absolutely. Flext, pool, I think even dyn~. Now, I'm not sure if maybe some of the make settings should actually be changed for the compilation. But I can confirm that they do compile and work in Pd.
hello, did you by chance try pyext?
v
Cheers, David
On 22/09/06, Thomas Grill gr@grrrr.org wrote:
Hey David,
Just so everyone knows, I've had almost no problems building externals on an intel mactel using the existing Pd-extended framework and replacing the source with the latest. (so "make flext", "make zexy" in
does it mean even flext compiled ok for you? I'm wondering because i got reports concerning some problem with assembly code used for atomic operations. greetings, Thomas