I have an OSX installer ready now; I have done some testing
and
it seems to work. As far as OSX installation goes, I say we
can go
for a release now.

One question: when preparing the binaries for release, apart
from
building with noDebug=1 is there anything else that it might
be
good to do?

Victor


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks for this work Victor!

Which systems are you able to test on?  I can test on a PowerMac Dual G4
running 10.2.8 and a PowerMac G3 running 10.1.5 whenever you post a test
binary.

I really hope that the standard release package for OS X will run on 10.2
and higher.  10.1 would be nice but I fear that there are some possible
technical hurdles for that (like CoreAudio, I believe).  It should still be
conceiveable though for a 10.1 user to compile a basic non-realtime Csound
though, I hope.

I also assume that you will be wrapping the framework, etc. in a .pkg file
and then making a disk image of that (hopefully with a ReadMe containing
installation notes), right?

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://akozar.spymac.com/


Victor Lazzarini wrote on 12/14/05 2:18 PM:

> One question: when preparing the binaries for release, apart
> from
> building with noDebug=1 is there anything else that it might
> be
> good to do?



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Yep. What I have is a Csound5.mpkg, which itself holds three
packages, CsoundLib framework, Csound 5 apps, Support Libs.

Installation should be just a matter of clicking on the installer file.
The only thing I am not able to get around is the root authorisation,
since things are installed in root directories. However, as far as I
can see this is required by a great number of packages, so users
should not find it unusual.

I decided I will make two releases: one for G4s and one for G5s, to
take advantage of gcc optmisations that seem to make a difference.
It will be nice to try it on 10.2. If it doesn't work, it might still be
possible to build it on your machine and prepare a special release for it.

Victor

At 06:32 15/12/2005, you wrote:
>Thanks for this work Victor!
>
>Which systems are you able to test on?  I can test on a PowerMac Dual G4
>running 10.2.8 and a PowerMac G3 running 10.1.5 whenever you post a test
>binary.
>
>I really hope that the standard release package for OS X will run on 10.2
>and higher.  10.1 would be nice but I fear that there are some possible
>technical hurdles for that (like CoreAudio, I believe).  It should still be
>conceiveable though for a 10.1 user to compile a basic non-realtime Csound
>though, I hope.
>
>I also assume that you will be wrapping the framework, etc. in a .pkg file
>and then making a disk image of that (hopefully with a ReadMe containing
>installation notes), right?
>
>Anthony Kozar
>anthonykozar AT sbcglobal DOT net
>http://akozar.spymac.com/
>
>
>Victor Lazzarini wrote on 12/14/05 2:18 PM:
>
> > One question: when preparing the binaries for release, apart
> > from
> > building with noDebug=1 is there anything else that it might
> > be
> > good to do?
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

What about the status of PortAudio for realtime on Mac OS 10.1.x ?

Certainly it should be possible to run a non-realtime version I hope !!?

We need to get all those colored iMacs running Csound5 ! :)


-David

On Dec 15, 2005, at 1:32 AM, Anthony Kozar wrote:

> 10.1 would be nice but I fear that there are some possible
> technical hurdles for that (like CoreAudio, I believe).  It should 
> still be
> conceiveable though for a 10.1 user to compile a basic non-realtime 
> Csound
> though, I hope.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Victor Lazzarini wrote on 12/15/05 4:36 AM:

> Yep. What I have is a Csound5.mpkg, which itself holds three
> packages, CsoundLib framework, Csound 5 apps, Support Libs.

Thanks Victor -- this sounds great.

> Installation should be just a matter of clicking on the installer file.

Is there any post-install configuration that the user needs to do?  If so,
that info should go in a read me along with a pointer to the sourceforge
site, csounds.com, the mailing lists, and the manual, as well as a statement
that Csound is LGPL.  (Packages may be redistributed by other sites, etc.).

Also, experience has taught me that with OS X, many newbies to Csound will
not have a clue about the commandline.  If the installer does not put a
double-clickable application in the Applications folder then they will be
confused.  A brief explanation of what is being installed and where to get
help on using it would, I think, be very helpful in the ReadMe for the disk
image.

If you want to look at what I have done in the past with my OS 9 and OS X
releases, just download them from the csoundmac package on Sourceforge.
Feel free to borrow any of the text from my ReadMes if it is useful to you.

Of course, this is just the way that I would package things if I were doing
it.  Since I am not volunteering, I will be quiet now ...


