Yes, a quick intro guide to this would be really valuable. It might be best if someone who has recently done this write an initial draft to be edited by those who live and breathe GitHub (I'll do it). I find I have a pretty hard time knowing what will and won't be confusing to people who aren't familiar with git and GitHub these days.
On Mon, Apr 21, 2014 at 10:07 AM, Tobias Knopp <[email protected]>wrote: > See https://github.com/timholy/HDF5.jl/issues/85#issuecomment-40868410for a > recent writeup of Tim. > > Maybe there should also be a disclaimer that each package is its own open > source project and that issues with packages should ideally be reported on > the projects issue tracker. > > Am Montag, 21. April 2014 14:49:04 UTC+2 schrieb Dahua Lin: > >> Whereas it might seem straightforward for people in the open source >> circle to use Github to file issues or make pull requests, general users >> may find them unfamiliar or even daunting tasks. >> >> It would be useful to provide relevant instructions somewhere so that >> people (especially those who are not familiar with Github) understand how >> the ecosystem works, and know what to do that they have issues with a >> package, find a bug, or want to contribute their patches. >> >> Best, >> Dahua >> >> >> On Sunday, April 20, 2014 9:04:05 AM UTC-5, Stefan Karpinski wrote: >>> >>> Spamming the repo isn't a concern – it's much easier to try someone >>> else's changes out if you just make a pull request. Then it's just a matter >>> of checking out their branch (which can be done completely automatically) >>> and trying it out. >>> >>> >>> On Sat, Apr 19, 2014 at 8:43 PM, Laszlo Hars <[email protected]> wrote: >>> >>>> It looks like the very simple change I noted yesterday makes the CUDA >>>> package work under Windows. Before spamming the GIT depository, could >>>> somebody verify it the fix really works? Or if it can be written in a >>>> better way? >>>> >>>> Add the following two lines to CUDA.jl, just above the include(...) >>>> lines >>>> ~~~ >>>> const CUDA_LIB = @windows? "nvcuda.dll" : "libcuda" >>>> dlopen(CUDA_LIB) # loads library, throws an error if not found >>>> ~~~ >>>> In the base.jl file replace "libcuda" with CUDA_LIB. (Line 9) >>>> >>>> Another useful tool could be "SendTo" in the Windows explorer for .cu >>>> files, to be compiled to .ptx files with a couple mouse clicks. >>>> Simply right click on a .cu file, and select Send to > in the context >>>> menu, and !nvcc in the new popup window. To make it work do the following. >>>> >>>> 1. Create a batch file, named !nvcc.bat, anywhere you like in a local >>>> disk. It has to contain the following lines: >>>> ~~~ >>>> @echo off >>>> REM Go to the drive of parameter1; cd to its path; run nvcc with the >>>> filename >>>> %~d1 >>>> cd "%~p1" >>>> "%CUDA_PATH%\bin\nvcc.exe" -ptx %~nx1 >>>> pause >>>> ~~~ >>>> >>>> 2. In Windows explorer navigate to %APPDATA%\Microsoft\Windows\SendTo\ >>>> >>>> 3. Create a link to the !nvcc.bat file just created. (Right-drag to >>>> here, select: Create shortcuts here) >>>> >>>> Now a new entry appears in the SendTo menu, !nvcc. If a .cu file is >>>> sent to there, it will be compiled to .ptx in the same directory, ready to >>>> be used by the CUDA package. >>>> >>> >>>
