On 06/17/2014 08:58 PM, Michal Babej wrote: > Clang+LLVM has windows binaries... only they're unusable with > pocl. The problem is, pocl requires a bunch of -libclang* and -libLLVM* > libraries; the windows installer doesn't ship any of these, IIRC.
Did you contact the Windows installer maintainer to check if they could be included? > Now, seeing this, i figured i'd try doing Visual Studio build, which > was actually quite easy to do, and it produced a full clang/llvm > installation. (didn't check if it worked ;) The next thing one needs is > to build hwloc (autotools project) in Visual Studio, and if i > understand correctly, a replacement for libltdl which would work in > windows. Too bad if hwloc requires autotools. Anyways, it's optional -- without it one just gets less information in the platform queries. If it is disabled first in Windows we can later figure out an alternative way to query the info in Windows. libltdl is used to wrap the dlopen() call that loads the work-group function (a dynamic library/plugin) in the basic/pthread drivers to actually run the kernel in the launcher process. This is the only place where it's used, IIRC. Here's how to load dynamic libraries in Windows: http://en.wikipedia.org/wiki/Dynamic_loading#Windows > Feeling that would be a bit too much work, i tried to do a mingw build > of clang/llvm, hoping hwloc+ltdl would be easier in mingw. The first > warning sign was that clang/llvm has hardcoded paths for the standard > library headers (!), and those paths only work with certain mingw gcc > versions (4.7.0 being the latest..). Anyway, after a few fixes of the > build system, i got a working clang+llvm via mingw, which linked to gcc > stdlib 4.7.0. To get hwloc working, i needed a bunch of other libraries > for an outdated mingw... and i must have introduced a bit of chaos into > my mingw libraries, because somewhere down the road the "make" command > started to segfault :) OK mingw/cygwin is a good start, but of course a "native" Visual Studio build is the ultimate target. The basic driver could be modified first to work in Windows as it does not use any threading libraries, then a separate driver could be done with Windows-specific optimizations, threading, etc. The biggest problem now seems to be the lack of libraries in the LLVM Windows installer, right? > Sure, but it would be nice to have at least 1 more person that has some > cmake experience. Mikael mentioned he is interested in cmake for Mac build, I think he even started to work on it. He mentioned this to me a month ago in IWOCL. -- Pekka ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
