Hi,
While I know it has not been explicitly discouraged, is there some reason crosstool-ng is not recommended for building a cross-compiler? The web site is: http://crosstool-ng.github.io/
crosstool-ng
- eryjus
- Member
- Posts: 286
- Joined: Fri Oct 21, 2011 9:47 pm
- Libera.chat IRC: eryjus
- Location: Tustin, CA USA
crosstool-ng
Adam
The name is fitting: Century Hobby OS -- At this rate, it's gonna take me that long!
Read about my mistakes and missteps with this iteration: Journal
"Sometimes things just don't make sense until you figure them out." -- Phil Stahlheber
The name is fitting: Century Hobby OS -- At this rate, it's gonna take me that long!
Read about my mistakes and missteps with this iteration: Journal
"Sometimes things just don't make sense until you figure them out." -- Phil Stahlheber
- dchapiesky
- Member
- Posts: 204
- Joined: Sun Dec 25, 2016 1:54 am
- Libera.chat IRC: dchapiesky
Re: crosstool-ng
my experience has been that I have specific work flow requirements for the order in which I build the cross compilers and libraries. When I tried to integrate crosstool-ng it just became a pain trying to get my requirements met... literally was easier to just use cmake.
others will probably disagree but there you have it.
others will probably disagree but there you have it.
Plagiarize. Plagiarize. Let not one line escape thine eyes...
Re: crosstool-ng
Well, the instructions in the OSDev Wiki predate crosstool-ng (v0.0.1 released Apr 10, 2007) by a comfortable margin, and are known to work.eryjus wrote:While I know it has not been explicitly discouraged, is there some reason crosstool-ng is not recommended for building a cross-compiler?
Every good solution is obvious once you've found it.
Re: crosstool-ng
I think it is an excellent toolchain and Ive used it to compile my os for a long time.
Fudge - Simplicity, clarity and speed.
http://github.com/Jezze/fudge/
http://github.com/Jezze/fudge/
Re: crosstool-ng
Not as long as I have been using the wiki instructions.
The other point is, while it would be OK to mention crosstool-ng in the Wiki, or even write an introduction on its use, replacing the existing instructions with those for a third-party tool would be suboptimal IMHO. It would mean that we would have to handle any issues encountered with present and future versions of crosstool-ng here in the forum. By not relying on crosstool-ng, we only have to handle problems with the cross-building process itself, and the occassional "why do I need a crosscompiler in the first place" question. I also think that the current way is more... instructive (no pun intended) as to what's really going on.
I don't say that these are "killer arguments", just that there are benefits to describing the "manual" path.
The other point is, while it would be OK to mention crosstool-ng in the Wiki, or even write an introduction on its use, replacing the existing instructions with those for a third-party tool would be suboptimal IMHO. It would mean that we would have to handle any issues encountered with present and future versions of crosstool-ng here in the forum. By not relying on crosstool-ng, we only have to handle problems with the cross-building process itself, and the occassional "why do I need a crosscompiler in the first place" question. I also think that the current way is more... instructive (no pun intended) as to what's really going on.
I don't say that these are "killer arguments", just that there are benefits to describing the "manual" path.
Every good solution is obvious once you've found it.
Re: crosstool-ng
I'm pretty sure that if you're able to undestand and execute manual instructions in the wiki you will be qualified to check and even perhaps fix any crosstool-ng issues.
The opposite is not true.
The opposite is not true.
Learn to read.
- eryjus
- Member
- Posts: 286
- Joined: Fri Oct 21, 2011 9:47 pm
- Libera.chat IRC: eryjus
- Location: Tustin, CA USA
Re: crosstool-ng
I never intended to suggest that.Solar wrote:replacing the existing instructions with those for a third-party tool would be suboptimal
I can also see the value of the "weed-out" instructions. That answer is good enough for me for why not to mention it.Solar wrote:I also think that the current way is more... instructive (no pun intended) as to what's really going on.
Adam
The name is fitting: Century Hobby OS -- At this rate, it's gonna take me that long!
Read about my mistakes and missteps with this iteration: Journal
"Sometimes things just don't make sense until you figure them out." -- Phil Stahlheber
The name is fitting: Century Hobby OS -- At this rate, it's gonna take me that long!
Read about my mistakes and missteps with this iteration: Journal
"Sometimes things just don't make sense until you figure them out." -- Phil Stahlheber