On Tuesday June 23 2015 16:27:57 Ryan Schmidt wrote:
On Jun 23, 2015, at 4:21 PM, René J.V. Bertin wrote:
Hairy detail: this project requires exactly Python 3.4.3 - nothing more,
nothing less...
I guess it'll work today, and break when the python34 port is updated to
3.4.4. Not a great
On Jun 24, 2015, at 3:31 PM, take...@macports.org wrote:
Revision
137995
Author
take...@macports.org
Date
2015-06-24 13:31:21 -0700 (Wed, 24 Jun 2015)
Log Message
grib_api, libemos, magicspp: set CMAKE_INSTALL_NAME_DIR in grib_api, revbump
ports that depends on grib_api
---
On Jun 23, 2015, at 7:01 PM, Joshua Root wrote:
On 2015-6-24 07:21 , Ryan Schmidt wrote:
On Jun 22, 2015, at 4:42 PM, Lawrence Velázquez wrote:
On Jun 4, 2015, at 7:32 PM, Ryan Schmidt wrote:
I agree setup procs are not the best.
I also don't like that the semantics of the arguments
On 2015-6-25 10:56 , Ryan Schmidt wrote:
On Jun 23, 2015, at 7:01 PM, Joshua Root wrote:
On 2015-6-24 07:21 , Ryan Schmidt wrote:
On Jun 22, 2015, at 4:42 PM, Lawrence Velázquez wrote:
On Jun 4, 2015, at 7:32 PM, Ryan Schmidt wrote:
I agree setup procs are not the best.
I also don't
Can someone please have a look at these and commit?
https://trac.macports.org/ticket/47823
https://trac.macports.org/ticket/48161
Thanks,
Albert
--
Dr. Albert Graf
Computer Music Research Group, JGU Mainz, Germany
Email: aggr...@gmail.com
WWW:https://plus.google.com/+AlbertGraef
On Tuesday June 23 2015 16:04:39 Ryan Schmidt wrote:
My impression is that cmake is horrible at many things, including finding
dependencies, and that you're best off bypassing automatic dependency finding
by specifying the absolute path to every dependency
About that: how do I get the
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:
https://bitbucket.org/ompl/ompl/src/tip/CMakeModules/FindPython.cmake
You
On Wednesday June 24 2015 15:04:32 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: