What is the easiest way to install on a Mac?

[Morn76]

I think the MT default is still sqlite for new worlds. You can simply change it to "backend = leveldb" (in world.mt) after you first create but before you first start a world. The LevelDB database will appear in the map.db directory then. Map.sqlite should not be created at all.

If you would like to convert an existing world, use "minetest --server --worldname someworld --migrate leveldb". World.mt will be updated automatically and you can remove map.sqlite then. You will probably want to try this with a copy of your world though, just to be safe. But I've migrated several maps from SQLite to LevelDB and back and so far I've not encountered any problems with the process.

[OmniStudent]

Thanks for the info :)

Do you know what I'm doing wrong if I can't find a world.mt file?

[Morn76]

It should be in ~/Library/Application Support/minetest/worlds/<yourworldname>/ on the Mac I think.

[OmniStudent]

It should be in ~/Library/Application Support/minetest/worlds/<yourworldname>/ on the Mac I think.

It was :)

[Morn76]

OmniStudent & raffahacks, I've made a new build: https://github.com/mdoege/minetest/rele ... g/20140430

I've reinstalled luajit from a Mavericks bottle that was available on the Homebrew Sourceforge site. And I've built a bottle of hiredis according to their Wiki instructions which should be Core 2-compatible.

If this still crashes on the Core 2, please paste the full crash report so we can see where exactly the crash occurs. But I'm really hoping it works now. Fingers crossed. :-)

[OmniStudent]

OmniStudent & raffahacks, I've made a new build: https://github.com/mdoege/minetest/rele ... g/20140430

I've reinstalled luajit from a Mavericks bottle that was available on the Homebrew Sourceforge site. And I've built a bottle of hiredis according to their Wiki instructions which should be Core 2-compatible.

If this still crashes on the Core 2, please paste the full crash report so we can see where exactly the crash occurs. But I'm really hoping it works now. Fingers crossed. :-)

I tried this version on my Core 2, and it crashed immediately :(
When running it from terminal I got the single message "Segmentation Fault". No minetest folder was created in Library/App support/.
My Core2 is missing several libraries, but when the error is due to a missing library it usually says so. I figure its best to not install any libraries with brew on that machine, so that it can be used for testing.

When I tried your build on my new mac, it didn't work at first, had to install luajit and then everything worked.

[Morn76]

I tried this version on my Core 2, and it crashed immediately :(
When running it from terminal I got the single message "Segmentation Fault". No minetest folder was created in Library/App support/.

Well, I need the full crash report. Your old Mac is running Mavericks, right? (Because if it doesn't, the binary won't work anyway.) "Segmentation Fault" alone doesn't help at all.

My Core2 is missing several libraries, but when the error is due to a missing library it usually says so. I figure its best to not install any libraries with brew on that machine, so that it can be used for testing.

Absolutely, that's useful for seeing if the binary has everything it needs.

When I tried your build on my new mac, it didn't work at first, had to install luajit and then everything worked.

Uh oh, that's strange. The bottled version of libluajit is included and the install name in the MT binary is correctly set. It should work. Maybe I should create my own bottle of libluajit and see if that helps.

I've changed the download link in my OS X build thread to 20140429 for now because that still had the old libluajit.

[OmniStudent]

Well, I need the full crash report. Your old Mac is running Mavericks, right? (Because if it doesn't, the binary won't work anyway.) "Segmentation Fault" alone doesn't help at all.

Oops. No, its still on snow leopard. I have the crash report now (didn't know about Library/Logs/DiagnosticReports until I checked this up), but I guess its not very useful.

[Morn76]

And I suppose if you built a binary on your machine and uploaded it to GitHub, it still wouldn't help raffahacks if his Core 2 is on Mavericks, right? It's really a bit complicated with all these different OS X versions.

[OmniStudent]

It might be worth a try, I'll at least start and see what obstacles I run into.

[OmniStudent]

Uninstalled luajit (brew unistall luajit) and reinstalled it to confirm.
20140429.4b44d35 requires luajit installed, while 20140427.088b18d works without it.

I like the zip better in 20140429.4b44d35, with the app appearing in a folder with the zip name.

[Morn76]

Yes, when I said "Minetest 20140429" I actually meant the release with that name, but with the attached zip 20140427.

It's a bit confusing, but I'm labeling the release tags with the actual build/upload date. Whereas the file name contains the date of the latest git commit (HEAD), so it might be a few days earlier.

Anyway, don't forget to run build_libs.sh before uploading. Also, build_libs moves the old library directory to libs.2, which you can delete after checking that the new libs folder contains everything libs.2 had.

Maybe you could rename your ZIP to snow_leopard_minetest, so it gets sorted alphabetically after minetest*zip on GH.

[Morn76]

I think I've tricked myself with my latest build, that's why it needed luajit installed. Because what you need to do is:

1. run make_mac.sh to build an executable using the new libraries
2. run build_libs.sh to scan the executable and create an updated libs/ folder
3. create a new ZIP, e.g. by running make_mac.sh again or doing it manually

I believe I simply forgot step #3 earlier.

So now I've updated the build at https://github.com/mdoege/minetest/rele ... g/20140430 . I'd like to get confirmation that this runs on a new Mac again without the need to install luajit yourself. And of course if Core 2/Mavericks compatibility would work now that would be great.

[OmniStudent]

So now I've updated the build at https://github.com/mdoege/minetest/rele ... g/20140430 . I'd like to get confirmation that this runs on a new Mac again without the need to install luajit yourself. And of course if Core 2/Mavericks compatibility would work now that would be great.

That version works without installing luajit (on my new mac).

[Morn76]

That version works without installing luajit (on my new mac).

Excellent, thanks! So I can change the first post link again. Now we just need to hear from raffahacks if this works on his machine too.

Any progress with your Snow Leopard build?

[OmniStudent]

Any progress with your Snow Leopard build?

It compiled fine with your script, but gave me a segmentation fault when started:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

Process:         bash [13586]
Path:            /Users/security/mtmake-osx-master/releases/minetest.app/Contents/MacOS/minetest
Identifier:      celeron55.minetest
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  launchd [248]

Date/Time:       2014-05-01 17:30:26.474 +0200
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:          3152513 sec
Crashes Since Last Report:           1072
Per-App Crashes Since Last Report:   14
Anonymous UUID:                      45B79329-6214-4452-94D9-BD5BC8E2F58D

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffffffffff8
Crashed Thread:  Unknown

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000055  rbx: 0x0000000000000000  rcx: 0x0000000000000000  rdx: 0x0000000000000000
  rdi: 0x0000000000000000  rsi: 0x0000000000000000  rbp: 0x0000000000000000  rsp: 0x0000000000000000
   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000
  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
  rip: 0x00007fff5fc01028  rfl: 0x0000000000010203  cr2: 0xfffffffffffffff8

Binary images description not available


Model: MacBookPro7,1, BootROM MBP71.0039.B0E, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.62f7
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.131.42.4)
Bluetooth: Version 2.4.5f3, 2 service, 12 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS545032B9SA02, 298.09 GB
Serial ATA Device: HL-DT-ST DVDRW  GS23N
USB Device: Internal Memory Card Reader, 0x05ac  (Apple Inc.), 0x8403, 0x26100000 / 2
USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8507, 0x24600000 / 2
USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06600000 / 4
USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8213, 0x06610000 / 7
USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0x06500000 / 3
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x0237, 0x06300000 / 2

[Morn76]

I think you will have to use the older version of my script (which made MT "Debug" builds) to get a useful crash log:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

cd mtmake-osx
git checkout 69fe4e9b9a

Or get the ZIP: https://github.com/mdoege/mtmake-osx/ar ... b438b1.zip

Of course it might be that this is again an optimization issue and that the Debug build does not crash. :-)

[OmniStudent]

I think you will have to use the older version of my script (which made MT "Debug" builds) to get a useful crash log:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

cd mtmake-osx
git checkout 69fe4e9b9a

Or get the ZIP: https://github.com/mdoege/mtmake-osx/ar ... b438b1.zip

Of course it might be that this is again an optimization issue and that the Debug build does not crash. :-)

