My recommendation is to look at what MacPorts does for gcc-arm or some other cross-compilation GNU toolchain that produces binutils, gcc, gdb, and library/header packages, and replicate that using the msp430 target flags. That would seem to be the best way to produce packages that are compatible with what users will expect.
Peter On Thu, Jun 26, 2014 at 9:01 PM, Aljaž Srebrnič <a2pirates...@gmail.com> wrote: > On 26/giu/2014, at 21:59, DJ Delorie <d...@redhat.com> wrote: > >> >>> Also, why are you building msp430-elf-gcc in two steps, Peter? Can I >>> build newlib first and then msp430-elf-gcc? >> >> How do you build newlib without a C compiler? > > Ah, yes, sorry. What I meant was can msp430-elf-gcc be built without newlib? > I wanted to create a separate package for newlib. > > -- > Aljaž Srebrnič a.k.a g5pw > My public key: http://bit.ly/g5pw_pubkey > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
