[prev in list] [next in list] [prev in thread] [next in thread]
List: macports-users
Subject: Re: How to keep .c files from devel install for debugging?
From: Brandon S Allbery KF8NH <allbery () kf8nh ! com>
Date: 2010-07-30 16:28:24
Message-ID: 4C52FDA8.7060707 () kf8nh ! com
[Download RAW message or body]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 7/29/10 11:47 , William Knight wrote:
> I've successfully installed glib2-devel with macports. When I do 'port
> contents glib2-devel', it only shows the header files though. I want
> to be able to step through the glib2 source code in a debugger so how
> do I retain the .c files that were used in building the port?
I think you have a confusion here: while Linux package managers use the
"-devel" convention to mean "install the files required for develoment",
this is the default on MacPorts (which builds from source by default).
"-devel" ports mean "install the latest development snapshot".
If you want to keep the source files used to build/install a port, use "port
- -k install <portname>".
- --
brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com
system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu
electrical and computer engineering, carnegie mellon university KF8NH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxS/agACgkQIn7hlCsL25VcCwCgjmVCiZvS5bksrHHJ08mFTxJw
DyQAoM3z2iq9U1YQ9Vlfth2mnhOZLos8
=6vKS
-----END PGP SIGNATURE-----
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic