on Git.  Packages for iOS, Android and Windows plus sources and
release notes.  Other packages to follow soon.

This release has many many bug fixes, code improvements and new ways
to use arrays.  

We also have extended the testing scheme so maybe this
will be the least buggy release ever...???
==John ffitch

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

OSX 10.6 package is now up there.

Victor
On 19 Oct 2013, at 13:55, john ffitch wrote:

> on Git.  Packages for iOS, Android and Windows plus sources and
> release notes.  Other packages to follow soon.
> 
> This release has many many bug fixes, code improvements and new ways
> to use arrays.  
> 
> We also have extended the testing scheme so maybe this
> will be the least buggy release ever...???
> ==John ffitch
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

Just FYI: I've just pushed an OSX 10.8 release.  I included the
csound~ installer with the DMG.

On Sat, Oct 19, 2013 at 1:04 PM, peiman khosravi
 wrote:
> I've just installed this package but it doesn't seem to contain csound~.
> Does it?
>
> Thanks
> Peiman
>
>
>
>
> www.peimankhosravi.co.uk || RSS Feed || Concert News
>
>
> On 19 October 2013 15:33, Victor Lazzarini  wrote:
>>
>> OSX 10.6 package is now up there.
>>
>> Victor
>> On 19 Oct 2013, at 13:55, john ffitch wrote:
>>
>> > on Git.  Packages for iOS, Android and Windows plus sources and
>> > release notes.  Other packages to follow soon.
>> >
>> > This release has many many bug fixes, code improvements and new ways
>> > to use arrays.
>> >
>> > We also have extended the testing scheme so maybe this
>> > will be the least buggy release ever...???
>> > ==John ffitch
>> >
>> >
>> > Send bugs reports to the Sourceforge bug trackers
>> > csound6:
>> >            https://sourceforge.net/p/csound/tickets/
>> > csound5:
>> >            https://sourceforge.net/p/csound/bugs/
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>> >
>> >
>>
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>>
>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>

On Sat, Oct 19, 2013 at 9:55 AM, john ffitch  wrote:
> on Git.  Packages for iOS, Android and Windows plus sources and
> release notes.  Other packages to follow soon.

I think I made a mistake. I pushed a small fix to the release/6.01
branch, but the release has already been done!

I also found a small anomaly. The Opcodes/CMakeLists.txt says:

    include_directories(${LUA_H_PATH}/luajit-2.0)


Why is that path appended? I thought LUA_H_PATH pointed to where lua.h
lives (which would mean that adding luajit-2.0 would point nowhere).




-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Felipe,

Thanks for commit that fix; it looks like the OSX installer I uploaded
does *not* have the fluidsynth opcode due to that. I'm going to
rebuild that now.  The iOS and Android builds are not affected though
as the former does not do builds for Fluidsynth and the latter has
it's own build file.

As for the lua stuff, the LUA_H_PATH is getting defined with:

find_path(LUA_H_PATH luajit-2.0/lua.h)

So I think the path would then get set to something like
"/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
found, then the luajit-2.0 would need to get appended to that.  I'm
pretty sure I wrote it that way, but if it's not working, then it
needs to be fixed.

Thanks!
steven

On Sat, Oct 19, 2013 at 5:44 PM, Felipe Sateler  wrote:
> On Sat, Oct 19, 2013 at 9:55 AM, john ffitch  wrote:
>> on Git.  Packages for iOS, Android and Windows plus sources and
>> release notes.  Other packages to follow soon.
>
> I think I made a mistake. I pushed a small fix to the release/6.01
> branch, but the release has already been done!
>
> I also found a small anomaly. The Opcodes/CMakeLists.txt says:
>
>     include_directories(${LUA_H_PATH}/luajit-2.0)
>
>
> Why is that path appended? I thought LUA_H_PATH pointed to where lua.h
> lives (which would mean that adding luajit-2.0 would point nowhere).
>
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
> Hi Felipe,
>
> Thanks for commit that fix; it looks like the OSX installer I uploaded
> does *not* have the fluidsynth opcode due to that. I'm going to
> rebuild that now.  The iOS and Android builds are not affected though
> as the former does not do builds for Fluidsynth and the latter has
> it's own build file.

But 6.01 has already been released, I thought the release branch was
supposed to be closed after the release. So I guess we have diverged a
bit from the git flow workflow.

>
> As for the lua stuff, the LUA_H_PATH is getting defined with:
>
> find_path(LUA_H_PATH luajit-2.0/lua.h)
>
> So I think the path would then get set to something like
> "/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
> found, then the luajit-2.0 would need to get appended to that.  I'm
> pretty sure I wrote it that way, but if it's not working, then it
> needs to be fixed.

Ah yes, that is correct. Then, I have a request. As far as I can
discern, luajit is supposed to be a drop-in replacement to standard
lua (at least, at build time). My request would be that csound not
assume that luajit is what is being used. Luajit is only available in
a limited number of architectures, therefore enabling lua opcodes and
interfaces in the other architectures.

