Opened 8 years ago
Closed 8 years ago
#51661 closed enhancement (invalid)
Use of PortGroup python 1.0
| Reported by: | emaros | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | gds |
Description
To be able to get the python configurations for the python variant that I am interested in, I have included at the top of my Portfile the PortGroup python 1.0 line.
As this sets the environment for building python modules, I have had to redefine many of the build targets such that things are appropriate from autoconf/automake.
The variable I want is: python.pkgd so I know where to install my extensions.
Is there a way to only set the python extended variables? Is there another PortGroup that I could include afterwards to reset use_configure, build.cmd, etc. back to the autoconf/automake defaults?
Change History (1)
comment:1 Changed 8 years ago by mf2k (Frank Schima)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Trac is not for tech support. Follow-up on the Macports Developers mailing list instead.