Closed TheJJ closed 7 years ago
Hi... may I try to update this documentation? I'll probably need to discuss a little bit on how to perform some of the changes.
Thanks
Sure, go ahead!
As --cpp-compiler
parameter no longer exists on ./configure
, it seems that the hardcoded versions of compiler will not be an issue anymore: they only seem to be "wrongly" used altogether with --cpp-compiler
, am I right?
Any prefered pattern to split specific os/distro build instructions on their own files? I was thinking of creating them this way on the same current path: building_<specific-distro-or-os-name>.md
. The Idea is to provide links to them on building.md
.
Any comment on such ideas would be nice!
Thanks,
The new --compiler
flag is used to specify a custom compiler type/version easily. Namely, you can select clang
instead of gcc
that way. I think you can safely remove the hardcoded versions, yes.
If you wanna split it up, yes, great idea :)
I'd create a new directory build_instructions/
or similar and then create files like ubuntu.md
, gentoo.md
and so on in there.
The building.md
can then link to them like you suggested.
Thanks for your comments, @TheJJ! I'll pick your suggestions.
https://github.com/SFTtech/openage/blob/master/doc/building.md#build-procedure
./configure
script no longer accepts--cpp-compiler