59ac79c4dc
The introduction of stages in gitlab-ci had quite a unfortune side effect that is described in the documentation [1]. The whole artifacts path (in our case obj/) is passed from one stage to another by default, which is causing very odd behavior as the previous results are only partially overwritten by the new cmake command and can even lead to execution of tests that are not supposed to run in particular job. [1] https://docs.gitlab.com/ee/ci/yaml/#dependencies Signed-off-by: Jakub Jelen <jjelen@redhat.com> Reviewed-by: Anderson Toshiyuki Sasaki <ansasaki@redhat.com> |
||
|---|---|---|
| cmake | ||
| doc | ||
| examples | ||
| include | ||
| src | ||
| tests | ||
| .arcconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| AUTHORS | ||
| BSD | ||
| ChangeLog | ||
| CMakeLists.txt | ||
| CompilerChecks.cmake | ||
| config.h.cmake | ||
| ConfigureChecks.cmake | ||
| COPYING | ||
| CPackConfig.cmake | ||
| CTestConfig.cmake | ||
| DefineOptions.cmake | ||
| INSTALL | ||
| libssh.pc.cmake | ||
| README | ||
| README.CodingStyle | ||
| README.mbedtls | ||
| README.md | ||
| SubmittingPatches | ||
_ _ _ _
(_) (_) (_) (_)
(_) _ (_) _ _ _ _ _ (_) _
(_) (_) (_)(_) _ (_)(_) (_)(_) (_)(_) _
(_) (_) (_) (_) _ (_) _ (_) (_) (_)
(_) (_) (_)(_)(_) (_)(_) (_)(_) (_) (_).org
The SSH library
Why?
Why not ? :) I've began to work on my own implementation of the ssh protocol because i didn't like the currently public ones. Not any allowed you to import and use the functions as a powerful library, and so i worked on a library-based SSH implementation which was non-existing in the free and open source software world.
How/Who?
If you downloaded this file, you must know what it is : a library for accessing ssh client services through C libraries calls in a simple manner. Everybody can use this software under the terms of the LGPL - see the COPYING file
If you ask yourself how to compile libssh, please read INSTALL before anything.
Where ?
Contributing
Please read the file 'SubmittingPatches' next to this README file. It explains our copyright policy and how you should send patches for upstream inclusion.
Have fun and happy libssh hacking!
The libssh Team