On Oct 4, 2018, at 10:26, Ken Cunningham wrote:
> On 2018-10-04, at 8:19 AM, Ryan Schmidt wrote:
>>
>> Josh brought up some reasonable objections:
>>
>> https://lists.macports.org/pipermail/macports-dev/2018-October/039443.html
>>
>
> I was thinking about Josh's concerns.
>
> Seems to me t
I’m ready to help with DOSBox, since I’ve dealt with it a lot through the years
and am using MacPorts for other things and at least know how to read a port
file. BUT for the snapshots I’m not using MacPorts but instead build a
minimalistic prefix for the snapshots I am doing (Exult, Pentagram, N
On 2018-10-04, at 8:19 AM, Ryan Schmidt wrote:
>
> Josh brought up some reasonable objections:
>
> https://lists.macports.org/pipermail/macports-dev/2018-October/039443.html
>
I was thinking about Josh's concerns.
Seems to me that if dosbox is an end-of-the-chain piece of software, that
sup
Here's the very simple Portfile I used to do the 64bit build. Probably yours is
similar.
---
# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
PortSystem 1.0
namedosbox
version
On Oct 4, 2018, at 10:14, Ken Cunningham wrote:
> 2. do an SDK trick with MacOS.10.13.sdk so it builds 32bit on Mojave (pretty
> easy, but required manual intervention)
This requires the MacOSX.sdk port and changes to base that I've mentioned
before.
https://lists.macports.org/pipermail/mac
Sounds like you're all over this.
We can keep the 32bit builds on PPC and all Intel systems prior to Mojave. The
patches and Portfile might need to be tweaked for the current release.
For Mojave, we have two options:
1. force a 64bit build no matter what (easy)
2. do an SDK trick with MacOS.10
On 04.10.18 14:13, S. L. Garwood wrote:
> I normally copy/paste the long string of ‘rm’ commands in the
> document. Up to now it (i.e., High Sierra) it worked ok.
What exactly did you do? Do you have logs? "sudo rm ..." definitely
works for me in Mojave, as long as the user executing the command
A follow up to my previous posting …
I was trying to uninstall MacPorts using the command list in the
Documentation->Uninstall part of the web site …
Had errors that looked like permissions problems. Logged on as system
administrator and it worked.
Its different behavior from High Sierra - my n
The developers of DOSBox know that it needs to improve but it’s not an easy
task. And yes, you are right for most things the 64bit performance is more than
enough and the more power the host machine has the less noticeable it is. Only
the “latest” Dos games, most prominent the build engine games
One might hope that could get a little better in time. But I imagine it's
still faster than the ancient systems it emulates, so aside from power usage
e.g. on a laptop, presumably it's still usable for most purposes, if not ideal.
> On Oct 4, 2018, at 03:36, Dominik Reichardt wrote:
>
> JFYI,
JFYI, while the 64bit DOSBox now builds and runs correctly, the performance
penalty is still enormous. DOSBox built in 64bit is running at roughly 55% of a
32bit build.
Dom
> On 4. Oct 2018, at 02:39, Ken Cunningham
> wrote:
>
> I have the update done and I'm using it now.
>
> Just working
11 matches
Mail list logo
