Well, it now ends up with:
libOSCFaust.0.93.dylib libOSCFaust.1.dylib libOSCFaust.dylib
That'll work for most purposes I guess, but are you really really sure that
you want that to be libOSCFaust.0.93.dylib and not
libOSCFaust.1.0.93.dylib?? It's customary to have the so version included
in the full library name, so this looks rather odd. Compare with `ls
/usr/lib/libz*.dylib` to see what I mean.
Also, `make install` creates deep copies of the symbolic links during
installation. But that's my fault, as I simply copied the command from the
httpd lib. Will fix that right away.
Albert
On Wed, Sep 24, 2014 at 3:28 PM, Sarah Denoux <sden...@grame.fr> wrote:
> It's committed. Let me know if there's another issue.
> Sarah
>
> Le 24 sept. 2014 à 14:58, Albert Graef a écrit :
>
> Note that this actually affects two Makefiles, osclib/Makefile and
> osclib/faust/Makefile. Just to make sure...
>
> On Wed, Sep 24, 2014 at 2:56 PM, Albert Graef <aggr...@gmail.com> wrote:
>
>> Better you do it so that I don't mess things up again. :)
>>
>> On Wed, Sep 24, 2014 at 2:43 PM, Sarah Denoux <sden...@grame.fr> wrote:
>>
>>> Hi Albert,
>>>
>>> we just came stepped on this problem with Dominique and it should
>>> be $(SOVERSION) instead of $(SOVERSION).$(VERSION). Do you want to change
>>> it or should I ?
>>>
>>> Sarah
>>>
>>>
>>> Le 24 sept. 2014 à 13:45, Albert Graef a écrit :
>>>
>>> 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
>>>
>>>
>>>
>>
>>
>> --
>> Dr. Albert Gr"af
>> Computer Music Research Group, JGU Mainz, Germany
>> Email: aggr...@gmail.com
>> WWW: https://plus.google.com/+AlbertGraef
>>
>
>
>
> --
> Dr. Albert Gr"af
> Computer Music Research Group, JGU Mainz, Germany
> Email: aggr...@gmail.com
> WWW: https://plus.google.com/+AlbertGraef
>
>
>
--
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
