LIBS versions and updates`

[nicholas]

My friend, as someone who has been known to spend hours researching the most up-to-date Libs versions (it's part of my OCD), allow me to introduce you to this site:

http://amiga.foul.fr/index.php?p=Work%2FLibs

Also this list was helpful when I was first getting started.

You can get partial version info from SysInfo, however speaking from experience, the C:Version FULL command is going to be your new best friend.

I run modified libraries from THoR, Cosmos, and Peter K., among others, and definitely recommend them (am sure someone will chime in here about "blah blah unstable, blah-blah not Commodore original, etc." however they work fine for me... your mileage may vary ).

Also if you would like to compare version numbers of specific libraries, I am down for that game any day.  

Mike you are my brother from another mother!

[nicholas]

I started writing a replacement for C:Copy that compares version strings of any file you copy with it but it's sat there 60% finished for a couple of years due to various real life issues taking up all my time.

Might try and finish it off at some point soon.

[nicholas]

Great idea.  Is this being done in C?

Thanks, I started it because of a personal need for it when to my surprise it didn't already exist on Aminet.  Yes it's written in C, the first prototype version I did was written on MorphOS and compiled with gcc4 but I rewrote it using old-fashioned style C so that it compiles with SAS/C for 68k too.

[nicholas]

That would be great!  I'm sure a few of us here would use such a tool.  

That helps with motivation, I'll try make some time over the weekend to start up work on it again.

[nicholas]

Most recent version I could find last night is from August 28th 2013 and isn't SAS/C compilable so I must have a newer version backed up somewhere.

If I can't find anything newer at the weekend I'll use this version to carry on working with.

[nicholas]

Not to derail this thread too much, and forgive the amateur programmer question... but I seem to remember the last C compiler coming out for the Amiga as Storm C and if my memory serves SAS/C was the defacto when Amiga first began.  Is there any consideration beyond personal preference when it comes to which C environment/compiler you use when writing a piece of software in C for the 68k Amiga now-a-days?

Short answer: OCD.

StormC is an IDE that uses GCC for compiling code. I like to compile it with SAS/C as it arguably creates tighter/faster binaries than GCC but also because it keeps it old school

VBCC is probably the best 68k compiler though.