| :D
BTW: I see what the issue is with Lua JIT: the package for mingw64
only installs the shared library version of luajit and does not
install the static libraries for linking. That's causing all of the
Lua-related stuff (lua opcodes, lua interface, csound AC lua
interface) from linking. We'll need to either create our own Luajit
package, or modify and submit back to MSYS an updated luajit PKGBUILD
file that can create the static libs.
On Tue, Jan 19, 2016 at 11:32 AM, Ed Costello wrote:
> Thats great Steven, thanks :)
>
> On Tue, 19 Jan 2016 at 15:38 Steven Yi wrote:
>>
>> Update: websockets opcodes now building.
>>
>> On Tue, Jan 19, 2016 at 9:23 AM, Steven Yi wrote:
>> > Update: hdf5 opcodes now building. This requires the latest hdf5
>> > library package installed that was updated today (the latest has the
>> > static libraries we need for linking).
>> >
>> > On Thu, Jan 14, 2016 at 6:16 PM, Steven Yi wrote:
>> >> Update: I managed to get the OSC opcodes building. Note that for this,
>> >> I created a PKGBUILD script for liblo:
>> >>
>> >>
>> >> https://github.com/csound/csound/commit/c4d5face41ef319fe618849a5d09d0e4d10768a7
>> >>
>> >> The idea here is to keep as much of this happening via the pacman
>> >> package manager. Since we needed liblo and msys2's package repository
>> >> did not include it, I created the package description to build the
>> >> package. From there you will need to install the package and then
>> >> build csound. (README.md updated with this information).
>> >>
>> >> I will stop here for today but continue on tomorrow with STK. (I
>> >> should note that I cobbled together the liblo package descriptor by
>> >> reading through the one made for Arch Linux, then referencing the
>> >> mingw64 repository's packages to figure out what to do for that.)
>> >>
>> >>
>> >>
>> >> On Thu, Jan 14, 2016 at 1:40 PM, Steven Yi wrote:
>> >>> Yeah, you might be waiting awhile for that. :P
>> >>>
>> >>> On Thu, Jan 14, 2016 at 1:02 PM, Rory Walsh wrote:
>> >>>> You're making stellar progress there Steven! I'm sure it won't be
>> >>>> long
>> >>>> before you have a touch-screen interface to Csound64 on your Surface
>> >>>> Pro. I
>> >>>> look forward to some videos!
>> >>>>
>> >>>> On 14 January 2016 at 17:26, Steven Yi wrote:
>> >>>>>
>> >>>>> Update: I just got the fluidsynth opcodes compiling. Turns out you
>> >>>>> need to define FLUIDSYNTH_NOT_A_DLL to get the fluidsynth headers
>> >>>>> configured correctly when static linking. After adding additional
>> >>>>> libs, it's compiling and running here.
>> >>>>>
>> >>>>> On Wed, Jan 13, 2016 at 4:50 PM, Steven Yi
>> >>>>> wrote:
>> >>>>> > Hi All,
>> >>>>> >
>> >>>>> > I'm starting this thread to update status on MSYS2/mingw64 64-bit
>> >>>>> > Windows build. Just FYI:
>> >>>>> >
>> >>>>> > * Status of targets not building is now tracked in the README.md
>> >>>>> > within the mingw64 folder. I've added some information (i.e.
>> >>>>> > luajit-51
>> >>>>> > not linking though it's there...) for the targets I've looked at.
>> >>>>> > This
>> >>>>> > can be viewed online:
>> >>>>> >
>> >>>>> > https://github.com/csound/csound/tree/develop/mingw64
>> >>>>> >
>> >>>>> > * The build.sh script is what I've been using to build csound.
>> >>>>> > It's
>> >>>>> > hardcoding some build options there for the time being and those
>> >>>>> > values should be removed later as targets get working.
>> >>>>> >
>> >>>>> > * Not all of the dependencies we use for Csound are available
>> >>>>> > through
>> >>>>> > pacman (msys2's forked version of Arch Linux's pacman package
>> >>>>> > manager). I think it'd be best if for the dependencies we need,
>> >>>>> > we
>> >>>>> > try to make PKGCONFIG's for the dependencies to build packages for
>> >>>>> > msys2. We could contribute those back to msys2 or at least use
>> >>>>> > them
>> >>>>> > locally. Ultimately, it would be good to get a package working
>> >>>>> > for
>> >>>>> > Csound itself. That would allow windows users then to download
>> >>>>> > msys2
>> >>>>> > and install csound from pacman, similarly to how homebrew is
>> >>>>> > functioning on OSX.
>> >>>>> >
>> >>>>> > * Fluidsynth should be on the list as it is not currently building
>> >>>>> > (I
>> >>>>> > think it's a linking issue, need to revisit to see what was going
>> >>>>> > on)
>> >>>>> >
>> >>>>> > Other than, I'll be just be continuing on as time permits. I'll
>> >>>>> > probably look at fluidsynth next, then on to putting together a
>> >>>>> > liblo
>> >>>>> > package and getting the OSC opcodes going.
>> >>>>> >
>> >>>>> > Thanks,
>> >>>>> > steven
>> >>>>
>> >>>>
>
> -- |