Am Sonntag, 16. September 2018 11:43 CEST, Marcus Weseloh <mar...@weseloh.cc> schrieb: > Hi, > > Am So., 16. Sep. 2018 um 11:10 Uhr schrieb Carlo Bramini < > carlo.bra...@libero.it>: > > > I was wondering what you think about using an external tool for compiling > > the const tables, like Python.
+1 > > In my opinion, that would be a simple, easy and straight forward solution. > And I would go one step further: make the generated files part of the > source distribution. That way you don't need Python to compile Fluidsynth. That would be a 'bad idea'. Golden rule of development: never VC generated files. > Only if and when those tables need to be regenerated is Python a > requirement. And judging from the past years of development, the need to > change the tables won't come up very often. > > Just think of the const tables as "configuration" and the Python script as > a tool to write that configuration. Similar to autotools configure scripts. > They get checked in to VCS all the time. ??? That's not how the autotool chain is supposed to work, they clearly document that the original input should be vesion controlled, not the results of running automake/autoconf et al. The generated files should be included in _release tarballs_, but that's something completely different. Cheers, RalfD > All the best, > > Marcus _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
