Browsing this Thread:
1 Anonymous Users
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Quite a regular
![]() |
I’m currently building AROS from source. For what it’s worth, <tt>configure</tt> fails to detect if <tt>wget</tt> is missing, so the build process broke down pretty quickly. Right now it’s running happily, though.
Out of curiosity, why on earth does AROS need gmp?
Posted on: 2018/4/7 21:56
|
|||
|
||||
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Quote:
No. You will need to check out the AROS code and build your own crosscompiler to use, or just so it within the build system. Quote:
I can?t predict the future but it isn?t/wasn?t the intention - the ABI v1 stuff is hopefully a one-off change out of necessity. Quote:
Yes. As I?ve mentioned, ABI v1 was changed to no longer use the wrapper in favour of build real cross compilers to use (so everyone is working off the same page ... and should be able to get the same results as e.g nightly build servers) so that we can use c++ properly within the build system. Most of the mmakefile.src macros will take c++ source files as input, and a lot of work has been done fixing the AROS headers to work in c++ code. There is still much to do but atleast doom3, odyssey, Mesa etc all compile using it.
Posted on: 2018/4/6 22:53
|
|||
|
||||
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Quite a regular
![]() |
Quote:
No, I downloaded the binaries, unzipped them into the directory I wanted, and I run from there. That’s what the website suggests. Quote: if you have had built it yourself you could use the cross compilers, which are in crosstools, say, dependent on actual architecture somewhere like: Are these files in the AROS download, or something I install on Fedora? I know gcc includes some cross-compiling options but I don’t think that’s what you mean here; I get the impression you mean something that comes with the AROS source download, as you write a moment later: Quote: downloading nightly the aros native gnu tools will be in contrib image: contrib/Developer/bin Quote: but as of current i noticed that on x86 abi v1 some of the executables are of size zero. not knowing if you are on abi v1 or v2… Wait. There’s an ABI v2?!?!? Let me put it thus: I would like to write programs for AROS, perhaps even contribute to things such as fixing a pointer issue I’ve encountered (which I suspect is easy to fix). I don’t really care much about the ABI, as I would be happy to work with open source. I would prefer to use C++, however, and I’d prefer to use a modern C++. I don’t have to, and obviously if I want to contribute to the system I imagine I’d be restricted to C, but I find C++11 is a much, much more flexible and reliable language than C, so I’d like to use it if I can. Do I have to download the sources to do that and compile AROS from scratch? Would that make it work?
Posted on: 2018/4/6 21:44
|
|||
|
||||
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Quite a regular
![]() |
Quote:
Ah. That probably explains it. You say “for <i>simple</i> c stuff.” Complicated C stuff doesn’t work, either?
Posted on: 2018/4/6 21:38
|
|||
|
||||
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Quote:
The ABi v1 sdk isn?t really in a usable state. The wrapper works for simple c stuff but not c++. Quote:
Posted on: 2018/4/6 15:59
|
|||
|
||||
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
talking of hosted you probably simply downloaded the iso?
if you have had built it yourself you could use the cross compilers, which are in crosstools, say, dependent on actual architecture somewhere like: your dir/bin/linux-(your arch)/tools/crosstools it would be something like (your arch)-aros-gcc, c++, cpp or the like respectively. downloading nightly the aros native gnu tools will be in contrib image: contrib/Developer/bin but as of current i noticed that on x86 abi v1 some of the executables are of size zero. not knowing if you are on abi v1 or v2 you must check for yourself if you have got a working one. for certain though, you cant compile your aros programs with your generic host compiler, even on the same arch.
Posted on: 2018/4/6 13:49
|
|||
|
||||
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Quite a regular
![]() |
Quote:
I just ran the SDK's installer script. GCC 7.x is what Fedora includes. If you want I?ll copy one of the resulting files here so you can see what it produced. Quote: When im working on stuff for AROS, I do it inside the source tree (just add a "local" dir or something) and use the mmakefile.src's the build system uses. I?m not sure why that should help but I?'ll try it. I didn?t use a makefile; I just ran <pre style="margin-left:10%;margin-right:10%;"><tt> g++ -o hello_cxx hello.cxx </tt></pre> The parallel to doing this in C worked fine so I thought, perhaps foolishly, it should work in C++, too. Quote: AROS builds a lot of c++ stuff with no issue - so I suspect its something on your end thats wrong. Oh, I do, too, after I investigated further. At first I had thought otherwise (& I admit I said so above) but not after.
Posted on: 2018/4/6 13:12
|
|||
|
||||
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
i too recommend to build within aros source tree exactly like kalamatee said. the makefile format may be a bit odd, but you will find a lot of reference around the source. you can still maintain a normal makefile for other targets within your source. you might want to use scripts/macros for building stuff you will find them described and implemented in config/make.templ. this way you might even be able to port gnu tools and libs with minimal effort. also a lot of stuff like paths and default tools are abstracted so, if something changes chances are that it doesnt break.
Posted on: 2018/4/6 11:28
|
|||
|
||||
|
Re: a more modern gcc?
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Quote:
When im working on stuff for AROS, I do it inside the source tree (just add a "local" dir or something) and use the mmakefile.src's the build system uses. It just makes it easier in the long run, especialy when it comes to importing it or building it for other targets to test (different compiler/toolchain configs, different AROS targets, debug, etc) AROS builds a lot of c++ stuff with no issue - so I suspect its something on your end thats wrong. It might sound a bit tedious to do it the way I have said but once you get used to it, developing stuff for AROS becomes a lot easier.
Posted on: 2018/4/6 2:43
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.








At first I had thought otherwise (& I admit I said so above) but not after.