BTW, about that version script. Isn't that a bit old-fashioned way of doing things? Shouldn't cmake be able to scrape the current version number from the toplevel Makefile or some other convenient location and then update the other files as needed? Dominique?
On Mon, Mar 26, 2018 at 9:34 AM, Albert Graef <aggr...@gmail.com> wrote: > One more thing I just noticed: Stéphane, could you please make sure > that the new version script in the toplevel directory also edits the > version number in the toplevel Makefile? That's still needed to > generate the correct version number for the Debian package. > > Thanks, > Albert > > On Mon, Mar 26, 2018 at 9:21 AM, Albert Graef <aggr...@gmail.com> wrote: >> Hi Dominique, >> >> first, congrats for adding cmake support! That should hopefully >> improve cross-platform support. >> >> That said, in build/README.md it says that "you must have LLVM version >> 3.8 or greater installed to compile the llvm backend." >> >> Is that a typo? Because it still builds fine with LLVM 3.5 for me, on >> Linux at least. And that's a good thing, too, because Pure is still >> stuck with LLVM 3.5 and earlier, because it still requires the old >> JIT. Which means that as long as that's the case, if I want to be able >> to use Faust with Pure, I need LLVM 3.5 to be supported by Faust. (In >> fact, in MacPorts we're still using LLVM 3.4 as the LLVM legacy >> version, since it's supposedly more stable than 3.5 there.) >> >> Second, staged installs using make install DESTDIR=... are broken. >> E.g., if I do: >> >> make install DESTDIR=$PWD/buildroot >> >> Then the staged install ends up in $PWD/buildroot$PWD/buildroot/ >> instead of $PWD/buildroot/, so there seems to be a duplication of >> DESTDIR somewhere in your cmake configuration. >> >> Can you please fix this? This is a major issue for package maintainers >> like David Runge and myself. We won't be able to build any up-to-date >> packages for all the various platforms until this gets fixed. >> >> Finally, is there a quick way to verbosely show the actual compilation >> commands that get executed? I hate it when cmake hides away all the >> details, I need to be able to see the actual commands if something >> goes awry during compilation. >> >> Thanks, >> Albert >> >> -- >> Dr. Albert Gr"af >> Computer Music Research Group, JGU Mainz, Germany >> Email: aggr...@gmail.com >> WWW: https://plus.google.com/+AlbertGraef > > > > -- > Dr. Albert Gr"af > Computer Music Research Group, JGU Mainz, Germany > Email: aggr...@gmail.com > WWW: https://plus.google.com/+AlbertGraef -- Dr. Albert Gr"af Computer Music Research Group, JGU Mainz, Germany Email: aggr...@gmail.com WWW: https://plus.google.com/+AlbertGraef ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Faudiostream-devel mailing list Faudiostream-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
