From: Maróy Á. <ak...@ma...> - 2009-07-29 06:56:33
|
Hi, As I've been playing along with cross-compilation issues for some time, and have found no single location for this kind of information, I decided to open a wiki to collect such information into one place. See the very initial form of this here: http://cross-compile.info/ Of course, the MinGW cross compiler building process is documented here: http://www.mingw.org/wiki/LinuxCrossMinGW but it might still make sense to collect a range of cross-compilation info at a single location. My hope is that this wiki will contain a range of information that is related to cross-compilation. I'd really appreciate anyone interested would consider contributing as well. Therefore I welcome all of you interested to register at the wiki, and extend the pages as you see fit. I'd be also glad to give interseted parties write access to the subversion repository I created, so as the collect files in relation to cross-compiling at a single location. And of course, all feedback is welcome! Akos |
From: Danny B. <dan...@sc...> - 2009-07-29 07:48:32
|
On Wed, 2009-07-29 at 08:56 +0200, Maróy Ákos wrote: > As I've been playing along with cross-compilation issues for some time, > and have found no single location for this kind of information, I > decided to open a wiki to collect such information into one place. > > See the very initial form of this here: http://cross-compile.info/ [..] > And of course, all feedback is welcome! You can pick up a thing or two at http://cegcc.sourceforge.net . Danny -- Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info |
From: Keith M. <kei...@us...> - 2009-07-29 18:09:12
|
On Wednesday 29 July 2009 07:56:16 Maróy Ákos wrote: > As I've been playing along with cross-compilation issues for some > time, and have found no single location for this kind of > information, I decided to open a wiki to collect such information > into one place. > > See the very initial form of this here: http://cross-compile.info/ I don't really have the time to participate in maintaining this, but I did have a quick peek. One thing I did notice immediately is that you seem to have fallen into the common trap of confusing the build, host and target terminology, as it is commonly accepted: build is the platform/architecture on which your cross tools run; (you have incorrectly described this as "host"). host is the platform/architecture on which the applications you build, using your cross tools, will run; (you have incorrectly described this as "target"). target is the platform/architecture for which the applications you build, using your cross tools, will generate code; (note that this implies that you are using your cross tools to build another compiler, or other form of code generator -- it is meaningless in any other context). -- Regards, Keith. |
From: Tor L. <tm...@ik...> - 2009-07-30 08:01:07
|
> but it might still make sense to collect a range of cross-compilation > info at a single location. I wonder if you are aware how large the scope of cross-compilation actually is? The case of cross-compiling from Linux (and other Unixes) to Windows using gcc is a very small part of it. All the code that runs in machines one interacts with every day, from toasters to phone exchanges, is cross-compiled, very often using proprietary toolkits (although gcc and the GNU toolchain is becoming more popular, I am sure, as part of commercial toolkits targeted at proprietary embedded OSes), very often from Windows, not from Linux. --tml |
From: Tor L. <tm...@ik...> - 2009-07-30 08:59:25
|
> that's even more of reason to collect such vast amount of documentation > into a single place! Good luck in convincing proprietary cross-tool companies to donate their documentation to this wiki... Or do you mean 3rd-party documentation for proprietary cross development toolchains? Does such exist? Who would have created it? Would a company that spends $$$ on licenses for some proprietary toolchain and yearly support, and where people then write in-house documentation to complement the vendor's documentation, be willing to make such documentation public (and useful to their competitors!)? Such in-house documentation presumably contains trade secrets, details specific to the company's environment and the products that the company builds using the toolchain in question. Or do you mean information written by people using illegal copies of proprietary cross-development toolchains, who perhaps have no written documentation and for obvious reasons can't use the toolchain vendor's official support channels, forums, etc? Note: I am not saying that the wiki could not be useful, for the specific case of cross development using the GNU toolchain, by the Open Source community. I am just nitpicking on its (unintendedly?) vast scope... Maybe just some clarification and restriction of scope on the front page is in order... --tml |
From: Maróy Á. <ak...@ma...> - 2009-07-30 11:31:05
|
Tor, > Good luck in convincing proprietary cross-tool companies to donate > their documentation to this wiki... well, I don't want to convince anyone - it's just an opportunity, that one might take. nor am I assuming that people would use illegal copies of any kind of software. software licenses should be honored - be that closed or open source licenses. OTOH, to respond to your specific topic, it might be beneficial for closed source / commercial tool users as well to share information online. the information itself does not have to be closed, even if the tool itself is not available for free (as in beer). I don't see any contradiction in that. also note that the CC-by-sa license on the page means that the contents of the page can be used in commercial environments. > Note: I am not saying that the wiki could not be useful, for the > specific case of cross development using the GNU toolchain, by the > Open Source community. I am just nitpicking on its (unintendedly?) > vast scope... Maybe just some clarification and restriction of scope > on the front page is in order... how does the wide scope confuse you? can you be more specific about this confusion? Akos |
From: Maróy Á. <ak...@ma...> - 2009-07-30 08:29:34
|
Tor, > I wonder if you are aware how large the scope of cross-compilation > actually is? The case of cross-compiling from Linux (and other Unixes) > to Windows using gcc is a very small part of it. > > All the code that runs in machines one interacts with every day, from > toasters to phone exchanges, is cross-compiled, very often using > proprietary toolkits (although gcc and the GNU toolchain is becoming > more popular, I am sure, as part of commercial toolkits targeted at > proprietary embedded OSes), very often from Windows, not from Linux. that's even more of reason to collect such vast amount of documentation into a single place! Akos |