Tried that version on the snow leopard core 2. It crashed and got the same error report as the previous one :(
But maybe we can wait with a working version for that one until someone needs it.

I'm a beginner at git and couldn't use the commands you provided. I got

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

 error: pathspec '69.... did not match any files known to git

[Morn76]

Tried that version on the snow leopard core 2. It crashed and got the same error report as the previous one :(
But maybe we can wait with a working version for that one until someone needs it.

A Debug build should normally produce a backtrace. "Backtrace not available" should just happen with Release.

Actually I think you could simply have changed "-DCMAKE_BUILD_TYPE=Release" in make_mac.sh to "-DCMAKE_BUILD_TYPE=Debug". Because unlike xcodebuild, make seems to put both builds directly under "bin/", so the paths in the script don't have to be changed.

[OmniStudent]

/69fe4e9b9a2eefc0067e6fc63591fb5e28b438b1.zip

That one actually had "Release" in it, but even when I changed it to "Debug" I still got the same "backtrace not available" short report. Strange.

[Morn76]

xcodebuild completely ignores cmake's wish for a Release build anyway. I think you would have to use "xcodebuild -configuration=Release" to get an actual release build with xcodebuild. That was one of the reasons I wanted to build with make instead. :-)

Maybe Snow Leopard is missing something? It probably needs gdb installed somewhere for a backtrace. Or gdb is there but doesn't work properly. Very mysterious problem.

[theoluk]

Trying to Install mdoege's minetest build for mac on 10.8.3, I download and unzip the file fine, but when I try to open it the application simply crashes before it opens. (The icon in the dock bounces once and then is gone). Could anybody give me a logical explanation as to what is happening?
Thank You

[Morn76]

10.8.3 is Mountain Lion, but the builds are for 10.9 == Mavericks. So you need to upgrade your OS if you want to use the binaries.

If that isn't possible, you could try to install the dependencies yourself and use the build script linked in the first post at viewtopic.php?f=3&t=9190.