How to access the C compiler?

[Geri]

hello, how i can access the gcc in aros?

[Geri]

okay, i have to install it first.

is there any way to report bugs, as i already found like 10

[Mazze]

https://sourceforge.net/p/aros/bugs/

[Geri]

thankyou

i was able to succesfully port my software to aros within a few hours



but i have scrapped the result, and decided not to release it.

here are the reasons why:

1. the gcc used in aros inserts every debug information (such as variable and function names) to the binary, and it canot be stripped. if someone disassembles it, essencially gets your source code.

2. no proper documentation. i was not even able to find an api call to get the number of cpu core count within 10 minutes of googling.

3. due to the second point i will not spend my next 2 weeks to figure out how to create a new window, how to interface the keyboard or how to initialize the sound card...

4. to counter to the 2th and 3th points, there is SDL. however, in aros, SDL1 was used, which is lgpl, therefore it is ILLEGAL to statically link it to a non-opensource software. SDL2 would be fine, but thats not available under aros.

5. no smp. smp was annouced a year ago or so, in theory it should work. but no, it does not works. also, no sound (ac97) so i cant test if my program even have sound.

if the new sdl2 will get released into aros then i can release at least a beta version but nothing until then

[trekiej]

Good luck, I believe someone will help you.

[BSzili]

1. the gcc used in aros inserts every debug information (such as variable and function names) to the binary, and it canot be stripped. if someone disassembles it, essencially gets your source code.

Use the --strip-unneeded switch, which will only keep the symbols necessary for relocation.

2. no proper documentation. i was not even able to find an api call to get the number of cpu core count within 10 minutes of googling.

The "mainstream" ABIv0 version of AROS only supports 1 CPU core. You won't find documentation for non-existent APIs.

3. due to the second point i will not spend my next 2 weeks to figure out how to create a new window, how to interface the keyboard or how to initialize the sound card...

Strange, because these are all very well documented, and even if they weren't he Amiga documentations could be used, since the two are API compatible.

4. to counter to the 2th and 3th points, there is SDL. however, in aros, SDL1 was used, which is lgpl, therefore it is ILLEGAL to statically link it to a non-opensource software. SDL2 would be fine, but thats not available under aros.

IANAL

5. no smp. smp was annouced a year ago or so, in theory it should work. but no, it does not works. also, no sound (ac97) so i cant test if my program even have sound.

What does announcing something has to do whether it was completed or not? AROS is developed by people as a hobby. Looking at that screenshot I can't imagine why couldn't it run on a single core. Sound card support is a different issue, you can end up with unsupported hardware.

if the new sdl2 will get released into aros then i can release at least a beta version but nothing until then

See ya later then.

[Geri]

BSzili thanks, i will try the  --strip-unneeded switch, maybe it can help. it CAN work in single core mode, but this is software rendering and its optimized to run on 2 threads, it would be so soft and fluid on 2 core.   lack of sound is happened with virtualbox (i did the whole process in virtualbox) and virtualbox does  a regular ac97 so its strange it had no sound. this is some kernel or driver glitch because if i wanted to test the built-in music tracker software to find out if there is actually any sound, the whole kernel froze.

[magorium]

1. the gcc used in aros inserts every debug information (such as variable and function names) to the binary, and it canot be stripped. if someone disassembles it, essencially gets your source code.

answered by BSzili

2. no proper documentation. i was not even able to find an api call to get the number of cpu core count within 10 minutes of googling.

sjees.... how hard can it be ? 

