On 2018-6-29 01:18 , Langer, Stephen A. (Fed) wrote:
>
> I meant to add a link to our distutils source, if anyone's interested:
> https://github.com/usnistgov/OOF3D/tree/macports-packaging/shlib
>
> The master branch doesn't yet have the latest modifications.
Looks pretty reasonable. You could
On 6/28/18, 4:00 PM, "Ryan Schmidt" wrote:
On Jun 28, 2018, at 14:56, Langer, Stephen A. (Fed) wrote:
> It's the same problem as
On Jun 28, 2018, at 14:56, Langer, Stephen A. (Fed) wrote:
> It's the same problem as https://trac.macports.org/ticket/56461 and
> https://trac.macports.org/ticket/54981. Is that a problem with glib2 or
> with all of the ports that use it?
My understanding is that those other ports are not
On 6/28/18, 3:30 PM, "Ryan Schmidt" wrote:
On Jun 28, 2018, at 14:00, Langer, Stephen A. (Fed) wrote:
> It *is* rebuilding glib2 when I run "port mpkg oof3d". I have -x11
+no_x11 +quartz in variants.conf, but glib2 is installed with +x11. Is mpkg
noticing that the
On Jun 28, 2018, at 14:00, Langer, Stephen A. (Fed) wrote:
> It *is* rebuilding glib2 when I run "port mpkg oof3d". I have -x11 +no_x11
> +quartz in variants.conf, but glib2 is installed with +x11. Is mpkg
> noticing that the installed variant isn't the default variant and thinking
>
On Jun 28, 2018, at 13:10, Langer, Stephen A. (Fed) wrote:
> I just ran "sudo port mpkg oof3d", without any other arguments. I had
> changed my PATH so that only the minimal, non-standardly-located ports
> directory was visible. (Minimal means only dependencies of oof3 are
> installed.)
On 6/28/18, 12:17 PM, "Ryan Schmidt" wrote:
On Jun 28, 2018, at 11:02, Langer, Stephen A. (Fed) wrote:
> In any case, thanks to all of your suggestions, I can now build and
install using the Portfile. I can create an mpkg and install from it.
However, the contents of the
Oops -- forgot to reply to the list.
On 6/28/18, 2:09 PM, "Langer, Stephen A. (Fed)"
mailto:stephen.lan...@nist.gov>> wrote:
On 6/28/18, 12:17 PM, "Ryan Schmidt" wrote:
On Jun 28, 2018, at 11:02, Langer, Stephen A. (Fed) wrote:
> In any case, thanks to all of your
On Jun 28, 2018, at 11:02, Langer, Stephen A. (Fed) wrote:
> In any case, thanks to all of your suggestions, I can now build and install
> using the Portfile. I can create an mpkg and install from it. However, the
> contents of the mpkg are incorrect. There are missing symbols in
>
On 6/28/18, 4:54 AM, "Ryan Schmidt" wrote:
On Jun 27, 2018, at 13:47, Langer, Stephen A. (Fed) wrote:
> It requires knowing the installation prefix during the distutils build
stage, which certainly can be done, but I don't think it's standard in the
distutils world. At
On 6/28/18, 11:12 AM, "macports-users on behalf of Langer, Stephen A. (Fed)"
wrote:
On 6/28/18, 5:39 AM, "Joshua Root" wrote:
On 2018-6-28 18:54 , Ryan Schmidt wrote:
>
> macOS has been around for over 17 years. It would be weird if in all
that time
On 6/28/18, 5:39 AM, "Joshua Root" wrote:
On 2018-6-28 18:54 , Ryan Schmidt wrote:
>
> macOS has been around for over 17 years. It would be weird if in all that
time Python hasn't developed an easy way to create correct dylibs. My
assumption therefore is that such an easy
On 2018-6-28 18:54 , Ryan Schmidt wrote:
>
> macOS has been around for over 17 years. It would be weird if in all that
> time Python hasn't developed an easy way to create correct dylibs. My
> assumption therefore is that such an easy method does exist, I just don't
> know what it is since I'm
On Jun 27, 2018, at 13:47, Langer, Stephen A. (Fed) wrote:
> It requires knowing the installation prefix during the distutils build stage,
> which certainly can be done, but I don't think it's standard in the distutils
> world. At least, the prefix isn't accessible to the build_ext command
On 6/27/18, 12:28 AM, "Ryan Schmidt" wrote:
On Jun 26, 2018, at 10:07, Langer, Stephen A. (Fed) wrote:
> That's what I don't understand. When not using MacPorts, we use
install_name_tool to fix the libraries. They're built in
$HOME/project/build/{lib, include, etc} and
On Jun 26, 2018, at 10:07, Langer, Stephen A. (Fed) wrote:
> That's what I don't understand. When not using MacPorts, we use
> install_name_tool to fix the libraries. They're built in
> $HOME/project/build/{lib, include, etc} and moved to $PREFIX /{lib, include,
> etc}, at which point
On 2018-6-27 01:07 , Langer, Stephen A. (Fed) wrote:
> That's what I don't understand. When not using MacPorts, we use
> install_name_tool to fix the libraries. They're built in
> $HOME/project/build/{lib, include, etc} and moved to $PREFIX /{lib, include,
> etc}, at which point
On 6/25/18, 8:42 PM, "Joshua Root" wrote:
> I still have at least one problem. We had to extend distutils so that it
builds a few .dylib shared libraries that are linked to by the more standardly
built python extension modules, which are all .so bundles. All of them are
being
> I still have at least one problem. We had to extend distutils so that it
> builds a few .dylib shared libraries that are linked to by the more
> standardly built python extension modules, which are all .so bundles. All of
> them are being installed in the correct location, but the .dylibs
On 6/22/18, 10:35 PM, "Ryan Schmidt" wrote:
On Jun 22, 2018, at 09:12, Langer, Stephen A. (Fed) wrote:
> If I change the MacPorts build phase so that it runs "python setup.py
build install --prefix=${destroot}, then everything that MacPorts needs to
install will be in
On Jun 22, 2018, at 09:12, Langer, Stephen A. (Fed) wrote:
> If I change the MacPorts build phase so that it runs "python setup.py build
> install --prefix=${destroot}, then everything that MacPorts needs to install
> will be in ${destroot}/lib, ${destroot}/bin, etc. Will the default
On 6/22/18, 10:28 AM, "Joshua Root" wrote:
> I'm making some progress in writing a Portfile for my project, but I'm
stuck on one point. The project's build script uses python distutils (which
I'd be happy to get rid of but that's not likely to happen soon). The build
commands,
> I'm making some progress in writing a Portfile for my project, but I'm stuck
> on one point. The project's build script uses python distutils (which I'd be
> happy to get rid of but that's not likely to happen soon). The build
> commands, outside of MacPorts, are
>
> python setup.py build
On 6/21/18, 11:01 PM, "Ryan Schmidt" wrote:
On Jun 21, 2018, at 16:46, Langer, Stephen A. (Fed) wrote:
> Hi--
>
> I'm making some progress in writing a Portfile for my project, but I'm
stuck on one point. The project's build script uses python distutils (which
On Jun 21, 2018, at 16:46, Langer, Stephen A. (Fed) wrote:
> Hi--
>
> I'm making some progress in writing a Portfile for my project, but I'm stuck
> on one point. The project's build script uses python distutils (which I'd be
> happy to get rid of but that's not likely to happen soon).
Hi--
I'm making some progress in writing a Portfile for my project, but I'm stuck on
one point. The project's build script uses python distutils (which I'd be
happy to get rid of but that's not likely to happen soon). The build
commands, outside of MacPorts, are
python setup.py build --3D
Regarding +x11 vs +quartz, you can use a line like this (from PortGroup
active_variants) to check that dependents (e.g. gtk2) have the right
variant (namely, yes +quartz and not +x11):
require_active_variants gtk2 quartz x11
David
On Fri, Jun 15, 2018 at 6:53 PM, Ryan Schmidt
wrote:
>
> On
On Jun 14, 2018, at 12:58, Langer, Stephen A. (Fed) wrote:
> Thanks for the advice. If I make a new non-standardly located macports
> directory on my system, build my program and all of its dependencies in that
> directory (including dependencies that aren't packaged with macports), and
>
> On Jun 14, 2018, at 1:58 PM, Langer, Stephen A. (Fed)
> wrote:
>
> On 6/13/18, 8:37 PM, "Craig Treleaven" wrote:
>
>> On Jun 13, 2018, at 6:35 PM, Rainer Müller wrote:
>>
>> On 2018-06-13 21:37, Langer, Stephen A. (Fed) wrote:
>>> (2) Package all of the compiled libraries and
On 6/13/18, 8:37 PM, "Craig Treleaven" wrote:
> On Jun 13, 2018, at 6:35 PM, Rainer Müller wrote:
>
> On 2018-06-13 21:37, Langer, Stephen A. (Fed) wrote:
>> (2) Package all of the compiled libraries and dependencies into a
Mac-like app and distribute binaries, but not a
> On Jun 13, 2018, at 6:35 PM, Rainer Müller wrote:
>
> On 2018-06-13 21:37, Langer, Stephen A. (Fed) wrote:
>> (2) Package all of the compiled libraries and dependencies into a Mac-like
>> app and distribute binaries, but not a portfile. Will "port pkg" do this
>> if I write a portfile for
On 2018-06-13 21:37, Langer, Stephen A. (Fed) wrote:
> (2) Package all of the compiled libraries and dependencies into a Mac-like
> app and distribute binaries, but not a portfile. Will "port pkg" do this if
> I write a portfile for the project? Can I tell it to include the vtk
> libraries
Hi --
I develop a program that has until now been distributed just as source code,
along with instructions on how to use MacPorts and other package managers to
install its dependencies on macOS and various flavors of Linux. Our build
script compiles the program and installs C++ libraries and
33 matches
Mail list logo
