VBCC

[derek2210]

Hi,

I have been reading about VBCC and it seems to have Amiga targets, can AROS run VBCC, and maybe natively.

[magorium]

I can't think of anything why it would not be possible.

The Free Pascal compiler makes use (or actually /can/ make use) of VBCC's linker and assembler. Have you tried to compile VBCC on AROS ? (I haven't done so either though)

[Mazze]

Problem is that our header files are full of GCC and AROS specific features. The compiler itself is already in contrib:

https://github.com/aros-development-team/contrib/tree/master/development/compilers/vbcc

[derek2210]

Hi,

I have not tried to compile VBCC on AROS, I was just asking if it had already been done.

I will have a look at this, as I would like a native AROS compiler, rather than Cross Compiler system.

[magorium]

@Mazze: thankl you for that as I did not know (even though I do have contrib installed)

@Derek:
Are you aware that there is a native gcc compiler present for AROS. At least Icaros desktop comes with it (when you choose to install the development package) ?

In other cases/distributions you can install GCC from contrib (in case the distro does not contain/supply gcc by default)

[AMIGASYSTEM]

magorium also on AROS One x86 and AROS One 68k the GCC is installed and works fine, of course during installation as you mentioned, you have to check development package !
Not only on AROS One x86 the Portable Compiler and other development software is also installed !

[derek2210]

Hi,

Thanks for the update, looks like I have not looked at the system currently installed.

I have more experience with GCC on Linux, so maybe I do not have re-invent the wheel. Back to reading the developer docs...

[AMIGASYSTEM]

No need to look at the system, just write GCC in a Shell 

[magorium]

@AMIGASYSTEM: Thank you for the (additional) information.

@Derek:
there is also a Linux compatible shell (with basic set of internal and external commands) that can be invoked/used with sh so you should be able to "feel" right at home 

[cdimauro]

Problem is that our header files are full of GCC and AROS specific features.

I can understand using AROS features (it should compile AROS code!), but... why using specific GCC features? This means strictly biding AROS to GCC and making the life much difficult (or even impossible) for people which want to use other compilers (like CLang, for example. And also VBCC).