Home | Forums | What's new | Resources | |
Developing under linux |
mrkotfw - May 4, 2003 |
antime | May 4, 2003 | |||
If you choose to install the compiler to directory /foo/bar, then when you open a terminal for compiling you should set the path to /foo/bar/bin:$path (the exact syntax depends on the shell you're using). You can write a small script that does this and does whatever other initialisation you want. You can get the GNUSH toolchain from www.gnush.com.... |
mrkotfw | May 4, 2003 | |||
that doesnt seem to work, im installing it as: /home/piratero/ssdk/SATURN so.... |
mrkotfw | May 4, 2003 | |||
could you maybe log onto IRC? my nick is piratero on EFNET well some people told me but i still dont get it... /me has a hard head |
antime | May 4, 2003 | |||
Yeah, I should have enough disk quota left to host it. By the by, the Sega compiler is DOS software (using an extender), so Wine may not help if you're still trying to go that route. |
ExCyber | May 4, 2003 | |||
The .tar.bz2 of the work in progress on my disk now is a little less than 8MB. If disk space is a problem I could produce a stripped down archive (just getting rid of the precompiled sample binaries cuts it down by about 3MB, and that's even without going in and getting rid of the .o files) and/or write a script to convert the standard one, the modifications needed aren't as bad as I thought (AFAICT, haven't been able to test the produced binary but there are no longer any build errors) and I'm using unmodified library files, so it would probably be a waste to duplicate everything... edit: cleaned out the .o files, now it's down to about 2.7MB |
antime | May 4, 2003 | |||
OK, send me a mail/message on where I can pick it up and I'll put it on the page. |
ExCyber | May 4, 2003 | |||
Well, it's not quite done yet, but I think (hope? still don't have commslink so I can't test without burning a CD, which will have to wait until tomorrow) the worst is over (error messages like "file format is ambiguous" tend to get a guy's spirits down). I'd like to get it to where all the samples can be compiled as well... update: pretty much finished, going to see if I can get someone who can run an emulator to test binaries in a bit. The build system for ip.bin is pretty hairy, so I haven't got it working, but I don't think it's worth it to delay putting together the package with the contest deadline looming and all... |
ExCyber | May 4, 2003 | |||
D'oh! Never mind, there's a linker problem that's going to delay it a bit longer. |
ExCyber | May 5, 2003 | |||
Tried a produced binary on a Saturn, didn't work. Still not giving up, but it's hard to say how long it will take now. update: was just a stupid error in my linker script tweaks. Akira is walking around my TV screen as I type this. Cleanup and release soon I guess. |
ExCyber | May 5, 2003 | |||
Whoever has the KPIT SuperH toolchain, what are the names of the program files? Is it just sh-coff-gcc, sh-coff-as, sh-coff-ld etc, or have they used other names? edit: also, what are the versions of the programs (I'm mainly interested in GCC and ld versions, but whatever else you feel like posting is fine |
TakaIsSilly | May 6, 2003 | ||||
Code:
All remaining files use normal nomenclature. KPIT's has his compiller rebuilt with all major GCC releases, up to the v3 one a month or so ago, altough mine's is still the GNUSH_v0204 release for gcc and ld. |
ExCyber | May 7, 2003 | ||||
Thanks. The reason I ask is that, oddly enough, I'm using an sh-elf toolchain (the one I built for Dreamcast stuff, in fact) without problems and wanted to provide KPIT-compatible definitions in the Makefile since that seems to be the easiest way for most people to get a SuperH cross compiler...
What releases of GCC and binutils do these correspond to? I'm currently using GCC 3.0.4 and binutils 2.11.2 at the moment, for what it's worth... |
antime | May 7, 2003 | |||
The latest release... is based on a pre-release GCC 3.3 and Binutils 2.13.2.1. |
ExCyber | May 12, 2003 | |||
Okay, the "fixed" SGL distribution is available on antime's site in the "Compilers, Libs, and Tools" section. I'd appreciate any feedback on how this works for people, especially those using GCC 2.x.x, 3.2.x, or prereleases. In theory this should work on Windows as well as on Unix/Linux systems, so I'd like to know if that is indeed the case. What's changed: - Eliminated precompiled object files for samples (except the sample ip.bin, which can't currently be built without the DOS/Windows-specific SuperH assembly translation system "GASP") for huge space/bandwidth savings. - Moved all configuration for samples to the top-level Makefile.template; define your compiler/path here once instead of editing the Makefile for each sample. - Ran all important sources/headers through a DOS->UNIX text conversion program to eliminate errors like "stray /032 in program". - Fixed a bug in one of the samples that resulted in lib/sglarea.o being deleted during the clean process. |