From: Sean Mitchell <SMitchell@phoenix-interactive.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] STLport ebuild
Date: Fri Jul 13 12:03:02 2001 [thread overview]
Message-ID: <1DCB85BD45DED211B12D009027279E4F47676E@murcury> (raw)
Hi All....
Emboldened by my success with doxygen, I have ventured on to the next thing
I need in Gentoo, which is STLport.
Like doxygen, STLport is a bit of an oddball. Basically it builds a couple
library files in the build tree then leaves it to you to put the libraries
and headers somewhere.
I've set up the libraries to go in /usr/lib and the includes to go in
/usr/include/stlport. Any reason they shouldn't go there?
I just create the directories I need in ${D} and then populate them with a
couple cp -r commands. Is this okay or is there a Better Way?
Here's the ebuild:
------------------SNIP------------------
S=${WORKDIR}/${P}
DESCRIPTION="STLport is a multiplatform ANSI C++ Standard Library
implementation."
SRC_URI="http://www.stlport.org/archive/${P}.tar.gz"
HOMEPAGE="http://www.stlport.org"
src_compile()
{
cd ${S}/src
try make -f gcc.mak clean all
}
src_install()
{
mkdir -p ${D}/usr/include/stlport
mkdir -p ${D}/usr/lib
cp -r ${S}/stlport/* ${D}/usr/include/stlport
cp -r ${S}/lib/* ${D}/usr/lib
dodoc README INSTALL TODO ChangeLog
}
------------------SNIP------------------
If anyone has any comments I'll update this otherwise I'll test it a bit
more and then post it to the list.
Cheers,
Sean
------------------------------------------------------------------------
Sean Mitchell Software Engineer
smitchell@phoenix-interactive.com Phoenix Interactive Design Inc
tel. 519-679-2913 x237 4th Floor, 137 Dundas St
fax. 519 679 6773 London, ON, Canada N6A 1E9
ICQ# 104246806
------------------------------------------------------------------------
next reply other threads:[~2001-07-13 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 12:03 Sean Mitchell [this message]
2001-07-13 13:26 ` [gentoo-dev] STLport ebuild john.allen
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 13:59 Sean Mitchell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1DCB85BD45DED211B12D009027279E4F47676E@murcury \
--to=smitchell@phoenix-interactive.com \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox