Search results

Yes, exactly. They have a policy for not producing universal libraries and includes, so this is a consequence. I used MacPorts for PowerPC, but I didn't know it was still going for Intel and ARM64 (I have used MacPorts when setting up some PowerPC Macs in the past year). Maybe we should turn...

@MIST, @Mu0n , @8bitbubsy , @noglin @bribri . Hi folks, I'm trying to work with Retro68. I can see from this example CMake.lst how it builds an application (NanoMacTracker). cmake_minimum_required(VERSION 3.28) project(NanoMacTracker) enable_language(C ASM) add_application(NanoMacTracker...

Thanks! On GitHub I am also Snial. Good idea. I think there’s some ambiguity when it comes to mapping Pascal’s Strxx types to ‘C’, because sometimes in Pascal is could cause storage to be allocated whereas at other times it’s just a pointer. Also, ‘C’ would expect zero-terminated strings...

Could you publish your changes? Either by forking the original and pushing that or by zipping the .c and .a? I think it would be a good idea to not have a default .MOD, because if you don't want to play AXELF.MOD (as great as it is), then you're still wasting hundreds of kB. I think bug (1) is...

I'll be able to fix that and I've been looking at it a bit. I can see you've replaced the lea's module_data in the assembly code: /* lea module_data+PATTERN_DATA_OFFSET(%pc),%a0 */ movea.l module_ptr(%pc),%a0

@MIST , @Mu0n : I can now build and run NanoMacTracker. https://68kmla.org/bb/index.php?threads/retro68-build-issues.50537/post-569396

I've been reading some of the documentation on building and running apps for Retro68 (ToughDev, Henlin's simplified guide), but again it seems to be a case of people not specifying critical information a newbie to CMake or Retro68 might not be aware of. The bit I didn't understand is where I'm...

We can take this a bit further. Lots of EVs provide V2L these days (Vehicle to Load), which means you can power mains appliances from an EV (e.g. if you're camping). A Mac Plus takes 60W. A typical modern EV has at least 50kWh of battery, so you could power your Mac Plus from a charged EV for...

@bribri , @Mu0n , @8bitbubsy , @MIST, @noglin. OK! It looks like I'm there: Done building Retro68. The toolchain has been installed to: /Users/julianskidmore/Development/Retro68Dev/Retro68-build/toolchain/ I think I can try building the MOD player next!

The reason why there are two different directories is because homebrew can't (or couldn't) build universal binaries. So, the Intel ones stay in /usr/local/[include], but the arm64 ones go in opt/homebrew/[include]. If you need both (or think you do), then the Intel directories ought to stay...

@bribri , @Mu0n , @8bitbubsy , @MIST, @noglin. OK, I've made a bit more progress, I now know where the wrong prototype is coming from and why, but I don't yet know the best way to solve it. To recap, the compilation fails, because libResourceFiles.a contains the x86_64 signature for...

I would normally use THINK C 5 for development. The nice thing is that it will run happily on a Mac Plus emulator in 4MB. However, it uses Motorola syntax for assembly rather than gas. For example, %d0 instead of d0. Also, it only supports inline assembly and doesn't support .rept. I haven't...

@joevt , thanks for the informative reply! @bribri , @Mu0n , @8bitbubsy , @MIST, @noglin. OK, I've made a bit more progress now in analysing the problem if not solving it. Going back to the error message I realised the problem isn't with ResInfo.cc.o , the newly compiled file that's being...

Thanks, it looks like the signature for your /opt/homebrew/lib/libboost_filesystem.dylib is the same as mine. Did you check that: cat pathTo/Retro68-build/build-host/ResourceFiles/CMakeFiles/ResInfo.dir/link.txt Says: /usr/bin/c++ -Wall -Werror=return-type -Wno-multichar -g -arch arm64...

OK. I've made a bit more progress. You can list the symbols in a dylib using nm -gU libraryName.dylib . Because I knew I had an x64 and arm64 version of libboost_filesystem.dylib , I figured I could list the symbols for each architecture; pipe them to grep "append" , because it was an append...

A minor improvement. I deleted the entire build tree in case it was trying to use a library it thought it had already built. I then re-ran the build for Retro68. It fell over just like before. This time though I've found the link command that caused the failure. /usr/bin/c++ -Wall...

Well, it didn't blow up, however, I still have the same problem when building Retro68: -- Found Boost: /opt/homebrew/lib/cmake/Boost-1.88.0/BoostConfig.cmake (found version "1.88.0") found components: filesystem program_options -- Configuring done (0.2s) -- Generating done (0.1s) -- Build files...

@bribri , @Mu0n . OK, so I think I'm making progress. $ lipo -info /usr/local/lib/libboost_filesystem.dylib Non-fat file: /usr/local/lib/libboost_filesystem.dylib is architecture: x86_64 $lipo -info /opt/homebrew/Cellar/boost/1.88.0/lib/libboost_filesystem.dylib Non-fat file...