Hi Stéphane,
thanks, that was quick. :) Also nice to see that osclib can now be built as
a dylib.
I still had to fix up some of the targets in the toplevel Makefile so that
the OSC dylib gets installed as well. I already committed that.
There seems to be some confusion about the versioning of the dylib in
osclib, though. In any case one of the dynamic links was broken, so I fixed
that, but this needs to be reviewed. If you really want to go all the way,
then it should probably be something like libOSCFaust.dylib ->
libOSCFaust.1.dylib -> libOSCFaust.1.0.93.dylib, assuming that 1 is the
major version and 0.93 the minor version and patchlevel. See
http://docstore.mik.ua/orelly/unix3/mac/ch05_04.htm.
Right now it's more like libOSCFaust.dylib, libOSCFaust.1.dylib ->
libOSCFaust.0.93.dylib, so I'd say that $(VERSION) needs to be replaced by
$(SOVERSION).$(VERSION), right?
I can fix that, just let me know.
Albert
On Wed, Sep 24, 2014 at 10:01 AM, Stéphane Letz <l...@grame.fr> wrote:
> Already committed.
>
> Stéphane
>
> Le 24 sept. 2014 à 08:48, Albert Graef <aggr...@gmail.com> a écrit :
>
> > On Wed, Sep 24, 2014 at 8:33 AM, Albert Graef <aggr...@gmail.com> wrote:
> > Or should I commit my changes to the Makefiles? (There's obviously some
> option in the c++ link command still missing for building universal
> binaries, though.)
> >
> > Just adding $(ARCHFLAGS) to the c++ linker command does the trick.
> Corrected diffs attached.
> >
> > Is it ok to commit this? I don't really see why anyone would want to use
> an archaic tool like Xcode's libtool to link dylibs when the system
> compiler does the job just fine. Is there any reason for that?
> >
> > Albert
> >
> > --
> > Dr. Albert Gr"af
> > Computer Music Research Group, JGU Mainz, Germany
> > Email: aggr...@gmail.com
> > WWW: https://plus.google.com/+AlbertGraef
> >
> <osx-dynamic.diff>------------------------------------------------------------------------------
> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk_______________________________________________
> > Faudiostream-devel mailing list
> > Faudiostream-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
>
>
--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggr...@gmail.com
WWW: https://plus.google.com/+AlbertGraef
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Faudiostream-devel mailing list
Faudiostream-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