www.aros.org then press reference (http://www.aros.org/documentation/developers/autodocs/index.php) . the api you are after can be read here http://www.aros.org/documentation/developers/autodocs/processor.php

3. due to the second point i will not spend my next 2 weeks to figure out how to create a new window, how to interface the keyboard or how to initialize the sound card...

AROS is API compatible with amiga OS.... what more do you want exactly ? You want to create an intuition window ? MUI window ? BGui window ? i have fpGUI and LCL for you as well (but that is a complete other programming language to begin with)

5. no smp. smp was annouced a year ago or so, in theory it should work. but no, it does not works. also, no sound (ac97) so i cant test if my program even have sound.

Yes... SMP has been there for what ? 10 years now ... it is located in trunk (64-bit) and not available for the common distributions. It is available for raspberry (again trunk) as well if not mistaken.

Sound works in virtual box provided that you have set it up correctly. And by that mean both the vbox and aros side of things. There is a manual... nobody bothers to read it though 

ps: oh and i see that you are not using the bash compatible shell to compile your stuff in ? again, can be read in the manual... nobody bothers to read it though 

[paolone]

BSzili thanks, i will try the  --strip-unneeded switch, maybe it can help. it CAN work in single core mode, but this is software rendering and its optimized to run on 2 threads, it would be so soft and fluid on 2 core.   lack of sound is happened with virtualbox (i did the whole process in virtualbox) and virtualbox does  a regular ac97 so its strange it had no sound. this is some kernel or driver glitch because if i wanted to test the built-in music tracker software to find out if there is actually any sound, the whole kernel froze.

Some considerations
1. VirtualBOX is the toy for people who don't want to get serious into virtualisation. Please act as an adult and user vmware player instead ;-)

2. software rendering for 3D apps might be fine, but MESA is available and definitely better on supported hardware
3. audio correctly works on supported ESS, AC97, HDAudiuo and Emu10K cards (and also on vmware). VirtualBOX is broken somewhere, but (vbox) users acceptance degree of the issue is "gneeeeh gneeeeeh VirtualBOX is good, it's your AROS problem" (experimented on my own skin).

[magorium]

1. VirtualBOX is the toy for people who don't want to get serious into virtualisation. Please act as an adult and user vmware player instead ;-)

Strange how vmware player isn't able to recognize that my processor has virtual extensions and refuses to use them.... i guess my bad for not reading the vmware manual 

Oh and you guess is right therefor vmware runs like shite on my core2duo.

3. audio correctly works on supported ESS, AC97, HDAudiuo and Emu10K cards (and also on vmware). VirtualBOX is broken somewhere, but (vbox) users acceptance degree of the issue is "gneeeeh gneeeeeh VirtualBOX is good, it's your AROS problem" (experimented on my own skin).

Sounds works perfectly on the 4.x series of vbox.

Oh, and i give you credit for bashing vbox. they have a tendency to break things that aren't broken. fix them and then break them again (to then fix them again). Repeat the cycle until complaining in the forums about that particular issue stops and then the issue in the bugtracker is solved because nobody complains about it anymore 

... a tactic that maybe can be used for AROS ? *ducks*

[paolone]

1. VirtualBOX is the toy for people who don't want to get serious into virtualisation. Please act as an adult and user vmware player instead ;-)

Strange how vmware player isn't able to recognize that my processor has virtual extensions and refuses to use them.... i guess my bad for not reading the vmware manual 

Oh and you guess is right therefor vmware runs like shite on my core2duo.

VMware player isn't able to recognize your processor's VT-extension probably because, on most default BIOS configurations, they are disabled. Please be sure your motherboard has VT-d and VT-x (or any other extension by AMD or Intel) enabled in the BIOS.

Core2Duo class of processors are not supported anymore by VMware. Please stick to Player version 12 because later releases need a Nehalem class CPU or a more recent one. Please have a look here:
https://docs.vmware.com/en/VMware-Workstation-Pro/14/rn/workstation-14-release-notes.html#System


(so yes, basically you didn't read the manual )

Oh, and i give you credit for bashing vbox. they have a tendency to break things that aren't broken. fix them and then break them again (to then fix them again). Repeat the cycle until complaining in the forums about that particular issue stops and then the issue in the bugtracker is solved because nobody complains about it anymore 

... a tactic that maybe can be used for AROS ? *ducks*

Sigh.