In CMake, to find an exact required specific version, you can use EXACT
and REQUIRED, e.g:
find_package(python 3.4.3 EXACT REQUIRED)
That said, the provided FindPython sucks, in that if multiple versions
of Python are installed it will generally find part in the
CMAKE_INSTALL_PREFIX and
Dear Ryan,
I wonder if anyone could help me with this.
I can build this port fine on my machines but I get errors on the buildbot.
The buildbot fails to find the glib2 include path and the configuration fails.
I would appreciate any comments.
Dependencies on glib2 should be written as
On 2015-6-29 23:26 , Takeshi Enomoto wrote:
Dear Ryan,
I wonder if anyone could help me with this.
I can build this port fine on my machines but I get errors on the buildbot.
The buildbot fails to find the glib2 include path and the configuration fails.
I would appreciate any comments.
On 29.06.2015 03:26 PM, Takeshi Enomoto wrote:
I wonder if anyone could help me with this.
I can build this port fine on my machines but I get errors on the buildbot.
The buildbot fails to find the glib2 include path and the configuration fails.
Please try building the port on your machine
On 6/29/15 12:22 PM, ele...@macports.org wrote:
[138119] users/elelay/ports/devel/gtk-osx-application/Portfile
Revision
138119 https://trac.macports.org/changeset/138119
Author
ele...@macports.org
Date
2015-06-29 12:22:04 -0700 (Mon, 29 Jun 2015)
Log Message
update messages
On 29.06.2015 10:14 PM, David Evans wrote:
One small additional suggestion. The error message that is emitted when one
of
the subports is attempted without +quartz still refers to
gtk-osx-application
rather than the subport name. Changing ${name} to ${name}-${gtk_version} in
that message
Dear Josh,
Perhaps pkgconfig?
Yes. You are right. Thanks!
r138121.
Best,
Takeshi
-
Takeshi Enomoto
take...@macports.org
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Monday June 29 2015 01:15:19 Marko Käning wrote:
Ha, I did that a year ago already, but I am not keen to patch Qt5 itself
anymore,
since this had been discussed at length with the Qt devs. They eventually
argued
that Qt5 and all apps based on it should make use of OSX’ standard directories
On Jun 24, 2015, at 3:04 PM, Mark Moll wrote:
Part of the problem is that there is no way to force the default CMake
modules for finding an python interpreter and python libraries to agree on
the same version. As a way around that I wrote my own FindPython.cmake:
On Jun 29, 2015, at 8:10 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jun 24, 2015, at 3:04 PM, Mark Moll wrote:
Part of the problem is that there is no way to force the default CMake
modules for finding an python interpreter and python libraries to agree on
the same version.
10 matches
Mail list logo