New target for Kickstart 1.x programs, using the original Commodore 1.3 headers.

New target for Atari Jaguar consoles.

Many bug fixes and enhancements.

We are happy to announce that iComp GmbH (www.icomp.de) has decided to sponsor the 68k-AmigaOS version of vbcc. This does not only help us to continue supporting and improving this port but it also allows us to relax the terms of use for the Amiga-68k community. Everyone may now freely use vbcc to develop 68k-AmigaOS code for commercial as well as non-commercial usage (for details please refer to the license in the documentation).

We thank iComp GmbH for the confidence in vbcc and hope that this step will help in the creation of new software for the Amiga-68k.

New target for Kickstart 1.x programs, using the original Commodore 1.3 headers.

New target for Atari Jaguar consoles.

Many bug fixes and enhancements.

We are happy to announce that iComp GmbH (www.icomp.de) has decided to sponsor the 68k-AmigaOS version of vbcc. This does not only help us to continue supporting and improving this port but it also allows us to relax the terms of use for the Amiga-68k community. Everyone may now freely use vbcc to develop 68k-AmigaOS code for commercial as well as non-commercial usage (for details please refer to the license in the documentation).

We thank iComp GmbH for the confidence in vbcc and hope that this step will help in the creation of new software for the Amiga-68k.

Congratulations!

Can't wait to try it out.

Was the no commercial use on previous versions due to bundled libraries?

Was the no commercial use on previous versions due to bundled libraries?

Previous releases had an unclear license, and nobody really thought of commercial environments.

I've been looking for development tools for quite some time, as I wanted to support as many people as possible by making the first steps in development as easy as possible. While I've found a few Pascal dialects, pretty much everyone convinced me that C is the way to go. I've tried to free the SAS/C compiler for the Amiga, but did not get the required answers.

One of my employees confirmed that vbcc produces very good code quality, and Volker was so kind to accept my offer for a sponsorship of the m68k-AmigaOS port.

Please don't get me wrong on the priorities: The only reason why I've tried to free SAS/C in the first place was that I wasn't aware of the high code quality that vbcc produces. So for any new project - commercial or not - vbcc is the way to go now.

Previous releases had an unclear license, and nobody really thought of commercial environments.

I've been looking for development tools for quite some time, as I wanted to support as many people as possible by making the first steps in development as easy as possible. While I've found a few Pascal dialects, pretty much everyone convinced me that C is the way to go. I've tried to free the SAS/C compiler for the Amiga, but did not get the required answers.

One of my employees confirmed that vbcc produces very good code quality, and Volker was so kind to accept my offer for a sponsorship of the m68k-AmigaOS port.

Please don't get me wrong on the priorities: The only reason why I've tried to free SAS/C in the first place was that I wasn't aware of the high code quality that vbcc produces. So for any new project - commercial or not - vbcc is the way to go now.

Sorry if that was not clear - I use "vbcc" as a synonym for the whole package of vbcc, vasm, vlink and PosixLib, as this is what we've been discussing via eMail since april 2017. Note that PosixLib didn't even have any license file previously, and is now clearly under a BSD license.

vasm has several modules that also have the new exception for commercial use for m68k-AmigaOS: Motorola-Syntax module, M68k CPU module and the Hunk format output module.

I've been looking for development tools for quite some time, as I wanted to support as many people as possible by making the first steps in development as easy as possible. While I've found a few Pascal dialects, pretty much everyone convinced me that C is the way to go. I've tried to free the SAS/C compiler for the Amiga, but did not get the required answers.

C has been the default language of the Amiga. It was the efficiency of C which allowed the AmigaOS to become as good as it was back in the day. SAS/C's professional support of the Amiga was important as well. Vbcc has the potential to become the next SAS/C for the Amiga and your kind support could help make it happen. I am impressed at your recognition of the importance of improving Amiga compilers.

Quote:

Originally Posted by Schoenfeld

One of my employees confirmed that vbcc produces very good code quality, and Volker was so kind to accept my offer for a sponsorship of the m68k-AmigaOS port.

Please don't get me wrong on the priorities: The only reason why I've tried to free SAS/C in the first place was that I wasn't aware of the high code quality that vbcc produces. So for any new project - commercial or not - vbcc is the way to go now.

I wouldn't say the vbcc code generation quality is that great yet but sponsoring it and making it a priority should help the situation. SAS/C code generation was average and I think vbcc has the potential to do much better if Dr. Volker Barthelmann is encouraged to give a little TLC to the 68k backend .

You have enabled code generation for the 68080 (Apollo Core)? It defines a new instruction LOAD for loading a vector register.

But there is also a LOAD directive for compatibility with old PhxAss, AsmOne, Seka sources, which has no effect in vasm anyway (vasm will never output code directly into memory), so it is safe to ignore it.

Any examples of using this to compile regular C code? I am trying to compile a 5 .c file and 2 .h file console app... Just plain c, not amiga specific. Tried crosscompiling on ubuntu but get a missing file error. Would love to get it going on amigaos native! Can someone point me in the right direction?

New target for Kickstart 1.x programs, using the original Commodore 1.3 headers.

New target for Atari Jaguar consoles.

Many bug fixes and enhancements.

Thanks a lot for the update.

Quote:

Originally Posted by fstltna

Any examples of using this to compile regular C code? I am trying to compile a 5 .c file and 2 .h file console app... Just plain c, not amiga specific. Tried crosscompiling on ubuntu but get a missing file error. Would love to get it going on amigaos native! Can someone point me in the right direction?

What program is it, do you have an URL to it? If it's just plain C with no specific requirements, then you should only have to run

vc *.c

to compile it. It could be an installation problem, have a look in the user manual to see how to install the tools and the m68k-amiga targets correctly.