V
V
Vitaly Pukhov2015-02-10 17:15:45
Programming
Vitaly Pukhov, 2015-02-10 17:15:45

Why do open source projects often fail to compile?

Why are open projects often found in which there are only source codes and no compiled versions, more often this is with applications in c ++, is this some kind of way to make fun of or is there still objective reasons for this?

ps the question arose after almost 2 hours of dancing with tambourines over one source, in which 2 dozen libraries were used, which SUDDENLY the author forgot to put along with the source, they say whoever needs it will find it apparently. What was the problem for the author to compile at least for Windows, I do not understand.

Answer the question

In order to leave comments, you need to log in

5 answer(s)
S
Sergey Petrikov, 2015-02-10
@Neuroware

It is interesting for a developer to write software, but it is not interesting to assemble it himself for heaps of platforms and their versions, for this there are distribution kit maintainers, so if the maintainers of a particular distro did not bother to assemble the program you need and put it in the repository, then you will have to compile it yourself, most often for assemblies have sane documentation and the procedure is not at all complicated, in the most extreme case there are third-party repositories where, if the program is more or less known, it has already been assembled for you by the caring hands of other people.

D
Don Kaban, 2015-02-10
@donkaban

Open Source
And "at least under Windows" sounds pathetic.

A
asd111, 2015-02-10
@asd111

Open source is usually focused on Linux.
On Linux, to install all the necessary libraries, just write apt-get install libaaa-dev, libccc-dev, etc. in one line and all the necessary libraries will be installed at once.
NuGET is a package manager for visual studio. Try searching for the open source project you need in
www.nuget.org/packages?q=

R
Roman Bazalevsky, 2015-02-10
@rvbglas

Because for different OS versions it will be necessary to build different binaries / packages. Keeping the OS zoo to satisfy everyone is overkill, and not always possible even in theory.
A well-written makefile (with correct build dependencies) will suffice in most cases.

M
mayorovp, 2015-02-11
@mayorovp

Another reason: most often, the sources are stored in the version control system, and putting binaries there is a bad form.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question