Dev-related docs
Code Review Code Style Contribute Deprecate Internals New protocol Release procedure Roadmap Run tests Source code Specifications Test Clutch Test curl Test case file format Tests Overview Vulnerability Disclosure Policy
Current status
Autobuilds Daily snapshots Dashboard Feature window git stats Issues (github) Pull requests (github) Release Notes
curl / Development / Source Code

Sources code control

Related:
Daily Snapshots
Build Instructions

In the curl project we use git for source code control.

Browse the Sources

Browse the source repository (on github.com)

Get the Sources

The curl sources are kept in a git repository. You can get the most recent curl source files from there at any time. git is the version control system we use for the curl project. All files in the release archive that are not generated from other files are kept there, to allow full backtracking of older versions. To use git you need a git client, get yours from git-scm.com. Windows users might fancy git for Windows.

This is mostly a feature for you who really want to have a peek in how the current development version looks like, and not if you just want to download a version to run. If you just want to download a tar or binary archive, go here.

If you want to use the git server, run:

 git clone https://github.com/curl/curl.git
Note that this will create a curl subdirectory.

If you at a later time want to get the updated set of files, just cd into this directory and run

 git pull
You can also opt to download a daily snapshot.

Compile and Build the Sources

When you checkout the sources, you get a file named GIT-INFO.md in the source root that describes how to proceed to compile and build them.

Change the Sources

If you are about to do a lot of modifications, discuss it on the curl or libcurl mailing list in advance and please consider to use git directly to do the changes and provide the necessary patches back to the project!

When you do your changes, commit them properly with git using appropriate commit messages and all. Then when you have something to show (and do show us early and often) generate either a pull-request on github or plain old patches and send to the mailing list.

AltStyle によって変換されたページ (->オリジナル) /