18 May 2017, 21:16 | #1 |
Natteravn
Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,496
|
vbcc 0.9f released
Hightlights:
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. |
18 May 2017, 23:06 | #2 |
Defendit numerus
Join Date: Mar 2017
Location: Crossing the Rubicon
Age: 53
Posts: 4,468
|
Great news!
|
18 May 2017, 23:06 | #3 | |
Registered User
Join Date: Mar 2016
Location: Australia
Posts: 881
|
Quote:
Can't wait to try it out. Was the no commercial use on previous versions due to bundled libraries? |
|
18 May 2017, 23:32 | #4 |
Registered User
Join Date: Jun 2016
Location: Stoke-On-Trent, England
Posts: 450
|
That's really good news on the sponsorship.
Makes a nice change seeing so much development in the Amiga world. |
19 May 2017, 09:08 | #5 | |
electricky.
Join Date: Jun 2010
Location: out in the wild
Posts: 1,256
|
Quote:
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. Jens https://icomp.de/shop-icomp/en/33/it...sors-vbcc.html |
|
19 May 2017, 09:44 | #6 | |
Registered User
Join Date: Mar 2016
Location: Australia
Posts: 881
|
Quote:
Thanks to all involved. |
|
19 May 2017, 13:49 | #7 |
electricky.
Join Date: Jun 2010
Location: out in the wild
Posts: 1,256
|
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. Jens |
19 May 2017, 15:19 | #8 |
BoingBagged
Join Date: Aug 2007
Location: The South of nowhere
Age: 46
Posts: 2,358
|
Thank you.
|
19 May 2017, 21:19 | #9 | ||
Banned
Join Date: Jan 2010
Location: Kansas
Posts: 1,284
|
Quote:
Quote:
|
||
19 May 2017, 21:46 | #10 |
Returning fan!
Join Date: Jan 2011
Location: Montréal, QC, Canada
Posts: 1,434
|
Hi all!
Very nice news, thank you all for supporting VBCC! Cheers |
20 May 2017, 03:53 | #11 |
Registered User
Join Date: Aug 2007
Location: berlin/germany
Posts: 1,054
|
its a good news i guess. congrats!
|
21 May 2017, 18:53 | #12 |
Semi-Retired
Join Date: Mar 2012
Location: Leiden / The Netherlands
Posts: 1,993
|
I'm getting a
"warning 2064: "load" directive was replaced by an instruction with the same name" in one of my 68k sources. No idea what it means? |
21 May 2017, 20:50 | #13 |
Natteravn
Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,496
|
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. But I thought it would be fair to inform the user about it. |
24 May 2017, 12:02 | #14 |
Indie Game Dev
|
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?
Last edited by fstltna; 24 May 2017 at 13:43. |
24 May 2017, 14:26 | #15 | ||
Join Date: Jul 2008
Location: Sweden
Posts: 2,269
|
Quote:
Quote:
vc *.cto 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. |
||
24 May 2017, 14:45 | #16 | |
Indie Game Dev
|
Quote:
Thanks for any help! Marisa |
|
24 May 2017, 19:15 | #17 |
Natteravn
Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,496
|
Please specify your precise problem. All files can be compiled without any warning, except osx.c, which includes a Unix/POSIX header file sys/ioctl.h. Probably you have to adapt that for AmigaOS.
You can compile osx.c with -DWINDOWS, but then the linker is missing min, max and getch (see above). The source is not portable. Support code for AmigaOS is missing. |
01 October 2017, 23:10 | #18 |
Registered User
Join Date: Feb 2012
Location: #DrainTheSwamp
Posts: 4,545
|
so many vbcc posting, so i put that here:
#1) "//" is not recognized as a comment line, why is it so? Code:
$ vc -sc -sd -O2 Decimate.c -o Decimate.o error=0 >// error 0 in line 1 of "Decimate.c": declaration expected aborting... 1 error found! Code:
// $Id: decimate.cxx,v 1.5 1997/10/01 14:07:25 garland Exp $ #include ... want link some object files, some made with gcc, others from sas/c, using vlink: Code:
INTERNAL ERROR: aout_symbols(): Symbol ___CTOR_LIST__ in Matrix.o has type 22, which is currently not supported. Aborting. make: *** [Makefile:23: qemloss.p] Error 1 Last edited by emufan; 01 October 2017 at 23:16. |
01 October 2017, 23:21 | #19 | |
Banned
Join Date: Sep 2016
Location: UK
Posts: 2,917
|
Quote:
From the vbcc manual -c99 Switch to the 1999 ISO standard for C /ISO/IEC9899:1999). Currently the following changes of C99 are handled: − long long int (not supported by all backends) − flexible array members as last element of a struct − mixed statements and declarations − declarations within for-loops − inline function-specifier − restrict-qualifier − new reserved keywords − //-comments − vararg-macros − _Pragma − implicit int deprecated − implicit function-declarations deprecated − increased translation-limits − designated initializers − non-constant initializers for automatic aggregates − compound literals − variable-length arrays (incomplete) |
|
01 October 2017, 23:23 | #20 | |
Registered User
Join Date: Feb 2012
Location: #DrainTheSwamp
Posts: 4,545
|
Quote:
#1) some patch for next vbcc version: Code:
if user uses "//" and option !=c99 printf ("looks like a comment --> use -c99 command line option\n"); endif Last edited by emufan; 01 October 2017 at 23:30. |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
vbcc IDE | iliak | Coders. C/C++ | 23 | 23 April 2019 17:27 |
vbcc V0.9e released | phx | News | 17 | 31 October 2016 21:18 |
vbcc 0.9d | phx | News | 43 | 13 July 2015 19:41 |
From gcc to vbcc. | Cowcat | Coders. General | 9 | 06 June 2014 14:45 |
Compiler: vbcc 0.8g patch 2 released | Paul | News | 0 | 29 November 2004 15:41 |
|
|