On Wed, Nov 5, 2014 at 5:08 PM, Carlos Antunes <[email protected]> wrote: > Whoops! My reply didn't go to the list initially... > > On 11/5/2014 11:04 AM, Ray Donnelly wrote: >> >> mingw-w64-{i686,x86_64}-toolchain wouldn't be appropriate >> > > Agreed! > >> >> ${MINGW_PACKAGE_PREFIX}-arm-linux-gnu-toolchain would be a good (if >> very long) package name, maybe we could shorten -toolchain to -tc (or >> -xtc if you really like cross to be in there somewhere?) >> > > I'm building "arm-none-eabi" so I guess we could settle on > "${MINGW_PACKAGE_PREFIX}-arm-none-eabi-toolchain"? The abreviations are > not immediately clear and, to the casual user, I'd say clarity is important. > > The names of the packages are currently > "${MINGW_PACKAGE_PREFIX}-{binutils,newlib,gcc}-arm-none-eabi". Is this > OK with you? > > I'll do a pull request for binutils once we agree on package naming > convention and you can then tell me if you'd like something changed. >
I wonder if we shouldn't just combine everything together into one otherwise I forsee a lot of packages. The other option is to wait until clang/llvm can be used for everything everywhere, then we need just one cross compiler (yeah I joke for now, but that is their eventual aim .. then again, I'm a fan of GNU too) >> >> I'm more interested in how you're planning to build them. I'm somewhat >> involved in crosstool-ng, and was planning to add a load of cross >> compilers to MSYS2/MinGW-w64 packages when MSYS2 itself is working >> well enough .. This would include cross compilers targeting Linux (arm >> and intel) and Darwin (arm and intel). >> > > I thought about using crosstool-ng but in the end decided to go with > something that, for me, is simpler: have all the build logic in PKGBUILD. Well, we can see. crosstool-ng brings a lot of benefits of course, but also a lot of waiting for builds. Clearly I'm a fan of that tool so there may be a conflict of interests at play regarding pull requests :-) Regarding that, we are going to at some time, open up an AUR-like repository, but we don't have the AUR-like infrastructure nor the time to manage it so it'll be a bit of a free-for-all, so long as the package builds and doesn't conflict with any of the mainline ones then we'd accept it. I guess I'll take a wait and see approach for now as I've not got much time for working on cross toolchains at present, and when I do I will target Linux and Darwin first anyway, rather than bare metal which you are targeting. > > Carlos > > ------------------------------------------------------------------------------ > _______________________________________________ > Msys2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/msys2-users ------------------------------------------------------------------------------ _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
