What dependency?
Perhaps start at the beginning and tell us what you're trying to do, instead of seemingly falling into the middle of things? See When requesting help on theses forums for hints on what information we'd like.

For building BOINC on Windows, see http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows.

Hi Thanks for the reply, apologies, I replied to a post about the visual basic dependencies. I'm just trying to install the tools so I can play with modifying and building the client and app.

Using the example that you posted - of which I was following.
git clone http://boinc.berkeley.edu/git/boinc_depends_win_vs2013.git
This comes up with a fatal error saying its not found. Just wondering what i'm missing with this.

Thanks in advance.

I did exactly what you're trying to do earlier in the year (mid-February), and got a successful git clone from the repository address.

I've just tried to pull updates (if any) into my local copy, and got this response:

git.exe pull --progress --no-rebase -v "origin"

fatal: repository 'http://boinc.berkeley.edu/git/boinc_depends_win_vs2013.git/' not found

git did not exit cleanly (exit code 1) (1420 ms @ 02/11/2016 23:02:11)

So, I think we need to ask the development team if anything has deliberately changed, and if so, to document it.

In the meantime, I do have a complete working copy, but at over 400MB (!), it's going to be a problem distributing it.

D:\Sources_build>dir *.zip
 Volume in drive D is New Volume
 Volume Serial Number is 86EF-84C1

 Directory of D:\Sources_build

15/02/2016  16:04        46,630,368 boinc_7-6-22.zip
15/02/2016  16:05        46,640,815 boinc_7-6-23.zip
15/02/2016  16:06        45,825,505 boinc_7-6-24.zip
15/02/2016  16:07        45,825,474 boinc_7-6-25.zip
03/03/2016  09:48        45,820,523 boinc_7-6-29.zip
05/10/2016  12:43        45,859,649 boinc_7-6-33.zip
14/02/2016  22:08       421,822,353 boinc_depends_win_vs2013.zip
31/08/2016  10:31        55,212,990 boinc_head.zip
15/02/2016  16:09        55,015,564 boinc_head_2016-02-15.zip
15/02/2016  19:48             5,841 Fixed solution files.zip
              10 File(s)    808,659,082 bytes
               0 Dir(s)  964,244,217,856 bytes free

I've just checked, and the source code pull from github (which I set up with the same tools on the same day) is working properly, so I don't think the problem is at my end.

I've found an email discussion about moving the dependency files - start from

http://lists.ssl.berkeley.edu/pipermail/boinc_dev/2015-November/022113.html

and follow the thread. But it rather peters out into generalised "wouldn't it be good if...?", and I haven't yet found any conclusive evidence that anybody decided to act on it, or not. Ironic, since the final few notes (continuing into December 2015) are all about keeping the documentation up to date.

Jord, I think it would be helpful if you could prod David, Rom, Charlie and Christian when you get a moment - they seem to be the main protagonists.