> I decided I will make two releases: one for G4s and one for G5s, to
> take advantage of gcc optmisations that seem to make a difference.
> It will be nice to try it on 10.2. If it doesn't work, it might still be
> possible to build it on your machine and prepare a special release for it.

Just a note about machines:  there are many G3-based Macs that can still run
up to 10.4.  Will the G4 optimizations exclude them by using G4-specific
instructions or does it just optimize performance for a G4?

Thanks again!

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://akozar.spymac.com/



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'm not really sure about G3s. I can probably do three packages then,
one without optmisation, just to be on the safe side.

There is no post-install configuration; the system should be able to be
run out of the box; the user can optionally set the SFDIR etc, but that
does not prevent csound from working.

I was thinking of the 'double-clickable app', and that's why I asked about
the MacCsound sources. Since Matt should do a csound5 version soon,
I'm wondering whether I should do anything. There is the CSDPlayer,
that plays CSD files only. I suppose it would be easy to knock a FLTK
player that is double-clickable. Do you think it's necessary?

I'm open to suggestions.

In relation to licenses and notes, the license is shown to the user on
installation. I am going to add a Welcome message and a Readme
as well. Have to think about the text though.

Victor


At 18:23 15/12/2005, you wrote:
>Victor Lazzarini wrote on 12/15/05 4:36 AM:
>
> > Yep. What I have is a Csound5.mpkg, which itself holds three
> > packages, CsoundLib framework, Csound 5 apps, Support Libs.
>
>Thanks Victor -- this sounds great.
>
> > Installation should be just a matter of clicking on the installer file.
>
>Is there any post-install configuration that the user needs to do?  If so,
>that info should go in a read me along with a pointer to the sourceforge
>site, csounds.com, the mailing lists, and the manual, as well as a statement
>that Csound is LGPL.  (Packages may be redistributed by other sites, etc.).
>
>Also, experience has taught me that with OS X, many newbies to Csound will
>not have a clue about the commandline.  If the installer does not put a
>double-clickable application in the Applications folder then they will be
>confused.  A brief explanation of what is being installed and where to get
>help on using it would, I think, be very helpful in the ReadMe for the disk
>image.
>
>If you want to look at what I have done in the past with my OS 9 and OS X
>releases, just download them from the csoundmac package on Sourceforge.
>Feel free to borrow any of the text from my ReadMes if it is useful to you.
>
>Of course, this is just the way that I would package things if I were doing
>it.  Since I am not volunteering, I will be quiet now ...
>
>
> > I decided I will make two releases: one for G4s and one for G5s, to
> > take advantage of gcc optmisations that seem to make a difference.
> > It will be nice to try it on 10.2. If it doesn't work, it might still be
> > possible to build it on your machine and prepare a special release for it.
>
>Just a note about machines:  there are many G3-based Macs that can still run
>up to 10.4.  Will the G4 optimizations exclude them by using G4-specific
>instructions or does it just optimize performance for a G4?
>
>Thanks again!
>
>Anthony Kozar
>anthonykozar AT sbcglobal DOT net
>http://akozar.spymac.com/
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Victor Lazzarini wrote on 12/16/05 4:14 AM:

> I'm not really sure about G3s. I can probably do three packages then,
> one without optmisation, just to be on the safe side.

Well, I was just asking about G3s to see if you knew anymore than I do.  My
understanding is that the G4 chip has the same instruction set except for
the Altivec extensions.  If I am correct, then I think your G4-optimised
package will run on a G3 (just not optimally).  But I certainly could be
wrong :)

Why don't you just make two packages for now and we'll try to get some
feedback as to whether they work for everyone.

> I was thinking of the 'double-clickable app', and that's why I asked about
> the MacCsound sources. Since Matt should do a csound5 version soon,
> I'm wondering whether I should do anything. There is the CSDPlayer,
> that plays CSD files only. I suppose it would be easy to knock a FLTK
> player that is double-clickable. Do you think it's necessary?

Sorry.  I did not mean to suggest that you create a GUI.  I think that
MacCsound will be sufficient and most people will probably use it anyways.
My point was simply that in the absence of a double-clickable app, that some
explanation about what is being installed (and where it is going) might be
desirable.  Otherwise, to some users, it will appear as if the installer has
done "nothing".

Thanks again for all of your efforts :)

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://akozar.spymac.com/



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net