I would strongly suggest calling the doubles version CsoundLib64.framework.
The doubles build does _not_ replace a float build. A program that links to
one at compile time will obviously crash if it links to the other at run
time. By giving them separate names, all hosts will use the correct version
only or fail to launch if it is not found. In the latter case, the crash
log or command line should give a clear error message about the missing
framework. If the frameworks have the same name, the crash log will give no
useful indication of what the problem is. Finally, using separate names
will allow both doubles and floats versions to coexist peacefully in the
same system. This may be necessary if the user wants to simultaneously
install two hosts that require different float sizes. (And it may even
allow a single host to offer the option of switching between floats and
doubles!)
Anthony
Victor Lazzarini wrote on 8/13/08 7:38 AM:
> The next one is to make sure the framework is correctly constructed
> by SConstruct, that everything is placed correctly. I am still wondering
> whether it should be called CsoundLib64 or just CsoundLib (I am inclined
> to the next, so that a 64 build replaces a 32 build completely and there
> are no name confusions).
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
Csound-devel mailing list
Csound-devel@...
https://lists.sourceforge.net/lists/listinfo/csound-devel