(edit - but see http://boinc.berkeley.edu/gitweb/. No sign of a move - may just be a server malfunction)

I had emailed David and Rom yesterday already, but have now forwarded the question to Christian and Charlie as well.

ssh://gitolite@boinc.berkeley.edu/boinc_depends_win_vs2013.git works, all the rest does not. (That's now also changed in http://boinc.berkeley.edu/trac/wiki/SourceCodeGit#Windowsbuilddependencies).

(It would appear that Rom no longer works for BOINC, am trying to get confirmation of that)

Yes, I saw that Charlie had made that change in the Wiki. I've managed to change the origin url in my clone, but now it wants:



and doesn't let me go any further.

Rom was still making commits to the BOINC github repository as recently as last week: my understanding was that he was still employed 'in the family' by WCG, and was participating in the BOINC project as a volunteer like the rest of us, under WCG's wing.

Rom was still making commits to the BOINC github repository as recently as last week: my understanding was that he was still employed 'in the family' by WCG, and was participating in the BOINC project as a volunteer like the rest of us, under WCG's wing.

The updates under his name (to e.g. translations like this one) are automated, they don't have his input.

OK, I've emailed Charlie and David to ask about the password request, but I haven't heard back - it's a bad time of day for communicating with west coast USA.

In the meantime, I've uploaded my saved copy of the VS2013 prerequisites to OneDrive:

https://1drv.ms/f/s!AvWGSkp3v4ONh2YvHYK50QPORVfv

That's the 'export' file from a git clone: it should expand to the correct subfolder structure as shown in Windows build dependencies

Didn't know where to put this, but it's useful information and asked for by many:

David Anderson wrote:

I added support for showing the OpenCL GPU on the web page for the host.
This will require projects to upgrade their server code.
I'll deploy it on SETI@home in a couple of days.

It is useful for project's admins? Can this help the gpu app development?
Or it's simply info?

OK, I've emailed Charlie and David

Not so weird, Charlie works at off hours and is usually still up around midday UTC. David is for the moment not available, as he's dealing with something in the family.

OK, fair enough - these things happen. Is it worth asking Christian, or putting out a general request on boinc_dev - or should we just wait until normal service is resumed? Hopefully my upload will allow mambo36 to get started while we wait.

I'm mailing further with Christian and Charlie.

Charlie says to look here: http://boinc.berkeley.edu/trac/wiki/SourceCodeGit/WindowsKeygen

(Which of course can be a problem when you have something different than TortoiseGit installed. Like in my case, where I have SmartGit installed because TortoiseGit refuses to work correctly.)

Yes, but...

The context for that is Write Access to the remote Git repository - in other words, for code contributors only.

Direct write access to the main repository is currently available via the SSH protocol with public-key authentication. If you want direct write access, contact David Anderson and/or Rom Walton. They'll ask you for your public key. Here's how you can create a public/private key pair and use it after you've been granted access to the repository:

I was asking for read access only. It's perfectly fair, even under Open Source, to restrict graffiti scribblers and other vandals by requiring pre-authorisation. But that isn't what we're talking about here.

No, I can remember that under TortoiseGit, it would automatically send the puttykey along, even if you weren't writing to the directory. But, I have downloaded Puttykey.exe from Softpedia and will try if that works.

Edit: No, that doesn't work.

Hi, yes that's allowed me to compile and begin playing around with it.
Much appreciated.
Thanks.

Edit: No, that doesn't work.

Well, it would probably have worked if you had already submitted the public key so it had something to validate against. But full marks for trying.

For the record, when I set up the git/tortoise repo clone on that machine in Feb 2016, I didn't load a putty key, and I still don't need one to update my local copy of the BOINC source code from github. I didn't need one to clone the dependencies from 'http://boinc.berkeley.edu/git/boinc_depends_win_vs2013.git' either: the authentication request is new with gitolite.

Hi,

I vaguely remember that Rom said something about http access to git repos on boinc.berkeley.edu. It was along the line that it is wonky and complicated. The access over ssh is just for people with write access it seems. That's why it's working for Charlie but not everyone else. I don't remember why we didn't put the dependencies on github. Maybe it was a size restriction in those days. I'll try to find out and put the repository in a better place.

Although I have limited access to boinc.berkeley.edu I usually refrain from poking around and changing anything.

I investigated some more. Someone fiddled with the webserver config of boinc.berkeley.edu on Mar 18 2016 and redirected the /git alias to the wrong directory. I also reverted the wikipage to before Charlies changes as the ssh access is limited to those with write access only (and does not work for anonymous downloads). The normal way to download those big repositories is through http (which currently is broken). We'll have to wait for David to return and clear up why the config changed and if we can revert back.

I also investigated about moving the dependency repositories to github and it seems that with the advent of git lfs (large file support) we are able to migrate. Github has a hard limit on file size (100MB) and some of the files in the dependency repos are bigger than that. I found a viable way to migrate the existing repos to lfs repos on github and will test this soon.