cmake integration is in progress on master-dev branch, but not fully finished yet. Stay tune !
Stéphane > Le 3 févr. 2018 à 13:31, stijn . <stijn.v.b...@gmail.com> a écrit : > > Hello Stéphane, > > How are you? I was wondering what the status is with the cmake build system, > in order to get my windows build working as well. > > All the best, > > Stijn > > 2017-12-14 16:05 GMT+01:00 Stéphane Letz <l...@grame.fr>: > We are currently in the process of moving to a « cmake » build system which > will simplify all that. This is currently in work on master-dev branch, but > not ready yet. > > I would advice to wait a bit more.. > > Stéphane > > > > Le 14 déc. 2017 à 15:49, stijn . <stijn.v.b...@gmail.com> a écrit : > > > > Hello all, > > > > thanks a lot for all the directions so far. I now have the LLVM chain > > working on OSX which is great. > > > > However on windows I experience some problems building libfaust. When I > > open the VS solution in VS2015 it gives me a lot of errormessages that > > unistd.h cannot be found. However this is a unix include if I am not > > mistaken? > > > > Does anybody have an idea how to solve this problem? > > > > Thanks a lot! > > > > 2017-12-01 22:40 GMT+01:00 Albert Graef <aggr...@gmail.com>: > > On Fri, Dec 1, 2017 at 8:58 PM, Stéphane Letz <l...@grame.fr> wrote: > > My recent tests on OS X with clang/LLVM 4.0 and 5.0 shows really less > > difference that previously, or you have winners and losers on either side, > > depending of the DSP and the Faust compilations parameters. > > > > Yes, that was my experience as well, and it's good to hear that the bitcode > > backend more closely matches clang now. > > > > libfaust is « obviously » supposed to correctly handle memory. We use a > > global memory allocator for all dynamic data structures that deallocate all > > of them when the DSP factory has been produced. I fixed some remaining > > memory leak some weeks/month ago. It should be OK now, and if not, then > > *please* send bug reports.. ((-;. > > > > That's good to know, thanks for setting me straight there! > > > > Nevertheless, FWIW I just wanted to pointed out that there *are* worthy > > alternatives to going the LLVM route. As always, YMMV. And don't get me > > wrong, I *love* LLVM, for us compiler writers it's the best thing since > > sliced bread, and then some. ;-) > > > > Albert > > > > -- > > Dr. Albert Gr"af > > Computer Music Research Group, JGU Mainz, Germany > > Email: aggr...@gmail.com > > WWW: https://plus.google.com/+AlbertGraef > > > > > > > > -- > > Stijn van Beek > > e-mail: stijn.v.b...@gmail.com > > tel.: ++31-6-22316389 > > > > > -- > Stijn van Beek > e-mail: stijn.v.b...@gmail.com > tel.: ++31-6-22316389 ------------------------------------------------------------------------------ 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
