Open CASCADE Community Edition has both a git clone url
(https://github.com/tpaviot/oce.git) and a tarball for download. I read in the
port documentation that fetching with git url may cause non-reproducible
builds, so downloaded the tarball
Those ports give the user a choice of compilers. How is the user supposed to
know which compiler to choose? Is there a best compiler?
On Jun 12, 2014, at 8:05 PM, Sean Farley s...@macports.org wrote:
Mark Brethen writes:
I'm writing a port for FreeCAD which requires a Fortran Compiler.
On 6/14/14 6:24 AM, Mark Brethen wrote:
Open CASCADE is required to build FreeCAD, and since it is a software
development platform for 3D surface and solid modeling I thought it deserved
its own Portfile.
Yes, it should be a separate port. While the lines you have written are
not incorrect
On Jun 14, 2014, at 9:06 AM, David Evans dev...@macports.org wrote:
While the lines you have written are
not incorrect per se, the preferred approach would be to use the github
PortGroup to do all this (and more) for you more simply.
This is what I have in the Portfile so far:
# -*-
Hi Mark,
Some observations about this Portfile:
On Jun 14, 2014, at 9:49 AM, Mark Brethen mark.bret...@gmail.com wrote:
This is what I have in the Portfile so far:
# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
c-basic-offset: 4 -*-
On 2014-6-14 23:24 , Mark Brethen wrote:
Open CASCADE Community Edition has both a git clone url
(https://github.com/tpaviot/oce.git) and a tarball for download. I read in
the port documentation that fetching with git url may cause non-reproducible
builds, so downloaded the tarball
On Jun 14, 2014, at 11:01 AM, Frank Schima m...@macports.org wrote:
Hi Mark,
Some observations about this Portfile:
On Jun 14, 2014, at 9:49 AM, Mark Brethen mark.bret...@gmail.com wrote:
This is what I have in the Portfile so far:
# -*- coding: utf-8; mode: tcl; tab-width: 4;
I've noticed that more a few Portfile's have invalid homepage entries.
I hacked/copied/pasted portlivecheck.tcl to have livecheck output
errors. Is there already a way of doing this or a better way?
Kurt
Index: base/src/port1.0/portlivecheck.tcl
Mark Brethen writes:
Those ports give the user a choice of compilers. How is the user supposed to
know which compiler to choose? Is there a best compiler?
By default, the fortran compiler from gcc48 will be used (though, I
guess I should make that gcc49 soon) so the user doesn't have to
Begin forwarded message:
From: Mark Brethen mark.bret...@gmail.com
Subject: Re: Open CASCADE Community Edition fetch type
Date: June 14, 2014 at 12:19:15 PM CDT
To: Frank Schima m...@macports.org
Cc: MacPorts Development macports-dev@lists.macosforge.org
On Jun 14, 2014, at 11:01 AM,
On 2014-6-15 10:09 , Mark Brethen wrote:
Begin forwarded message:
From: Mark Brethen mark.bret...@gmail.com
Subject: Re: Open CASCADE Community Edition fetch type
Date: June 14, 2014 at 12:19:15 PM CDT
To: Frank Schima m...@macports.org
Cc: MacPorts Development
I have an unfinished portfile for OpenCASCADE 6.3.0 I was working on in July
2010, but nothing about our portfiles is similar. Maybe that was a different
software package.
On Jun 14, 2014, at 12:19 PM, Mark Brethen wrote:
Revised Portfile based on comments from the group:
# -*- coding:
On Jun 14, 2014, at 4:55 PM, Kurt Hindenburg wrote:
I've noticed that more a few Portfile's have invalid homepage entries. I
hacked/copied/pasted portlivecheck.tcl to have livecheck output errors. Is
there already a way of doing this or a better way?
I'm not sure I understand completely.
On Jun 14, 2014, at 7:27 PM, Ryan Schmidt ryandes...@macports.org wrote:
I have an unfinished portfile for OpenCASCADE 6.3.0 I was working on in July
2010, but nothing about our portfiles is similar. Maybe that was a different
software package.
On Jun 14, 2014, at 12:19 PM, Mark
On Jun 14, 2014, at 6:42 PM, m...@macports.org wrote:
Revision
121029
Author
m...@macports.org
Date
2014-06-14 16:42:28 -0700 (Sat, 14 Jun 2014)
Log Message
audacious audacious-core audacious-plugins: New ports. (#25260)
--- trunk/dports/multimedia/audacious-core/Portfile
On 6/14/14, 8:31 PM, Ryan Schmidt wrote:
On Jun 14, 2014, at 4:55 PM, Kurt Hindenburg wrote:
I've noticed that more a few Portfile's have invalid homepage entries. I
hacked/copied/pasted portlivecheck.tcl to have livecheck output errors. Is
there already a way of doing this or a better
+platform darin {
Both audacious-core and audacious-plugins contain this line. I think
you darwin.
Craig
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Jun 14, 2014, at 7:22 PM, Joshua Root j...@macports.org wrote:
On 2014-6-15 10:09 , Mark Brethen wrote:
Begin forwarded message:
From: Mark Brethen mark.bret...@gmail.com
Subject: Re: Open CASCADE Community Edition fetch type
Date: June 14, 2014 at 12:19:15 PM CDT
To: Frank Schima
On Jun 14, 2014, at 7:58 PM, Kurt Hindenburg wrote:
On 6/14/14, 8:31 PM, Ryan Schmidt wrote:
On Jun 14, 2014, at 4:55 PM, Kurt Hindenburg wrote:
I've noticed that more a few Portfile's have invalid homepage entries. I
hacked/copied/pasted portlivecheck.tcl to have livecheck output errors.
* On 15.06.2014 02:51 am, Ryan Schmidt wrote:
On Jun 14, 2014, at 6:42 PM, m...@macports.org wrote:
libtool is also usually needed to autoreconf. You should verify whether this
port builds ok when libtool is deactivated; if not, add the libtool build
dependency as well.
I built with trace
* On 15.06.2014 03:40 am, Mihai Moldovan wrote:
* On 15.06.2014 02:51 am, Ryan Schmidt wrote:
+if {[info exists configure.cxx_stdlib]
Now that MacPorts 2.3.0 has been released, configure.cxx_stdlib does exist,
so there's no need to check for it.
What's a better way to handle this? That
Hi guys,
I think I have found the reason for two KDE problems on OS X and MacPorts:
1. When a KDE app crashes, Dr Konqi often fails to run and produce
the backtrace KDE developers ask for.
2. Also the debug dialog fails to run and take the user through the
steps to
On Sat, Jun 14, 2014 at 10:25 PM, Ian Wadham iandw...@gmail.com wrote:
The procedure for closing the file descriptors is a bit brute force. It
uses
struct rlimit rlp; getrlimit(RLIMIT_NOFILE, rlp); to find out how many
open files the user is allowed (my system says 2560) and then does
OCE's Makefile does not appear to support the DESTDIR variable. In my first
build it put all the files in /usr/local. So I tried to set the variable
-DOCE_INSTALL_PREFIX:PATH=${destroot}${prefix} but this resulted in warning
messages:
--- Updating database of binaries
Warning: Error
This patch fixes the darwin typo, a TCL issue that has been shadowed by the
aforementioned typo and doesn't explicitly check for the existence of
${configure.cxx_stdlib}.
Also revbumped to have the correct min version target set.
--- multimedia/audacious/Portfile.old 2014-06-15
Thanks for your very prompt reply, Bradley.
On 15/06/2014, at 1:03 PM, Brandon Allbery wrote:
On Sat, Jun 14, 2014 at 10:25 PM, Ian Wadham iandw...@gmail.com wrote:
The procedure for closing the file descriptors is a bit brute force. It uses
struct rlimit rlp; getrlimit(RLIMIT_NOFILE, rlp);
26 matches
Mail list logo
