Csound Csound-dev Csound-tekno Search About

[Csnd-dev] Renamed STK and HDF5 opcode library names

Date2016-02-27 18:16
FromSteven Yi
Subject[Csnd-dev] Renamed STK and HDF5 opcode library names
Hi All,

I've put in a change to rename the opcode library builds for STK and
HDF5 to create libraries called libstkops.so and libhdf5ops.so (or
stkops.dll and hdf5ops.dll on Windows).  The reason for this is that
the previous names were the same as the libraries the opcodes were
linking to. This caused a lot of problems for me in the past when
building on OSX but I largely ignored them as it would largely get
through building if configuration wasn't redone in the same folder.
However, the problem has crept up for others and myself again and I
went ahead and changed those.

The result is that we should no longer have any issues with linking
when building those two libraries. On the other hand, we will need to
update any installer scripts that referenced those opcode libraries by
name.  Also, if you have been building from GIT, you may need to
manually delete libstk.so and libhdf5.so from your opcode directory
(or stk.dll and hdf5.dll).  I think this may be a small annoyance but
the benefit of fixing this issue permanently should be worth it.

If there's any other issues that come up, please let me know or feel
free to make a change directly to GIT.

Thanks!

Date2016-02-27 18:34
FromMichael Gogins
SubjectRe: [Csnd-dev] Renamed STK and HDF5 opcode library names
That sounds good.

Best,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sat, Feb 27, 2016 at 1:16 PM, Steven Yi  wrote:
> Hi All,
>
> I've put in a change to rename the opcode library builds for STK and
> HDF5 to create libraries called libstkops.so and libhdf5ops.so (or
> stkops.dll and hdf5ops.dll on Windows).  The reason for this is that
> the previous names were the same as the libraries the opcodes were
> linking to. This caused a lot of problems for me in the past when
> building on OSX but I largely ignored them as it would largely get
> through building if configuration wasn't redone in the same folder.
> However, the problem has crept up for others and myself again and I
> went ahead and changed those.
>
> The result is that we should no longer have any issues with linking
> when building those two libraries. On the other hand, we will need to
> update any installer scripts that referenced those opcode libraries by
> name.  Also, if you have been building from GIT, you may need to
> manually delete libstk.so and libhdf5.so from your opcode directory
> (or stk.dll and hdf5.dll).  I think this may be a small annoyance but
> the benefit of fixing this issue permanently should be worth it.
>
> If there's any other issues that come up, please let me know or feel
> free to make a change directly to GIT.
>
> Thanks!