Jump to content
Jagware

ggn

Members
  • Content count

    172
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by ggn


  1. By the way, you may be interested by looking at the source code of the renderer I have written for my library.

    I have learnt a lot of things about the blitter while doing this (especially Gouraud/Zbuffer/...)

     

    Unfortunately, I am too lazy (for the moment) to rewrite a more efficient a renderer (ideas are written on paper though).

     

    Okay, will do!

     

    Unfortunately, as you say, the only way to get the best out of the blitter is to write a couple of renderers, learning from the mistakes/experience of the previous ones.

     

     

     

    (OT: maybe it would benefit all to make a semi manual/semi tutorial doc for the blitter? I.E. Explaining in simple words what the registers do and some sample programs like "if you want to do ....., then use this source as base)


  2. Cyrano, when I try to run Make or Nmake using dosbox, it says the program can not run in dos mode. Which is kind of weird.

    No matter if I use a version of make from 94 or a current one.

    How did you get make to work in dosbox?

     

    This sounds like it's confusing make versions. Try typing PATH and see which directories are included. The scan each directory for make.exe or nmake.exe. There may be other versions that are being ran instead of the old make/nmake from the Atari devkit.

     

    Hope this helps.


  3. I just tried it and I could compile it after a few changes. However the gcc doesn't support dos.

    Which means using dosbox for linking and windows for compiling and at the same time keeping all library files in the project folder, which is kind of annoying at the moment.

     

    I hope we find a better way to do it, maybe support for the .a file could be added to sln? No idea how much effort it would take though.

     

    Also, keep in mind that dos only supports 8 symbols + 3 symbols extensions. in other words files like interrupt.o need to be renamed.

     

    IIRC you can run dosbox with a different .conf file. So, after typing "make" on windows, you can have a .conf file in your project directory that does the linking (i.e. call aln with the right params) and then exits dosbox. Then start dosbox using that config.

     

    Although CJ codes in pure asm using that principle, it's mostly the same thing.

     

    (another thing would be a .bat file that calls 'make' and then bring up dosbox with the pre-made config file).

     

     

    Hope this helps.


  4. Hi ggn!

     

    When I enter "make install" in the jlibc directory I get the following error message...

     

    [snippety snip]

     

    install: cannot stat `crt0.o': No such file or directory

    install: cannot stat `jlibc.a': No such file or directory[/b]

     

    Any ideas?

    Thanks, I really appreciate your input. :)

     

    Dunno if you're going to use cygwin at all but for what it's worth: if 'make install' can't find the files, it means they weren't compiled. Did you do a 'make' before 'make install'? Did it exit without errors? Also, did you modify Makefile.config?


  5. Hiya Lars,

     

    How can I test it?

     

    Easy - j ust open a Cygwin console and type "m68k-atari-mint-gcc --version". That should run the cross-gcc and print some generic infor about it.

     

    Hmm, I put the Jaguar folder into my home directory and also placed the example1 of the removers lib into the home directory.

    Installed the same Gcc as mentioned on the removers lib, just to be sure, as well.

     

    However when I type make in the example1 folder, I get error messages as if the jag c lib wasn't found.

    Now where exactly in the makefile does it say where the remover / jag c lib has to be located?

    I think if I get that right, things might work already.

     

    Umm, the way I understand it, Seb is offering the lib in source format. So you will have to compile that first before anything you write using it works. Get the archive, unpack it, edit the makefile(s) to point to your tools, and type make. If no errors occur, type 'make install' and the library should be installed in your cygwin system. Then, the example program should compile (perhaps with more makefile tinkering).

     

    I think we're making good progress though :)


  6. BUMP!

     

    :hug:s to Seb for this thread - you saved me a few days of total frustration and head scratching :) (plus having to use some pen and paper and write down the equations needed ;)). I now have my rotator up and running - some tables are generated offline, unlike your version. Also thanks to Zerosquare for bringing this thread to my attention!

     

    There's only one weird thing I haven't managed to solve yet. Seems that my routine is working perfectly on vjag and PT. But depending on the width and height of my bitmap, it may or may not work on the real Jaguar. It sounds like phrase alignment, but I'm not sure. Any ideas?


  7. Hello,

     

    Let's see now...

     

    - Did you check that the cross-68k tools work from the cygwin console?

    - Can you also run mac/smac from the console? It must be present in cygwin's PATH, which generally isn't the same as the system's. You might have to copy the executables to a directory that is on cygwin's path (typing "set|grep PATH" on console will help)

    - If both of the above work, then locate cygwin's home directory (can't remember by heart, it should be something like <path-to-cygwin>/home/administrator) and extract the remover's lib on a folder there (typically if you've copied the lib archive on the root, "tar -zxvf jlibc-0.5.6.tar.gz" will do the trick.

     

    Now, for editing the Makefile (sorry if you made all of the above, I just wasn't certain): Seems to me that you don't need to edit Makefile, but instead you need to edit Makefile.config. It seems to me that Seb has installed the whole Atari Jagdev kit to $HOME/Jaguar. If you don't need all this, you can just remove JAGPATH and edit the MADMAC entry to point to mac or smac. After that, edit CROSSPATH to the path where the cross-68k tools reside. If you don't know the path, I think something like "which m68k-atari-mint-gcc" or similar will help (I can't remember exactly how the cross-gcc filename is, Vincent should state that on his website).

     

    After all this is done, type "make" on the lib directory and it should compile. Of course, the most likely thing is that it won't, but if you get to that, you can give more info :)

     

     

     


  8. Hello,

     

    I had a quick look at it. Seems that in order to use it, you need a few components:

     

    a ) A unixoid enviroment (since you're using Window$ and all)

    b ) Madmac assembler

    c ) Cross-68k-gcc

     

    For ( a ) I'd go with cygwin (http://cygwin.org/), because of ( c ) :).

    For ( b ) I'd suggest going with smac, as the only way Reboot has managed to make mac work on new OSes is via DOSbox, which would increase complexity in your build scripts (again, maybe not so much). Beware though, there are still bugs creeping in smac.

    For ( c ) the sane choice is Vincent Riviere's gcc port for Cygwin (http://vincent.riviere.free.fr/soft/m68k-atari-mint/).

     

    I'd give it a go myself, but I have a MinGW installation, and it's not so straightforward getting gcc up'n'running in that. (actually I have a 2nd machine running Win7 and cygwin -not mine!- so if you get really stuck I might set it up there)

     

    After you set everything up, it should be a simple matter of editing the Makefile and Makefile.conf, bringing up a console, CDing to the relevant directory and typing 'make' ;). Hmm, yeah, another point worth mentioning is to use a text editor that can edit unix source files (iirc they're CR while DOS is CR/LF). Notepad++, Notepad2 or gvim are all up to the task.

     

    Good luck, and please share your experiences!


  9. No rush. I will check it out when he posts the source. I don't encrypt many JagCD's anymore, but would be willing to port it to Linux/OS X if people want. Course if you guys are handling that, even better.

     

    Hi there,

     

    I'll be updating the archive in a short while with the full source (most of it is not mine to keep anyway :)). Port it to linux/OSX? My version of the encrypter doesn't use anything machine specific, as long as jcp supports the -c switch, it all should work flawlessly...

     

    [EDIT]It's up


  10. We have just succesfully booted the first few CDs created using ULS. All your CD-Creation woes are now over.

     

    More info to follow shortly.

     

    Not bad for 2 coders who don't even own Toilets, eh? :)

     

    And, to follow up, the CD image generator seems rock solid and is only waiting for testing before release :)


  11. Hi,

     

    Just wanted to drop a quick note that after a furious 2 day thriller starring me and sh3, we managed to get it to work 100% :). To test it, we created an encrypted CD image using the key the skunkboard sent to the PC and it's working!

     

    I'll clean up the source code and release it asap!


  12. Another news : i have heard a little thing, Reboot (Jagware) will release a new game in few days !! Yes another game for our beloved 64 bit console !! What game ? I can't told anything about it, except that a 1 week game !! Just wait and see !!!!

     

    Yep, sorry we haven't posted anything about it yet, I guess we got sucked in so much that we forgot to tell anyone (as with Project One, we spent more time playing it than doing anything else ;) ).

     

    The game is practically ready, we only need to take care of 2 small matters and then we'll release it!


  13. Salut!

     

    Nice forum guys, and active as it seems!

     

     

    Some months back I acquired an Atari Jaguar devkit, which is essentially a jag with a (kid of) alpine board, a scsi card and a disk with software for the PC.

     

    Since then I haven't been able to use it, because I couldn't get hold of a PC with an ISA slot to use the built-in card. Well, I just got hold of such a beast ;). I will try to set it up soon enough, and I'll try to keep you updated on how that goes on this thread.

     

    Before I begin though, I thought I'd ask here too: Anyone got any info on this, more specifically, anyone knows/have software for a devkit for the Atari? I heard some stories that there was a suite of programs for the tt/falcon that used SCSI to talk to the Jag, which is more or less my case here. Anyone knows anything about this?

     

    Regards, George

×