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 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Installing .ads, best practices ? Date: Mon, 30 Apr 2018 17:03:47 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <74e6a67b-092a-4059-82e9-b6f6838cf709@googlegroups.com> NNTP-Posting-Host: kQkuQcRDy1QFvWpyB1foYw.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 X-Notice: Filtered by postfilter v. 0.8.3 Content-Language: en-US Xref: reader02.eternal-september.org comp.lang.ada:51838 Date: 2018-04-30T17:03:47+02:00 List-Id: On 2018-04-30 15:17, patrick@spellingbeewinnars.org wrote: > If we create our own C libraries on Linux(or similar posix) the best practice is to put the header in /usr/local/lib and not in /usr/lib where the original libraries installed by the package manager or at install time are located. > > On my system, most of the .ads spec files are located in: > /usr/lib/gcc/x86_64-linux-gnu/4.6/rts-native/adainclude/ > > It doesn't seem to like a good idea to install my own spec files there for system wide use. > > Would /usr/local/include be better? Do you use something like this? If so, do you have an environmental variable in your.bashrc so that gnatmake finds it without passing an argument ? No. As Niklas suggested use the corresponding Ada policy of the target and pack your Ada library using the corresponding packaging tool, e.g. dpkg under Debian or rpm under Fedora. If you respect the policy, no additional user settings are required to use your library with either gnatmake or gprbuild. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de