Repository navigation
Conversation
git clone from repository is very "expensive" in terms of time and traffic produced. In fact only very small core part of the civetweb code is used in the ROOT. Therefore just create minimal tarball ourself and download it
Test Results 2 files 2 suites 4h 4m 14s ⏱️ Results for commit d7d7d18. ♻️ This comment has been updated with latest results. |
Put in civetweb-588860e3.tar.gz code from 588860e3 commit and apply our patches to it. Then build with same commands as with git checkout
linev
changed the title
588860e3 commit
| # URL_HASH SHA256=${ROOT_CIVETWEB_HASH} | ||
|
|
||
| # ------- here is extract of 588860e3 commit ------ | ||
| URL https://jsroot.gsi.de/civetweb-588860e3.tar.gz |
There was a problem hiding this comment.
| URL https://jsroot.gsi.de/civetweb-588860e3.tar.gz | |
| URL https://root.cern/download/civetweb-588860e3.tar.gz | |
| https://jsroot.gsi.de/civetweb-588860e3.tar.gz |
With #23963, I'm trying to ensure that every tarball has two mirrors: one at CERN (usually LCG), tried first, and then an "external" (usually GitHub).
To preserve this also for civetweb, maybe we can put the same civetweb-588860e3.tar.gz also on root.cern? If the tarball is final, then @dpiparo could upload it there
There was a problem hiding this comment.
@guitargeek
Lets wait until all builds are green.
I also see some warnings during build (on my Linux I normally using external civetweb) and want to fix them
|
Need to restart for clean build |
d7d7d18 to
afff951
Compare
git clone from repository is very "expensive" in terms of time and produced traffic.
In fact only very small core part of the civetweb code is used in the ROOT.
Therefore just create minimal tarball ourself, download it and apply same patches as for git repository
Trying also fix cmake warning when provide list of libs as argument - trying to use
LIST_SEPARATOR "|"argument