I don't think that is a sane design, because the platform-specific code is largely interrelated to the common code. For example, all platforms build plugins, but use a slightly different method. This means you can't abstract the platform-dependent from the platform-independent. On Wednesday 26 March 2008 22:53:03 DavidW wrote: > I agree w. refactoring. Similar to my desire to refactor the > BuildingCsound manual page. > (Would those I sent my draft to who haven't yet, please have a look at > my suggestions and comment as necessary - there's currently nothing on > how to do an install for OSX for example) > I think a two-tiered structure is best: > Tier 1: the SConstruct file (in parallel with SConstruct2 current > SConstruct becomes redundant) > > All those things which are immutable across all platforms > + test for Platform and then include a Tier 2 file > Tier 2: > Everything platform specific. If in doubt, put stuff here. > It should include the following sections: > - clean to be otionally used b4 build > - build > - install > > David > > On 27/03/2008, at 11:17 AM, Felipe Sateler wrote: > > On Wednesday 26 March 2008 20:58:17 Steven Yi wrote: > >> Hi Felipe, > >> > >> I think this would be very useful work, but also have a hard time > >> visualizing at the moment. I think it might be useful if you were > >> commit your work early but under a different name, SConstruct2 > >> perhaps, so that we could see in code what you are working on and > >> also > >> to see how this would impact development going forward. Plus we > >> could > >> switch between the current build file and the SConstruct2 file using > >> -f, which would be good for testing. > > > > Good idea. This file would of course start as a copy of SConstruct > > (starting > > from scratch would require much more work, and probably involve > > rediscovering > > problems with different platforms). > > > >> Are you planning SConscript files for each library then? (If so, I > >> think that would be a very good thing.) > > > > No. It's one SConscript for each folder. This way all related stuff is > > together in a SConscript (for example, all opcodes, because they > > build more > > or less the same way). > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplac >e _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel -- Felipe Sateler