belboz Posted October 21, 2009 Author Share Posted October 21, 2009 I have an update almost ready for the Windows version, and an initial release for Linux. If you want to test the linux version just drop me a PM. If there are any OS X users still interested let me know. (I know some did earlier, but let me know again! also let me know if your wanting a PPC or x86 build of the tools or both) Hi belboz! Was wondering if there was any news on a linux version or a source release for vasm/vbcc/vlink targetting jaguar? Thanks very much for any info! If I can do anything to help (incl. stop bothering you), let me know too... Quote Link to comment Share on other sites More sharing options...
+poobah Posted October 22, 2009 Share Posted October 22, 2009 I have an update almost ready for the Windows version, and an initial release for Linux. If you want to test the linux version just drop me a PM. If there are any OS X users still interested let me know. (I know some did earlier, but let me know again! also let me know if your wanting a PPC or x86 build of the tools or both) intel mac Quote Link to comment Share on other sites More sharing options...
tarkb Posted October 31, 2009 Share Posted October 31, 2009 I have an update almost ready for the Windows version, and an initial release for Linux. If you want to test the linux version just drop me a PM. If there are any OS X users still interested let me know. (I know some did earlier, but let me know again! also let me know if your wanting a PPC or x86 build of the tools or both) Hi belboz! Was wondering if there was any news on a linux version or a source release for vasm/vbcc/vlink targetting jaguar? Thanks very much for any info! If I can do anything to help (incl. stop bothering you), let me know too... Thank you belboz! Did you ever know that you're my hero? Quote Link to comment Share on other sites More sharing options...
Hyper_Eye Posted October 31, 2009 Share Posted October 31, 2009 I have an update almost ready for the Windows version, and an initial release for Linux. If you want to test the linux version just drop me a PM. If there are any OS X users still interested let me know. (I know some did earlier, but let me know again! also let me know if your wanting a PPC or x86 build of the tools or both) Hi belboz! Was wondering if there was any news on a linux version or a source release for vasm/vbcc/vlink targetting jaguar? Thanks very much for any info! If I can do anything to help (incl. stop bothering you), let me know too... Is there any reason not to do a universal build? Quote Link to comment Share on other sites More sharing options...
belboz Posted October 31, 2009 Author Share Posted October 31, 2009 Just in case people missed it since I released a lot of stuff in a couple days. I released versions of the dev tools for Linux and OS X (intel only). http://www.atariage.com/forums/topic/152693-new-developers-and-others-live-cds-released-with-videos/page__view__findpost__p__1868886 Quote Link to comment Share on other sites More sharing options...
belboz Posted October 31, 2009 Author Share Posted October 31, 2009 Well having the time to do it is the big factor. I am not an OS X guru so there might be an easy way to tweak a makefile to generate a universal build, but I am not aware of it. Generally to make a universal build app in the past I have compiled on an x86 and ppc Mac and then used a command line tool to bundle them both into a universal app. For now the few responses for OS X tools seem to have been from x86 Mac users. Is there any reason not to do a universal build? Quote Link to comment Share on other sites More sharing options...
Hyper_Eye Posted October 31, 2009 Share Posted October 31, 2009 Well having the time to do it is the big factor. I am not an OS X guru so there might be an easy way to tweak a makefile to generate a universal build, but I am not aware of it. Generally to make a universal build app in the past I have compiled on an x86 and ppc Mac and then used a command line tool to bundle them both into a universal app. For now the few responses for OS X tools seem to have been from x86 Mac users. Well it happens that I maintain the OS X build for the project in my sig (on top of working on Linux issues for it) and for the parts of it that are built with gcc (or g++) it is quite simple to make a universal build. Simply add this to your cflags and link flags: -arch i386 -arch ppc That's all there is to it. Quote Link to comment Share on other sites More sharing options...
belboz Posted October 31, 2009 Author Share Posted October 31, 2009 I am pretty sure I tried that, but ran into issues with some of the tools that require a big endian / little endian type define at build time. Doing what you list below would work, but I would get a universal binary that wouldn't run properly on one of the architectures. (e.g. it would be built as little endian and the universal binary would work fine on x86 Macs, but PPC macs would not run correctly because the code was still thinking it was a little endian system). -arch i386 -arch ppc That's all there is to it. Quote Link to comment Share on other sites More sharing options...
Hyper_Eye Posted October 31, 2009 Share Posted October 31, 2009 I am pretty sure I tried that, but ran into issues with some of the tools that require a big endian / little endian type define at build time. Doing what you list below would work, but I would get a universal binary that wouldn't run properly on one of the architectures. (e.g. it would be built as little endian and the universal binary would work fine on x86 Macs, but PPC macs would not run correctly because the code was still thinking it was a little endian system). -arch i386 -arch ppc That's all there is to it. That shouldn't be the case unless sections of code are making an assumption about endianness. The compiler itself knows that x86 is little endian and ppc is big endian and it should take care of that. When I compile socket code I have no endian problems in universal builds. I would be curious to know where these problems lie. It would be easy enough to test ppc builds of your tools by building them for ppc only and then they should run through rosetta. Quote Link to comment Share on other sites More sharing options...
belboz Posted October 31, 2009 Author Share Posted October 31, 2009 Yes, some of the code was endian specific and had #ifdef's arround the code. Basically if HOSTBIGENDIAN was set it would handle things assuming the system was a big endian machine. Else it was compiled assuming little endian. I think it was the assembler or linker. Not sure which. That shouldn't be the case unless sections of code are making an assumption about endianness. The compiler itself knows that x86 is little endian and ppc is big endian and it should take care of that. When I compile socket code I have no endian problems in universal builds. I would be curious to know where these problems lie. It would be easy enough to test ppc builds of your tools by building them for ppc only and then they should run through rosetta. Quote Link to comment Share on other sites More sharing options...
tarkb Posted November 21, 2009 Share Posted November 21, 2009 Lastly, I do not want to take w/out giving anything back, so if there is anything I can do to help please let me know. Know anything about writing machine descriptors? One for the RISC's would be rather sweet. It would be nice to have it set up to run out in main or in the local depending on what you need using a directive or something. However, descriptors are a science in their own right. I only wish I understood it better. Hi Gorf! Hope you like books! http://www.amazon.com/gp/product/1558603204?ie=UTF8&tag=atariage&linkCode=xm2&camp=1789&creativeASIN=1558603204 Chapter 6 Producing Code Generators Automatically http://www.amazon.com/gp/product/1558603204?ie=UTF8&tag=atariage&linkCode=xm2&camp=1789&creativeASIN=1558603204 Chapter 15 Code Generation and Local Code Optimization http://www.amazon.com/gp/product/0321486811?ie=UTF8&tag=atariage&linkCode=xm2&camp=1789&creativeASIN=0321486811 Chapter 8 Code Generation http://www.amazon.com/gp/product/155860698X?ie=UTF8&tag=atariage&linkCode=xm2&camp=1789&creativeASIN=155860698X 11.1.1 Building Retargetable Compilers disclaimer: I purchased those recently, it will be years years years before I read them, let alone grok any of their contents. I will post back here in 2026. I guess I have no excuse now, but neither do you, so we are even Quote Link to comment Share on other sites More sharing options...
JagChris Posted February 1, 2010 Share Posted February 1, 2010 (edited) This compiler works really well. I have used it to compile the Doom source and it worked beautifully. Holy cow, this is huge! Is it possible to post your modified Doom sources? Thanks again. I still do way too much work in DOSBox and this could finally mark the end of that... - KS Well now we know why Boz was tinkering around with the Doom source. Edited February 1, 2010 by JagChris Quote Link to comment Share on other sites More sharing options...
belboz Posted February 1, 2010 Author Share Posted February 1, 2010 Actually I have built the Doom source (after fixing some things in it) with the old gcc in the original dev kit, a newer gcc retargeted to the 68K, and with vbcc. Doom just made a nice test case for vbcc Quote Link to comment Share on other sites More sharing options...
Morpheus23 Posted February 24, 2013 Share Posted February 24, 2013 Since the Hillsoft page is no longer available, are the Vista tools available somewhere else? which is better to use, the falcon or Vista? Quote Link to comment Share on other sites More sharing options...
sh3-rg Posted February 24, 2013 Share Posted February 24, 2013 belboz's stuff is here: http://www.hillsoftware.com/files/atari/jaguar/ Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.