All geek questions in one place

Location and library packages for Linux software development

Soon we will begin new work on the development of Linux; and we are developing new developments for Linux on a large scale. We have a well-defined process for processing third-party and internal libraries in Windows, but I'm interested in specific Linux options and optimizations.

Seems logical (like on Windows)

  • Not everyone downloads and compiles their own version of various libraries, such as boost / etc. but there are official builds in the repository.
  • In order to have access to the above binary binaries in the source control, so that different versions can be tied to our code, so, for example, version 1.2 of our code needs to be upgraded 1.41, and it all just works.

Should we use something like apt-get packages on a local server with official versions?

If so, are we allowed to install the libraries in their "natural" place / usr / local / include or where?

If not; we just register the libraries in our usual places of the repository, then our Makefile (s) have paths (relative or others) built into them so that it does not depend on / usr / local /?

What are other people doing in this area? Book / site pointers are also highly regarded for Linux development (applications, not the kernel).

+3
source share
2 answers

AFAIS uses regular placeholders for the libraries you use! Users will do.

, IDE , , ( .deb, ), , , , ! !: D ( )

. , - , . (, Skype, Tlen)

, . .

EDIT ( ):

, in-house?!? ?

, , :)

, , , .

dev , ( ) . , , : (

, : , linux , dev env. (, script, VC:) script VC:))

, , .

+1

, Linux, . - , . Debian equivs. . , , . , VCS.

, , . . , jhbuild, .

deb / rpm - . " " - , .

, , , . , OSS, .

, .

0

Source: https://habr.com/ru/post/1724128/

More articles:


All Articles