From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail
From: Victor Porton <porton@narod.ru>
Newsgroups: comp.lang.ada
Subject: Re: How to deal with Ada libraries?
Date: Sun, 29 Oct 2017 23:26:38 +0200
Organization: Aioe.org NNTP Server
Message-ID: <ot5h2j$1nlu$1@gioia.aioe.org>
References: <ot55ms$1439$1@gioia.aioe.org> <ot57v5$17td$1@gioia.aioe.org>
NNTP-Posting-Host: p7dn7ovnlfKNrsGJsG/4aA.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: abuse@aioe.org
User-Agent: KNode/4.14.10
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news.eternal-september.org comp.lang.ada:48644
Date: 2017-10-29T23:26:38+02:00
List-Id: <comp.lang.ada>

Dmitry A. Kazakov wrote:

> On 2017-10-29 19:12, Victor Porton wrote:
> 
>> I am to choose of three variants:
>> 
>> 1. create a Makefile to build the Simple Components library and link to
>> this library;
> 
> Why not gprbuild?

I call gprbuild from my Makefiles.

>> 2. don't create a library but just include Dmitry's files as a part of my
>> source;
> 
> If you use project files, and you should, there is no difference unless
> you wanted a dynamically-linked library. Using sources is more
> comfortable with GPS as you could easily browse the implementations and
> fix them if necessary.
> 
>> 3. just install the Debian package built by Dmitry.
>> 
>> The "3" variant has the deficiency that because the Dmitry's package is
>> not in Debian, this may cause difficulty in the future to make my own
>> Debian package of my software.
> 
> Again no difference for a static library.
> 
> Note that there might be dependencies on third-party packages. E.g. if
> you wanted to use secure HTTP, you would depend on GNUTLS (for AWS it
> would be OpenSSL).
> 
> For the case of having dynamic libraries and your own Debian package,
> you would probably set up your own repository. Then you would just put
> there any packages you needed which are not in the standard repository.
> So I don't see a problem here.
> 
> P.S. Any choice is easily reversible if you use project files. I would
> strongly recommend to ditch makefile, automake et al, sooner, the better.

Yes, I do use automake and autoconf.

-- 
Victor Porton - http://portonvictor.org