Art,
Setting buildRelease=1 to one has no affect on the build. With that set when
I look at the build logs it still reports building the new Parser. We use to
set buildRelease=0 in all previous releases. Why they would swap this around
is beyond me! Can you forward details on to them because I can
Peter,
My feelings exactly.
As regards Csound, most of our listservs are users; developers are relatively
few and tend to communicate largely among themselves.
Though I also am a member of csound-dev, I was unaware of the old/new parser
status. I knew the new parser was (and has been long) "un
Art,
It seems I did get the mail but some how missed it.
Sigh! How so typical of CSound to make the new parser the default even
though they themselves don't recommend it, nor do they really even document
it anywhere! GRR!
I'll have a look at the build and see what else it will affect, csound isn
Peter -
Did you ever receive the messages collated below? (They largely occurred on
the csound-dev list.)
Are the questions you mentioned (ones that were never answered) the ones
addressed here?
If not, please send them again. To my knowledge, the simple "Csound
solution" is running scons
Peter:
I presume you received the messages immediately listed below, regarding a
solution to the old/new Csound parser issue ("build csound with the scons
option buildRelease=1").
If you sent questions either to this group, or the Csound-developers list,
I'm sorry; I didn't receive them. Ar
5 matches
Mail list logo