As far as I can tell, this can be done entirely by defining the
appropriate paths in Custom.cmake instead of CMakeLists.txt (in fact,
I'm doing that to use standard lua instead of luajit). I can propose a
patch if this is acceptable (defaulting to luajit, of course)


-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Well, we haven't closed off the release branch yet. I guess we're not
quite going by the books here. It's alright I think as it's our first
time doing a git-flow release.

Two things:

1. The fluid opcodes don't compile here now since OPEN_MP was made
mandatory.  There is no OpenMP here on OSX but the fluid opcodes
worked alright without them in the past. To that effect, I've removed
the USE_OPEN_MP requirement and committed that.

2. From what I remember asking in an earlier email email thread,
LuaJIT is required for both the opcodes and SWIG wrapper, and plain
Lua is not acceptable.  If that means not having them on certain
platforms, I think that's alright. I know on OSX, we don't distribute
the Lua opcodes but do distribute the Lua wrapper due to an x86_64
issue with Luajit.



On Sat, Oct 19, 2013 at 6:56 PM, Felipe Sateler  wrote:
> On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
>> Hi Felipe,
>>
>> Thanks for commit that fix; it looks like the OSX installer I uploaded
>> does *not* have the fluidsynth opcode due to that. I'm going to
>> rebuild that now.  The iOS and Android builds are not affected though
>> as the former does not do builds for Fluidsynth and the latter has
>> it's own build file.
>
> But 6.01 has already been released, I thought the release branch was
> supposed to be closed after the release. So I guess we have diverged a
> bit from the git flow workflow.
>
>>
>> As for the lua stuff, the LUA_H_PATH is getting defined with:
>>
>> find_path(LUA_H_PATH luajit-2.0/lua.h)
>>
>> So I think the path would then get set to something like
>> "/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
>> found, then the luajit-2.0 would need to get appended to that.  I'm
>> pretty sure I wrote it that way, but if it's not working, then it
>> needs to be fixed.
>
> Ah yes, that is correct. Then, I have a request. As far as I can
> discern, luajit is supposed to be a drop-in replacement to standard
> lua (at least, at build time). My request would be that csound not
> assume that luajit is what is being used. Luajit is only available in
> a limited number of architectures, therefore enabling lua opcodes and
> interfaces in the other architectures.
>
> As far as I can tell, this can be done entirely by defining the
> appropriate paths in Custom.cmake instead of CMakeLists.txt (in fact,
> I'm doing that to use standard lua instead of luajit). I can propose a
> patch if this is acceptable (defaulting to luajit, of course)
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Just a sidenote, I'm realizing something is really off with my build.
It's essentially not finding any headers from /usr/local/include even
though I've got it in the Custom.cmake used with the build.  I'm
looking at redoing this build now...

On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
> Well, we haven't closed off the release branch yet. I guess we're not
> quite going by the books here. It's alright I think as it's our first
> time doing a git-flow release.
>
> Two things:
>
> 1. The fluid opcodes don't compile here now since OPEN_MP was made
> mandatory.  There is no OpenMP here on OSX but the fluid opcodes
> worked alright without them in the past. To that effect, I've removed
> the USE_OPEN_MP requirement and committed that.
>
> 2. From what I remember asking in an earlier email email thread,
> LuaJIT is required for both the opcodes and SWIG wrapper, and plain
> Lua is not acceptable.  If that means not having them on certain
> platforms, I think that's alright. I know on OSX, we don't distribute
> the Lua opcodes but do distribute the Lua wrapper due to an x86_64
> issue with Luajit.
>
>
>
> On Sat, Oct 19, 2013 at 6:56 PM, Felipe Sateler  wrote:
>> On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
>>> Hi Felipe,
>>>
>>> Thanks for commit that fix; it looks like the OSX installer I uploaded
>>> does *not* have the fluidsynth opcode due to that. I'm going to
>>> rebuild that now.  The iOS and Android builds are not affected though
>>> as the former does not do builds for Fluidsynth and the latter has
>>> it's own build file.
>>
>> But 6.01 has already been released, I thought the release branch was
>> supposed to be closed after the release. So I guess we have diverged a
>> bit from the git flow workflow.
>>
>>>
>>> As for the lua stuff, the LUA_H_PATH is getting defined with:
>>>
>>> find_path(LUA_H_PATH luajit-2.0/lua.h)
>>>
>>> So I think the path would then get set to something like
>>> "/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
>>> found, then the luajit-2.0 would need to get appended to that.  I'm
>>> pretty sure I wrote it that way, but if it's not working, then it
>>> needs to be fixed.
>>
>> Ah yes, that is correct. Then, I have a request. As far as I can
>> discern, luajit is supposed to be a drop-in replacement to standard
>> lua (at least, at build time). My request would be that csound not
>> assume that luajit is what is being used. Luajit is only available in
>> a limited number of architectures, therefore enabling lua opcodes and
>> interfaces in the other architectures.
>>
>> As far as I can tell, this can be done entirely by defining the
>> appropriate paths in Custom.cmake instead of CMakeLists.txt (in fact,
>> I'm doing that to use standard lua instead of luajit). I can propose a
>> patch if this is acceptable (defaulting to luajit, of course)
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Tested the new release with a big orchestra using python opcodes and
partikkel and it works like a charm.
Thanks and congratulations!
Oeyvind

2013/10/20 Steven Yi :
> Well, we haven't closed off the release branch yet. I guess we're not
> quite going by the books here. It's alright I think as it's our first
> time doing a git-flow release.
>
> Two things:
>
> 1. The fluid opcodes don't compile here now since OPEN_MP was made
> mandatory.  There is no OpenMP here on OSX but the fluid opcodes
> worked alright without them in the past. To that effect, I've removed
> the USE_OPEN_MP requirement and committed that.
>
> 2. From what I remember asking in an earlier email email thread,
> LuaJIT is required for both the opcodes and SWIG wrapper, and plain
> Lua is not acceptable.  If that means not having them on certain
> platforms, I think that's alright. I know on OSX, we don't distribute
> the Lua opcodes but do distribute the Lua wrapper due to an x86_64
> issue with Luajit.
>
>
>
> On Sat, Oct 19, 2013 at 6:56 PM, Felipe Sateler  wrote:
>> On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
>>> Hi Felipe,
>>>
>>> Thanks for commit that fix; it looks like the OSX installer I uploaded
>>> does *not* have the fluidsynth opcode due to that. I'm going to
>>> rebuild that now.  The iOS and Android builds are not affected though
>>> as the former does not do builds for Fluidsynth and the latter has
>>> it's own build file.
>>
>> But 6.01 has already been released, I thought the release branch was
>> supposed to be closed after the release. So I guess we have diverged a
>> bit from the git flow workflow.
>>
>>>
>>> As for the lua stuff, the LUA_H_PATH is getting defined with:
>>>
>>> find_path(LUA_H_PATH luajit-2.0/lua.h)
>>>
>>> So I think the path would then get set to something like
>>> "/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
>>> found, then the luajit-2.0 would need to get appended to that.  I'm
>>> pretty sure I wrote it that way, but if it's not working, then it
>>> needs to be fixed.
>>
>> Ah yes, that is correct. Then, I have a request. As far as I can
>> discern, luajit is supposed to be a drop-in replacement to standard
>> lua (at least, at build time). My request would be that csound not
>> assume that luajit is what is being used. Luajit is only available in
>> a limited number of architectures, therefore enabling lua opcodes and
>> interfaces in the other architectures.
>>
>> As far as I can tell, this can be done entirely by defining the
>> appropriate paths in Custom.cmake instead of CMakeLists.txt (in fact,
>> I'm doing that to use standard lua instead of luajit). I can propose a
>> patch if this is acceptable (defaulting to luajit, of course)
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://flyndresang.no/
http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://soundcloud.com/t-emp

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

... but if I rename my csound5 directory, I get warnings about missing
MSVCR110.dll, and a segfault.

Simplified csd that segfaults:





    sr = 48000
    ksmps = 10
    nchnls = 2
    0dbfs = 1

    giSine        ftgen    0, 0, 65536, 10, 1                ; sine wave

    instr 1

; get time
    kmetro        metro 1
    if kmetro > 0.5 then
    reinit getTime
    endif
getTime:
    itim         date
    Stim         dates   itim
    Shor         strsub  Stim, 11, 13
    Smin         strsub  Stim, 14, 16
    Ssec         strsub  Stim, 17, 19
    ihor        strtod    Shor
    imin        strtod    Smin
    isec        strtod    Ssec
            chnset    0, "hours"
            chnset    0, "minutes"
            chnset    0, "seconds"
    endin




;    start    dur
i1    0    10
e



2013/10/20 Oeyvind Brandtsegg :
> Tested the new release with a big orchestra using python opcodes and
> partikkel and it works like a charm.
> Thanks and congratulations!
> Oeyvind
>
> 2013/10/20 Steven Yi :
>> Well, we haven't closed off the release branch yet. I guess we're not
>> quite going by the books here. It's alright I think as it's our first
>> time doing a git-flow release.
>>
>> Two things:
>>
>> 1. The fluid opcodes don't compile here now since OPEN_MP was made
>> mandatory.  There is no OpenMP here on OSX but the fluid opcodes
>> worked alright without them in the past. To that effect, I've removed
>> the USE_OPEN_MP requirement and committed that.
>>
>> 2. From what I remember asking in an earlier email email thread,
>> LuaJIT is required for both the opcodes and SWIG wrapper, and plain
>> Lua is not acceptable.  If that means not having them on certain
>> platforms, I think that's alright. I know on OSX, we don't distribute
>> the Lua opcodes but do distribute the Lua wrapper due to an x86_64
>> issue with Luajit.
>>
>>
>>
>> On Sat, Oct 19, 2013 at 6:56 PM, Felipe Sateler  wrote:
>>> On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
>>>> Hi Felipe,
>>>>
>>>> Thanks for commit that fix; it looks like the OSX installer I uploaded
>>>> does *not* have the fluidsynth opcode due to that. I'm going to
>>>> rebuild that now.  The iOS and Android builds are not affected though
>>>> as the former does not do builds for Fluidsynth and the latter has
>>>> it's own build file.
>>>
>>> But 6.01 has already been released, I thought the release branch was
>>> supposed to be closed after the release. So I guess we have diverged a
>>> bit from the git flow workflow.
>>>
>>>>
>>>> As for the lua stuff, the LUA_H_PATH is getting defined with:
>>>>
>>>> find_path(LUA_H_PATH luajit-2.0/lua.h)
>>>>
>>>> So I think the path would then get set to something like
>>>> "/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
>>>> found, then the luajit-2.0 would need to get appended to that.  I'm
>>>> pretty sure I wrote it that way, but if it's not working, then it
>>>> needs to be fixed.
>>>
>>> Ah yes, that is correct. Then, I have a request. As far as I can
>>> discern, luajit is supposed to be a drop-in replacement to standard
>>> lua (at least, at build time). My request would be that csound not
>>> assume that luajit is what is being used. Luajit is only available in
>>> a limited number of architectures, therefore enabling lua opcodes and
>>> interfaces in the other architectures.
>>>
>>> As far as I can tell, this can be done entirely by defining the
>>> appropriate paths in Custom.cmake instead of CMakeLists.txt (in fact,
>>> I'm doing that to use standard lua instead of luajit). I can propose a
>>> patch if this is acceptable (defaulting to luajit, of course)
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>>>
>>> ------------------------------------------------------------------------------
>>> October Webinars: Code for Performance
>>> Free Intel webinars can help you accelerate application performance.
>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>>> the latest Intel processors and coprocessors. See abstracts and register >
>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> --
>
> Oeyvind Brandtsegg
> Professor of Music Technology
> NTNU
> 7491 Trondheim
> Norway
> Cell: +47 92 203 205
>
> http://flyndresang.no/
> http://www.partikkelaudio.com/
> http://soundcloud.com/brandtsegg
> http://soundcloud.com/t-emp



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://flyndresang.no/
http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://soundcloud.com/t-emp

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Re: Lua:

http://csound.1045644.n5.nabble.com/OSX-Lion-OpenMP-and-crashes-td4900923.html

The reply of mine further down has the answer (Oct 24,2011, 7:53pm).

On Sat, Oct 19, 2013 at 8:30 PM, Michael Gogins
 wrote:
> Something wouldn't compile without OpenMP on Windows, but this was a
> requirement by CmakeLists.txt, not an actual runtime requirement, I think.
>
> What is the OS X issue with LuaJIT? I think it should be OK, I will take
> another look at this in the LuaJIT list and installation guide.
>
> Regards,
> Mike
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
>>
>> Well, we haven't closed off the release branch yet. I guess we're not
>> quite going by the books here. It's alright I think as it's our first
>> time doing a git-flow release.
>>
>> Two things:
>>
>> 1. The fluid opcodes don't compile here now since OPEN_MP was made
>> mandatory.  There is no OpenMP here on OSX but the fluid opcodes
>> worked alright without them in the past. To that effect, I've removed
>> the USE_OPEN_MP requirement and committed that.
>>
>> 2. From what I remember asking in an earlier email email thread,
>> LuaJIT is required for both the opcodes and SWIG wrapper, and plain
>> Lua is not acceptable.  If that means not having them on certain
>> platforms, I think that's alright. I know on OSX, we don't distribute
>> the Lua opcodes but do distribute the Lua wrapper due to an x86_64
>> issue with Luajit.
>>
>>
>>
>> On Sat, Oct 19, 2013 at 6:56 PM, Felipe Sateler 
>> wrote:
>> > On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
>> >> Hi Felipe,
>> >>
>> >> Thanks for commit that fix; it looks like the OSX installer I uploaded
>> >> does *not* have the fluidsynth opcode due to that. I'm going to
>> >> rebuild that now.  The iOS and Android builds are not affected though
>> >> as the former does not do builds for Fluidsynth and the latter has
>> >> it's own build file.
>> >
>> > But 6.01 has already been released, I thought the release branch was
>> > supposed to be closed after the release. So I guess we have diverged a
>> > bit from the git flow workflow.
>> >
>> >>
>> >> As for the lua stuff, the LUA_H_PATH is getting defined with:
>> >>
>> >> find_path(LUA_H_PATH luajit-2.0/lua.h)
>> >>
>> >> So I think the path would then get set to something like
>> >> "/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
>> >> found, then the luajit-2.0 would need to get appended to that.  I'm
>> >> pretty sure I wrote it that way, but if it's not working, then it
>> >> needs to be fixed.
>> >
>> > Ah yes, that is correct. Then, I have a request. As far as I can
>> > discern, luajit is supposed to be a drop-in replacement to standard
>> > lua (at least, at build time). My request would be that csound not
>> > assume that luajit is what is being used. Luajit is only available in
>> > a limited number of architectures, therefore enabling lua opcodes and
>> > interfaces in the other architectures.
>> >
>> > As far as I can tell, this can be done entirely by defining the
>> > appropriate paths in Custom.cmake instead of CMakeLists.txt (in fact,
>> > I'm doing that to use standard lua instead of luajit). I can propose a
>> > patch if this is acceptable (defaulting to luajit, of course)
>> >
>> >
>> > --
>> >
>> > Saludos,
>> > Felipe Sateler
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > October Webinars: Code for Performance
>> > Free Intel webinars can help you accelerate application performance.
>> > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>> > from
>> > the latest Intel processors and coprocessors. See abstracts and register
>> > >
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>> from
>> the latest Intel processors and coprocessors. See abstracts and register >
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi All,

Just FYI: I have re-released the 6.01.0 build for OSX 10.8.  I had not
realized there was a build script problem causing many opcode
libraries not to be included with the release.  This should now be
fixed.

Thanks!
steven


On Sat, Oct 19, 2013 at 1:11 PM, Steven Yi  wrote:
> Just FYI: I've just pushed an OSX 10.8 release.  I included the
> csound~ installer with the DMG.
>
> On Sat, Oct 19, 2013 at 1:04 PM, peiman khosravi
>  wrote:
>> I've just installed this package but it doesn't seem to contain csound~.
>> Does it?
>>
>> Thanks
>> Peiman
>>
>>
>>
>>
>> www.peimankhosravi.co.uk || RSS Feed || Concert News
>>
>>
>> On 19 October 2013 15:33, Victor Lazzarini  wrote:
>>>
>>> OSX 10.6 package is now up there.
>>>
>>> Victor
>>> On 19 Oct 2013, at 13:55, john ffitch wrote:
>>>
>>> > on Git.  Packages for iOS, Android and Windows plus sources and
>>> > release notes.  Other packages to follow soon.
>>> >
>>> > This release has many many bug fixes, code improvements and new ways
>>> > to use arrays.
>>> >
>>> > We also have extended the testing scheme so maybe this
>>> > will be the least buggy release ever...???
>>> > ==John ffitch
>>> >
>>> >
>>> > Send bugs reports to the Sourceforge bug trackers
>>> > csound6:
>>> >            https://sourceforge.net/p/csound/tickets/
>>> > csound5:
>>> >            https://sourceforge.net/p/csound/bugs/
>>> > Discussions of bugs and features can be posted here
>>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> > csound"
>>> >
>>> >
>>>
>>> Dr Victor Lazzarini
>>> Senior Lecturer
>>> Dept. of Music
>>> NUI Maynooth Ireland
>>> tel.: +353 1 708 3545
>>> Victor dot Lazzarini AT nuim dot ie
>>>
>>>
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug trackers
>>> csound6:
>>>             https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>             https://sourceforge.net/p/csound/bugs/
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>

I copied MSVCR110.dll from the csound5/bin to csound6/bin and the
warning is gone, but csound6 segfaults on the "get time" example I
posted yesterday.
That is, it does compile fine if the old csound (5.19) is present on
my system (windows 7),
but csound6 segfaults on the csd if I rename the 5.19 install (so it
is not in my path).
Could there be other files, or other versions of files,
missing/changed between 5 and 6 that is the cause of this behaviour?
best
Oeyvind

2013/10/20 Michael Gogins :
> I'll look into that dll tomorrow. I'll probably have to add it to the
> Windows installer. The same thing happened to me here just now. In the
> meantime you should be able to google for and add that DLL to your csound
> bin dir.
>
> Regards,
> Mike
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sat, Oct 19, 2013 at 7:54 PM, Oeyvind Brandtsegg
>  wrote:
>>
>> ... but if I rename my csound5 directory, I get warnings about missing
>> MSVCR110.dll, and a segfault.
>>
>> Simplified csd that segfaults:
>> 
>> 
>> 
>> 
>>
>>     sr = 48000
>>     ksmps = 10
>>     nchnls = 2
>>     0dbfs = 1
>>
>>     giSine        ftgen    0, 0, 65536, 10, 1                ; sine wave
>>
>>     instr 1
>>
>> ; get time
>>     kmetro        metro 1
>>     if kmetro > 0.5 then
>>     reinit getTime
>>     endif
>> getTime:
>>     itim         date
>>     Stim         dates   itim
>>     Shor         strsub  Stim, 11, 13
>>     Smin         strsub  Stim, 14, 16
>>     Ssec         strsub  Stim, 17, 19
>>     ihor        strtod    Shor
>>     imin        strtod    Smin
>>     isec        strtod    Ssec
>>             chnset    0, "hours"
>>             chnset    0, "minutes"
>>             chnset    0, "seconds"
>>     endin
>>
>>
>> 
>> 
>> ;    start    dur
>> i1    0    10
>> e
>> 
>> 
>>
>> 2013/10/20 Oeyvind Brandtsegg :
>> > Tested the new release with a big orchestra using python opcodes and
>> > partikkel and it works like a charm.
>> > Thanks and congratulations!
>> > Oeyvind
>> >
>> > 2013/10/20 Steven Yi :
>> >> Well, we haven't closed off the release branch yet. I guess we're not
>> >> quite going by the books here. It's alright I think as it's our first
>> >> time doing a git-flow release.
>> >>
>> >> Two things:
>> >>
>> >> 1. The fluid opcodes don't compile here now since OPEN_MP was made
>> >> mandatory.  There is no OpenMP here on OSX but the fluid opcodes
>> >> worked alright without them in the past. To that effect, I've removed
>> >> the USE_OPEN_MP requirement and committed that.
>> >>
>> >> 2. From what I remember asking in an earlier email email thread,
>> >> LuaJIT is required for both the opcodes and SWIG wrapper, and plain
>> >> Lua is not acceptable.  If that means not having them on certain
>> >> platforms, I think that's alright. I know on OSX, we don't distribute
>> >> the Lua opcodes but do distribute the Lua wrapper due to an x86_64
>> >> issue with Luajit.
>> >>
>> >>
>> >>
>> >> On Sat, Oct 19, 2013 at 6:56 PM, Felipe Sateler 
>> >> wrote:
>> >>> On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi  wrote:
>> >>>> Hi Felipe,
>> >>>>
>> >>>> Thanks for commit that fix; it looks like the OSX installer I
>> >>>> uploaded
>> >>>> does *not* have the fluidsynth opcode due to that. I'm going to
>> >>>> rebuild that now.  The iOS and Android builds are not affected though
>> >>>> as the former does not do builds for Fluidsynth and the latter has
>> >>>> it's own build file.
>> >>>
>> >>> But 6.01 has already been released, I thought the release branch was
>> >>> supposed to be closed after the release. So I guess we have diverged a
>> >>> bit from the git flow workflow.
>> >>>
>> >>>>
>> >>>> As for the lua stuff, the LUA_H_PATH is getting defined with:
>> >>>>
>> >>>> find_path(LUA_H_PATH luajit-2.0/lua.h)
>> >>>>
>> >>>> So I think the path would then get set to something like
>> >>>> "/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
>> >>>> found, then the luajit-2.0 would need to get appended to that.  I'm
>> >>>> pretty sure I wrote it that way, but if it's not working, then it
>> >>>> needs to be fixed.
>> >>>
>> >>> Ah yes, that is correct. Then, I have a request. As far as I can
>> >>> discern, luajit is supposed to be a drop-in replacement to standard
>> >>> lua (at least, at build time). My request would be that csound not
>> >>> assume that luajit is what is being used. Luajit is only available in
>> >>> a limited number of architectures, therefore enabling lua opcodes and
>> >>> interfaces in the other architectures.
>> >>>
>> >>> As far as I can tell, this can be done entirely by defining the
>> >>> appropriate paths in Custom.cmake instead of CMakeLists.txt (in fact,
>> >>> I'm doing that to use standard lua instead of luajit). I can propose a
>> >>> patch if this is acceptable (defaulting to luajit, of course)
>> >>>
>> >>>
>> >>> --
>> >>>
>> >>> Saludos,
>> >>> Felipe Sateler
>> >>>
>> >>>
>> >>> ------------------------------------------------------------------------------
>> >>> October Webinars: Code for Performance
>> >>> Free Intel webinars can help you accelerate application performance.
>> >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
>> >>> most from
>> >>> the latest Intel processors and coprocessors. See abstracts and
>> >>> register >
>> >>>
>> >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> >>> _______________________________________________
>> >>> Csound-devel mailing list
>> >>> Csound-devel@lists.sourceforge.net
>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> October Webinars: Code for Performance
>> >> Free Intel webinars can help you accelerate application performance.
>> >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
>> >> most from
>> >> the latest Intel processors and coprocessors. See abstracts and
>> >> register >
>> >>
>> >> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>> >
>> >
>> > --
>> >
>> > Oeyvind Brandtsegg
>> > Professor of Music Technology
>> > NTNU
>> > 7491 Trondheim
>> > Norway
>> > Cell: +47 92 203 205
>> >
>> > http://flyndresang.no/
>> > http://www.partikkelaudio.com/
>> > http://soundcloud.com/brandtsegg
>> > http://soundcloud.com/t-emp
>>
>>
>>
>> --
>>
>> Oeyvind Brandtsegg
>> Professor of Music Technology
>> NTNU
>> 7491 Trondheim
>> Norway
>> Cell: +47 92 203 205
>>
>> http://flyndresang.no/
>> http://www.partikkelaudio.com/
>> http://soundcloud.com/brandtsegg
>> http://soundcloud.com/t-emp
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>> from
>> the latest Intel processors and coprocessors. See abstracts and register >
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://flyndresang.no/
http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://soundcloud.com/t-emp

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

No problem here, I have no 5.19 install here. What does the windows event log say?

Hmm can't seem to find any new entries when getting the segfault,
where would I expect to find it?
Looked in Event Log / Windows logs / Program, also looked in System
under the same path.
best
Oeyvind

2013/10/20 Michael Gogins :
> No problem here, I have no 5.19 install here. What does the windows event
> log say?
>
> On Oct 20, 2013 3:24 PM, "Oeyvind Brandtsegg" 
> wrote:
>>
>> I copied MSVCR110.dll from the csound5/bin to csound6/bin and the
>> warning is gone, but csound6 segfaults on the "get time" example I
>> posted yesterday.
>> That is, it does compile fine if the old csound (5.19) is present on
>> my system (windows 7),
>> but csound6 segfaults on the csd if I rename the 5.19 install (so it
>> is not in my path).
>> Could there be other files, or other versions of files,
>> missing/changed between 5 and 6 that is the cause of this behaviour?
>> best
>> Oeyvind
>>
>> 2013/10/20 Michael Gogins :
>> > I'll look into that dll tomorrow. I'll probably have to add it to the
>> > Windows installer. The same thing happened to me here just now. In the
>> > meantime you should be able to google for and add that DLL to your
>> > csound
>> > bin dir.
>> >
>> > Regards,
>> > Mike
>> >
>> >
>> > ===========================
>> > Michael Gogins
>> > Irreducible Productions
>> > http://michaelgogins.tumblr.com
>> > Michael dot Gogins at gmail dot com
>> >
>> >
>> > On Sat, Oct 19, 2013 at 7:54 PM, Oeyvind Brandtsegg
>> >  wrote:
>> >>
>> >> ... but if I rename my csound5 directory, I get warnings about missing
>> >> MSVCR110.dll, and a segfault.
>> >>
>> >> Simplified csd that segfaults:
>> >> 
>> >> 
>> >> 
>> >> 
>> >>
>> >>     sr = 48000
>> >>     ksmps = 10
>> >>     nchnls = 2
>> >>     0dbfs = 1
>> >>
>> >>     giSine        ftgen    0, 0, 65536, 10, 1                ; sine
>> >> wave
>> >>
>> >>     instr 1
>> >>
>> >> ; get time
>> >>     kmetro        metro 1
>> >>     if kmetro > 0.5 then
>> >>     reinit getTime
>> >>     endif
>> >> getTime:
>> >>     itim         date
>> >>     Stim         dates   itim
>> >>     Shor         strsub  Stim, 11, 13
>> >>     Smin         strsub  Stim, 14, 16
>> >>     Ssec         strsub  Stim, 17, 19
>> >>     ihor        strtod    Shor
>> >>     imin        strtod    Smin
>> >>     isec        strtod    Ssec
>> >>             chnset    0, "hours"
>> >>             chnset    0, "minutes"
>> >>             chnset    0, "seconds"
>> >>     endin
>> >>
>> >>
>> >> 
>> >> 
>> >> ;    start    dur
>> >> i1    0    10
>> >> e
>> >> 
>> >> 
>> >>
>> >> 2013/10/20 Oeyvind Brandtsegg :
>> >> > Tested the new release with a big orchestra using python opcodes and
>> >> > partikkel and it works like a charm.
>> >> > Thanks and congratulations!
>> >> > Oeyvind
>> >> >
>> >> > 2013/10/20 Steven Yi :
>> >> >> Well, we haven't closed off the release branch yet. I guess we're
>> >> >> not
>> >> >> quite going by the books here. It's alright I think as it's our
>> >> >> first
>> >> >> time doing a git-flow release.
>> >> >>
>> >> >> Two things:
>> >> >>
>> >> >> 1. The fluid opcodes don't compile here now since OPEN_MP was made
>> >> >> mandatory.  There is no OpenMP here on OSX but the fluid opcodes
>> >> >> worked alright without them in the past. To that effect, I've
>> >> >> removed
>> >> >> the USE_OPEN_MP requirement and committed that.
>> >> >>
>> >> >> 2. From what I remember asking in an earlier email email thread,
>> >> >> LuaJIT is required for both the opcodes and SWIG wrapper, and plain
>> >> >> Lua is not acceptable.  If that means not having them on certain
>> >> >> platforms, I think that's alright. I know on OSX, we don't
>> >> >> distribute
>> >> >> the Lua opcodes but do distribute the Lua wrapper due to an x86_64
>> >> >> issue with Luajit.
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Sat, Oct 19, 2013 at 6:56 PM, Felipe Sateler 
>> >> >> wrote:
>> >> >>> On Sat, Oct 19, 2013 at 7:20 PM, Steven Yi 
>> >> >>> wrote:
>> >> >>>> Hi Felipe,
>> >> >>>>
>> >> >>>> Thanks for commit that fix; it looks like the OSX installer I
>> >> >>>> uploaded
>> >> >>>> does *not* have the fluidsynth opcode due to that. I'm going to
>> >> >>>> rebuild that now.  The iOS and Android builds are not affected
>> >> >>>> though
>> >> >>>> as the former does not do builds for Fluidsynth and the latter has
>> >> >>>> it's own build file.
>> >> >>>
>> >> >>> But 6.01 has already been released, I thought the release branch
>> >> >>> was
>> >> >>> supposed to be closed after the release. So I guess we have
>> >> >>> diverged a
>> >> >>> bit from the git flow workflow.
>> >> >>>
>> >> >>>>
>> >> >>>> As for the lua stuff, the LUA_H_PATH is getting defined with:
>> >> >>>>
>> >> >>>> find_path(LUA_H_PATH luajit-2.0/lua.h)
>> >> >>>>
>> >> >>>> So I think the path would then get set to something like
>> >> >>>> "/usr/local/include" if "/usr/local/include/luajit-2.0/lua.h" was
>> >> >>>> found, then the luajit-2.0 would need to get appended to that.
>> >> >>>> I'm
>> >> >>>> pretty sure I wrote it that way, but if it's not working, then it
>> >> >>>> needs to be fixed.
>> >> >>>
>> >> >>> Ah yes, that is correct. Then, I have a request. As far as I can
>> >> >>> discern, luajit is supposed to be a drop-in replacement to standard
>> >> >>> lua (at least, at build time). My request would be that csound not
>> >> >>> assume that luajit is what is being used. Luajit is only available
>> >> >>> in
>> >> >>> a limited number of architectures, therefore enabling lua opcodes
>> >> >>> and
>> >> >>> interfaces in the other architectures.
>> >> >>>
>> >> >>> As far as I can tell, this can be done entirely by defining the
>> >> >>> appropriate paths in Custom.cmake instead of CMakeLists.txt (in
>> >> >>> fact,
>> >> >>> I'm doing that to use standard lua instead of luajit). I can
>> >> >>> propose a
>> >> >>> patch if this is acceptable (defaulting to luajit, of course)
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>>
>> >> >>> Saludos,
>> >> >>> Felipe Sateler
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> ------------------------------------------------------------------------------
>> >> >>> October Webinars: Code for Performance
>> >> >>> Free Intel webinars can help you accelerate application
>> >> >>> performance.
>> >> >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
>> >> >>> most from
>> >> >>> the latest Intel processors and coprocessors. See abstracts and
>> >> >>> register >
>> >> >>>
>> >> >>>
>> >> >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> >> >>> _______________________________________________
>> >> >>> Csound-devel mailing list
>> >> >>> Csound-devel@lists.sourceforge.net
>> >> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>
>> >> >>
>> >> >>
>> >> >> ------------------------------------------------------------------------------
>> >> >> October Webinars: Code for Performance
>> >> >> Free Intel webinars can help you accelerate application performance.
>> >> >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
>> >> >> most from
>> >> >> the latest Intel processors and coprocessors. See abstracts and
>> >> >> register >
>> >> >>
>> >> >>
>> >> >> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> >> >> _______________________________________________
>> >> >> Csound-devel mailing list
>> >> >> Csound-devel@lists.sourceforge.net
>> >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> >
>> >> > Oeyvind Brandtsegg
>> >> > Professor of Music Technology
>> >> > NTNU
>> >> > 7491 Trondheim
>> >> > Norway
>> >> > Cell: +47 92 203 205
>> >> >
>> >> > http://flyndresang.no/
>> >> > http://www.partikkelaudio.com/
>> >> > http://soundcloud.com/brandtsegg
>> >> > http://soundcloud.com/t-emp
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Oeyvind Brandtsegg
>> >> Professor of Music Technology
>> >> NTNU
>> >> 7491 Trondheim
>> >> Norway
>> >> Cell: +47 92 203 205
>> >>
>> >> http://flyndresang.no/
>> >> http://www.partikkelaudio.com/
>> >> http://soundcloud.com/brandtsegg
>> >> http://soundcloud.com/t-emp
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> October Webinars: Code for Performance
>> >> Free Intel webinars can help you accelerate application performance.
>> >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
>> >> most
>> >> from
>> >> the latest Intel processors and coprocessors. See abstracts and
>> >> register >
>> >>
>> >>
>> >> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > October Webinars: Code for Performance
>> > Free Intel webinars can help you accelerate application performance.
>> > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>> > from
>> > the latest Intel processors and coprocessors. See abstracts and register
>> > >
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>>
>>
>>
>> --
>>
>> Oeyvind Brandtsegg
>> Professor of Music Technology
>> NTNU
>> 7491 Trondheim
>> Norway
>> Cell: +47 92 203 205
>>
>> http://flyndresang.no/
>> http://www.partikkelaudio.com/
>> http://soundcloud.com/brandtsegg
>> http://soundcloud.com/t-emp
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>> from
>> the latest Intel processors and coprocessors. See abstracts and register >
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://flyndresang.no/
http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://soundcloud.com/t-emp

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net