[PD-dev] "imports" section of CVS

[Hans-Christoph Steiner]

Frank Barknecht wrote:
> Hallo,
> Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
> 
> 
>>After the long winded discussion about whether to import sources in  
>>the Pd CVS, I want to propose a comprimise:  making an "imports"  
>>section of the CVS.  Then those who don't want to deal with imported  
>>code can just ignore the "imports" section.
>>
>>But be forewarned Pd-extended on Mac OS X and Windows would then rely  
>>on code from the "imports" section, unless you manually redirect things.
>>
>>Any objections?
> 
> 
> I don't have real objections, but could you elaborate a bit on how you
> intend to rely on the imports sections with Pd-extended and how to
> redirect things? I would prefer if not-having-to-redirect would be the
> default, and if the imports section would only be used, if explicitly
> specified. Or something like that.

A good example would be the DSSI stuff.  The fluidsynth plugin code 
would be in "imports" and the Windows and Mac OS X parts of the Makefile 
would include the source code in imports.  The GNU/Linux part would look 
in the standard system locations for that stuff.

.hc