Hi, Karl Rupp <r...@iue.tuwien.ac.at> writes: >> Right -- so I've assumed that you have a working python and git >> installation; it seemed fair to assume that, if you want to install from >> source and want to be using Python, you'd have both set up. > > I don't think we should assume that something is setup in whichever way, > but instead clearly outline how users can bring their machine into a > usable state. Now, considering that both Python and Git by default do > *not* put their installation folders into path, we should at least > mention that they might have to use the full path.
Sure -- but if you're using Python, then you should probably know how to invoke it. I don't put Python in the PATH on Windows, because I have multiple versions installed, and so I don't want to suggest that's the best way for users. But I can put a note in saying something about this. >> Also, I >> don't think I should be providing installation guides for components >> other than PyViennaCL! In particular, people's installations of Windows >> software vary widely, and so general instructions will either be complex >> or vague. > > Of course not. The installation of other packages is not our business > (which, on the other hand, is a reason not to have too many required > dependencies), but we need to be explicit about how we expect these > packages to be set up. If we provide installation guidelines assuming > that 'python' and 'git' are in PATH, we need to document this somehow > (even if it's just a single sentence) :-) All I require is that, if you want to use Python or Git, then you should know how to invoke them! >> Ultimately, either the user should install a prebuilt binary, or will >> use `pip install pyviennacl`; any other case suggests more advanced >> usage. >> >> pip comes with setuptools, so that dependency is automatically satisfied >> there; but I will mention it for completeness! > > Sure, once these easier methods are in place, they will be the default. > For the time being, let's make sure as many users as possible can also > manage this more involved procedure. :-) Quite :) > Short reply here: Compilation now succeeds :-) The many compilation > warnings are a pain, though. Is there anything we can do to reduce them? > Or are they all from Boost.NumPy? > > Also, --no-use-opencl doesn't seem to work yet, I get an error > (unrecognized option). It's curious -- I don't get that error on Linux or Windows. If I just give "-no-use-opencl" as Andreas suggests, then I get "configure.py: error: no such option: -n". >>>> I've also heard that building is successful on Mac OS X, with both clang >>>> and Intel compilers. But apparently running the blas3_prod.py test >>>> caused artefacts on and freezing of the user's screen.. but I suspect >>>> that's a problem with their OpenCL implementation not PyViennaCL! >>> >>> Our test machine running Mac OS X 10.6 has a pretty buggy OpenCL SDK, so >>> it may be the same thing there. On the other hand, it's better to >>> produce slow code rather than crashing a user's machine. Do you happen >>> to know which version of Mac OS this was? >> >> Hmm, no. But I shall find out. If you get a chance to test on your >> OS X machine, the results would be interesting to know. > > I'll try it on the OS X machine tomorrow. Excellent. I also have a Mac OS X user who is comparing building and performance on Mac OS X across Intel and clang compilers. >> But I >> appreciate that you probably don't want to spend all your time testing >> PyViennaCL! :-) > > There are certainly things which are more fun than testing, but since > this is something every prospective user needs to go through, this needs > to be taken seriously. You are of course quite right! Cheers, Toby ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
