Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!post02.iad!fx03.iad.POSTED!not-for-mail X-newsreader: xrn 9.03-beta-14-64bit Sender: scott@dragon.sl.home (Scott Lurndal) From: scott@slp53.sl.home (Scott Lurndal) Reply-To: slp53@pacbell.net Subject: Re: software disenchantment Newsgroups: comp.lang.c References: <8a4514a7-0185-4de5-8033-006a7bbc10f4@googlegroups.com> <0vkvD.14918$Nt6.14398@fx19.am4> <7FkvD.14919$Nt6.2825@fx19.am4> <968306fe-f05b-45cb-93a4-3081ec0d2fd0@googlegroups.com> <31e0bf8d-6138-4539-a4ae-168285339050@googlegroups.com> Lines: 22 Message-ID: X-Complaints-To: abuse@usenetserver.com NNTP-Posting-Date: Thu, 11 Oct 2018 13:16:25 UTC Organization: UsenetServer - www.usenetserver.com Date: Thu, 11 Oct 2018 13:16:25 GMT X-Received-Bytes: 2283 X-Received-Body-CRC: 3946285166 Xref: csiph.com comp.lang.c:136635 Malcolm McLean writes: >On Thursday, October 11, 2018 at 9:08:37 AM UTC+1, Wouter Verhelst wrote: >> On 10/10/18 18:42, Malcolm McLean wrote: >> > When we compile this, we must have thirdparty.c, plus any dependencies. >> >> No, you do not. You must have the library that thirdparty.c was compiled >> into; either the shared one, or the static one. >> >> (if you're using thirdparty code that your build system needs to compile >> yourself, then yes, but why would you set up your build system to behave >> that way? Use the third party code's build system for that, that's what >> it's for, and then use the libraries that it yields) >> >Depending on libraries is a bad idea. Generally it's better to integrate >third party source into your product. Then you don't have an external >dependency. You almost _never_ get that choice, unless it is open source. In our field, all the third-party code costs $$ and comes only in object form (e.g. Synopsis, Cadence, Tensilica, et alia) and often requiring a on-site license manager with a limited set of supported linux releases (generally Redhat/Centos for the tool vendors).