Munt Mac OSX version discussion

Developer's Forum for discussion of bugs, code, and other developmental aspects of the Munt Project.

Re: Munt Mac OSX version discussion

Postby sergm » 2013-10-03 @ 08:21

It confidently works under Snow-64 but it's still lacking those "official" txt files...
sergm
Oldbie
 
Posts: 734
Joined: 2011-2-23 @ 16:37

Re: Munt Mac OSX version discussion

Postby ufoufo512 » 2013-10-06 @ 09:10

Ok. :blush: I'll add the txt files to bundle.
ufoufo512
Newbie
 
Posts: 38
Joined: 2010-1-27 @ 05:47

Re: Munt Mac OSX version discussion

Postby ufoufo512 » 2013-10-06 @ 09:31

Here is a link to an updated dmg-package. https://dl.dropboxusercontent.com/u/308 ... T32Emu.dmg It now includes DOCS folder with AUTHORS.txt, COPYING.txt, NEWS.txt and README.txt text files. Hopefully that is what was requested. Things still to do:
1) Visual stuff. Proper icon and maybe a folder background image. Anyone?
2) Signing of the package. Maybe dominus can help?
3) Distribution. Should this be distributed on sourceforge?
ufoufo512
Newbie
 
Posts: 38
Joined: 2010-1-27 @ 05:47

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-06 @ 10:27

Ah, yes. I can help with signing. I return hom on tuesday and can then sign the app(will have to re-image the dmg, though).
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-08 @ 18:44

I ran into some problems signing...
The framework for the QT stuff seems to need its info.plist file as per http://stackoverflow.com/questions/9476 ... 6#18143296 or signing will always fail.
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

Re: Munt Mac OSX version discussion

Postby ufoufo512 » 2013-10-09 @ 09:02

Pity to hear about the signing problem. I'll study the link you posted later today. My previous experience with signing Mac builds has been that I have signed both the libraries and the actual executable separately with no issues, but this case seems a bit different. Need to look into it...
ufoufo512
Newbie
 
Posts: 38
Joined: 2010-1-27 @ 05:47

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-09 @ 10:39

Hmm, I'll see about signing each binary individually.

Edit: I wonder, did you already sign it? I cannot trigger a negative gatekeeper response to the downloaded file. This is with OS X Maverick, so maybe things changed a bit...
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

Re: Munt Mac OSX version discussion

Postby ufoufo512 » 2013-10-12 @ 09:36

I didn't sign it. Maybe Qt binaries have signing on them by Qt folks.
ufoufo512
Newbie
 
Posts: 38
Joined: 2010-1-27 @ 05:47

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-13 @ 21:07

You are right, on a new 10.8.5 installation in a VM Gatekeeper rejects the app. So after signing everything individually, you can get it from https://dl.dropboxusercontent.com/u/773 ... -1.1.0.dmg (edited to point at the later discussed version).
- moved the qt_menu.nib from the QTGui resources to the main resources folder of the App (as per some obscure hint somewhere on the web)
- gave the dmg the name "MT32Emu 1.3.0"
- the dmg got slightly smaller (mostly because it doesn't have the folders .fseventsd, .DocumentRevisions-V100, .TemporaryItems and no .DS_Store file)

So, Sergm, I think you can put that up on the official dl page :)
Last edited by Dominus on 2013-10-14 @ 07:50, edited 2 times in total.
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

Re: Munt Mac OSX version discussion

Postby sergm » 2013-10-14 @ 06:06

Great news, guys!
As for publishing: naming you use is a bit confusing. AFAICT, the image contains the build of mt32emu_qt solely, no library framework files. The damn DOCS folder also contains mt32emu_qt specific files only. So, I'd rename it to something like mt32emu-qt-1.1.0.dmg instead. How does it sound?

You can also consider adding to the package a proper (for OS X directory layout) Framework to allow static linking to the library out of the box. In this case all the above said becomes a bit inconsistent though ;)
sergm
Oldbie
 
Posts: 734
Joined: 2011-2-23 @ 16:37

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-14 @ 06:52

I'd say mt32emu-qt-1.3.0.dmg ;)
If you want I can change the finder displayed title of the dmg as well to that (only takes a minute and a bit to do and upload)
I can see why you'd want the framework there as well, but IMO the framework should be a seperate package. For an OS X end user the QT package is the only one he/she needs. Adding the framework to that will only confuse ;)
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

Re: Munt Mac OSX version discussion

Postby sergm » 2013-10-14 @ 06:59

OK, agree about end users ;)

But the version numbers of the package and mt32emu-qt thing are different in fact, so I am not mistaken.
sergm
Oldbie
 
Posts: 734
Joined: 2011-2-23 @ 16:37

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-14 @ 07:25

He he, oops ;)
I'll make a new dmg
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

Re: Munt Mac OSX version discussion

Postby sergm » 2013-10-14 @ 07:34

Yes, please.
Though, that per-project versioning confuses me myself. And keeping separate projects in one repo isn't any better. Hmm, it's heritage we have.
sergm
Oldbie
 
Posts: 734
Joined: 2011-2-23 @ 16:37

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-14 @ 07:49

ok, here it is https://dl.dropboxusercontent.com/u/773 ... -1.1.0.dmg with the dmg title "MT32Emu-Qt 1.1.0"
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

Re: Munt Mac OSX version discussion

Postby sergm » 2013-10-14 @ 07:55

Cool, uploading...
sergm
Oldbie
 
Posts: 734
Joined: 2011-2-23 @ 16:37

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-17 @ 22:08

sergm wrote:Well, at least, DOSBox should be excluded from your list. I remember midiconfig changed the port it connects to.

Back to the "problem" of port in coremidi. I couldn't find any way to control this in DOSBox so that it favors Munt-qt over USB. Only when you disconnect the USB-Midi device can you control via midiconfig=Mt32EmuPort which port of the MT32Emu it should use. So if I add a new Midi port in MT32Emu I can switch between those MT32Emu ports by using midiconfig=Mt32EmuPort or midiconfig=Mt32EmuPort1 etc...
So definitely keep this in mind for OS X that the software CoreMidi driver will only work after real hardware is disconnected.
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

Re: Munt Mac OSX version discussion

Postby sergm » 2013-10-18 @ 05:28

Bah, that is really disappointing...
sergm
Oldbie
 
Posts: 734
Joined: 2011-2-23 @ 16:37

Re: Munt Mac OSX version discussion

Postby Qbix » 2013-10-18 @ 08:14

midiconfig for coremidi wants a number, not a name
Water flows down the stream
How to ask questions the smart way!
User avatar
Qbix
DOSBox Author
 
Posts: 10445
Joined: 2002-11-27 @ 14:50
Location: Fryslan

Re: Munt Mac OSX version discussion

Postby Dominus » 2013-10-18 @ 08:17

Interesting, so when I entered mt32emuport and mt32emuport1 it thought of it as 0 and 1?
User avatar
Dominus
DOSBox Moderator
 
Posts: 7381
Joined: 2002-10-03 @ 09:54
Location: Vienna

PreviousNext

Return to MT-32 Development

Who is online

Users browsing this forum: No registered users and 1 guest