From: Michael C. <mi...@ca...> - 2008-05-15 17:29:34
|
I complete new to C++ development in this environment. I did C/C++ 9 years a go and since then I've done Java. I have used Eclipse in Java alot including making plugins. That said, I"m crawling all over again, I fee like an infant. Here's my question: I have a linux machine running Unbuntu 8.04 with Eclipse 3.3 installed along with th CDT. I also have the BuildRoot checked out and built. When I create a new C++ Project I select Makefile project, then the Hello World C++ Project. Then on the right hand side there is an option Linux GCC or --Other Toolchain --. As I understand and I'm reading like crazy both in new books I bought from borders and from the gumstix wiki amongst others, as I understand when the BuildRoot is built it creates a toolchain for the gumstix. is there a way to register that tool chain withEclipse so that I can select it? Do I need to? Ulitmately I'll add to the build root process local on my computer and build it as part of the file system, unless there is an easier way, like build it in Eclipse using the correct toolchain and then all I have to do is deploy it. Like I said I'm totally new to this. Please be gentle : - ). Thanks, Michael "In the beginner's mind there are many possibilities. In the expert's mind there are few." -Shunryu Suzuki |
From: Chris D. <chr...@gm...> - 2008-05-15 20:10:11
|
Michael, Take a look here http://wiki.hbmobile.org/index.php?title=HOWTO_Configure_Eclipse_to_Work_with_Jowles It goes through the steps to have eclipse use the buildroot toolchain. Chris On Thu, May 15, 2008 at 11:30 AM, Michael Caughey <mi...@ca...> wrote: > I complete new to C++ development in this environment. I did C/C++ 9 years > a go and since then I've done Java. I have used Eclipse in Java alot > including making plugins. That said, I"m crawling all over again, I fee > like an infant. > > Here's my question: > > I have a linux machine running Unbuntu 8.04 with Eclipse 3.3 installed along > with th CDT. > I also have the BuildRoot checked out and built. > > When I create a new C++ Project I select Makefile project, then the Hello > World C++ Project. Then on the right hand side there is an option Linux GCC > or --Other Toolchain --. As I understand and I'm reading like crazy both in > new books I bought from borders and from the gumstix wiki amongst others, as > I understand when the BuildRoot is built it creates a toolchain for the > gumstix. is there a way to register that tool chain withEclipse so that I > can select it? Do I need to? Ulitmately I'll add to the build root process > local on my computer and build it as part of the file system, unless there > is an easier way, like build it in Eclipse using the correct toolchain and > then all I have to do is deploy it. > > Like I said I'm totally new to this. Please be gentle : - ). > > > Thanks, > Michael > > "In the beginner's mind there are many possibilities. In the expert's mind > there are few." > -Shunryu Suzuki > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Michael C. <mi...@ca...> - 2008-05-16 02:37:02
|
This might be a stupid question, but if I use the toolchain from the buildroot, will the executable that I compile be ready to run on the gumstix? My assumption, or belief, or thought is yes. I just want to be positive so if i try it and hit a brick wall I can rule that out. I'm soooo glad I went down this road. I've already switched from C++ to C, read two books started another, begun coding in C and totally redesigned my application. All in two days. BTW any good book recommendations for building apps for Gumstix or embedded apps? I read the C++ pocket guide, as a refresher and OReillys Programming Embedded Systems and I have identified a few chapters in the Advanced Programming in the Unix Environmet that I want to skim/read. I thought about picking up O'Riellys book on Device Drivers. -Michael ----- Original Message ----- From: "Chris Dollar" <chr...@gm...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Thursday, May 15, 2008 4:09 PM Subject: Re: [Gumstix-users] Eclipse C++ and using the toolchain for gumstix > Michael, > > Take a look here > http://wiki.hbmobile.org/index.php?title=HOWTO_Configure_Eclipse_to_Work_with_Jowles > It goes through the steps to have eclipse use the buildroot toolchain. > > Chris > > On Thu, May 15, 2008 at 11:30 AM, Michael Caughey <mi...@ca...> > wrote: >> I complete new to C++ development in this environment. I did C/C++ 9 >> years >> a go and since then I've done Java. I have used Eclipse in Java alot >> including making plugins. That said, I"m crawling all over again, I fee >> like an infant. >> >> Here's my question: >> >> I have a linux machine running Unbuntu 8.04 with Eclipse 3.3 installed >> along >> with th CDT. >> I also have the BuildRoot checked out and built. >> >> When I create a new C++ Project I select Makefile project, then the Hello >> World C++ Project. Then on the right hand side there is an option Linux >> GCC >> or --Other Toolchain --. As I understand and I'm reading like crazy both >> in >> new books I bought from borders and from the gumstix wiki amongst others, >> as >> I understand when the BuildRoot is built it creates a toolchain for the >> gumstix. is there a way to register that tool chain withEclipse so that >> I >> can select it? Do I need to? Ulitmately I'll add to the build root >> process >> local on my computer and build it as part of the file system, unless >> there >> is an easier way, like build it in Eclipse using the correct toolchain >> and >> then all I have to do is deploy it. >> >> Like I said I'm totally new to this. Please be gentle : - ). >> >> >> Thanks, >> Michael >> >> "In the beginner's mind there are many possibilities. In the expert's >> mind >> there are few." >> -Shunryu Suzuki >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Chris D. <chr...@gm...> - 2008-05-16 02:53:09
|
On Thu, May 15, 2008 at 8:37 PM, Michael Caughey <mi...@ca...> wrote: > This might be a stupid question, but if I use the toolchain from the > buildroot, will the executable that I compile be ready to run on the > gumstix? My assumption, or belief, or thought is yes. I just want to be > positive so if i try it and hit a brick wall I can rule that out. Yes, assuming you have a buildroot-based root filesystem on your gumstix. If you have an OE-based one you'll need to use the toolchain it builds. ...snip... > I thought about picking up O'Riellys book on Device Drivers. Really just about any book on C programming with linux will work, it doesn't have to be embedded specific. And the Linux Device Drivers book is available online for free if you don't mind reading it from a PDF. Chris |
From: Michael C. <mi...@ca...> - 2008-05-16 03:07:13
|
OE-Based? Whats that is it something new? I thought there was only BuildRoot. ----- Original Message ----- From: "Chris Dollar" <chr...@gm...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Thursday, May 15, 2008 10:53 PM Subject: Re: [Gumstix-users] Eclipse C++ and using the toolchain for gumstix > On Thu, May 15, 2008 at 8:37 PM, Michael Caughey <mi...@ca...> > wrote: >> This might be a stupid question, but if I use the toolchain from the >> buildroot, will the executable that I compile be ready to run on the >> gumstix? My assumption, or belief, or thought is yes. I just want to be >> positive so if i try it and hit a brick wall I can rule that out. > Yes, assuming you have a buildroot-based root filesystem on your > gumstix. If you have an OE-based one you'll need to use the toolchain > it builds. > > ...snip... >> I thought about picking up O'Riellys book on Device Drivers. > Really just about any book on C programming with linux will work, it > doesn't have to be embedded specific. And the Linux Device Drivers > book is available online for free if you don't mind reading it from a > PDF. > > Chris > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Chris D. <chr...@gm...> - 2008-05-16 03:57:44
|
On Thu, May 15, 2008 at 9:07 PM, Michael Caughey <mi...@ca...> wrote: > OE-Based? Whats that is it something new? I thought there was only > BuildRoot. There has been an OE based gumstix build system available for ~6 months, and you can use either it (docs available at gumstix.net) or the buildroot system, which still works fine too. The main difference between the 2 is that buildroot builds a uClibc based rootfs, while OE builds a glibc based one (OE can build a uClibc system but doesn't by default). The two different libc are not compatIble with one another, so if you need to make sure what you compile with is the same as what is on your gumstix. If its not the same, no need to worry -- just build a rootfs and kernel with whatever build system you want to use and flash that to your gumstix and all is well. Gumstix just started shipping the motherboards with OE based filesystems. If when you login your prompt is 'root@gumstix-custom-verdex' or 'root@gumstix-custom-connex' then you have an OE based filesystem. If its just 'root@gumstix' chances are you've got a buildroot based system. If you stil aren't sure what type of filesystem you have on your stix write back and I'll give you some other things to help determine it, but keep in mind that if you want to use buildroot and you do have an OE system on your stix all you have to do is reflash it and you can continue to use buildroot. Chris > > > ----- Original Message ----- > From: "Chris Dollar" <chr...@gm...> > To: "General mailing list for gumstix users." > <gum...@li...> > Sent: Thursday, May 15, 2008 10:53 PM > Subject: Re: [Gumstix-users] Eclipse C++ and using the toolchain for gumstix > > >> On Thu, May 15, 2008 at 8:37 PM, Michael Caughey <mi...@ca...> >> wrote: >>> This might be a stupid question, but if I use the toolchain from the >>> buildroot, will the executable that I compile be ready to run on the >>> gumstix? My assumption, or belief, or thought is yes. I just want to be >>> positive so if i try it and hit a brick wall I can rule that out. >> Yes, assuming you have a buildroot-based root filesystem on your >> gumstix. If you have an OE-based one you'll need to use the toolchain >> it builds. >> >> ...snip... >>> I thought about picking up O'Riellys book on Device Drivers. >> Really just about any book on C programming with linux will work, it >> doesn't have to be embedded specific. And the Linux Device Drivers >> book is available online for free if you don't mind reading it from a >> PDF. >> >> Chris >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Michael C. <mi...@ca...> - 2008-05-16 05:00:37
|
I bought my boards last June and July. I think the last time I flashed them it was in September. However I did download the Source and followed the Buildroot process. I haven't done much since October on the Gumstix app. I wrote the Ground station in November but thats a Java app that is meant to be run a Laptop PC. So obviously i have a little catching up to do. Are there benifits to the OE version? I'm not going to have a GUI, but I will be using UART, I2C, PWM on the robostix, ethernet and File/IO on the CompatFlash card. Oh and the board is a verdex . Thanks for all your help with this. -Michael ----- Original Message ----- From: "Chris Dollar" <chr...@gm...> To: "General mailing list for gumstix users." <gum...@li...> Sent: Thursday, May 15, 2008 11:57 PM Subject: Re: [Gumstix-users] Eclipse C++ and using the toolchain for gumstix > On Thu, May 15, 2008 at 9:07 PM, Michael Caughey <mi...@ca...> > wrote: >> OE-Based? Whats that is it something new? I thought there was only >> BuildRoot. > There has been an OE based gumstix build system available for ~6 > months, and you can use either it (docs available at gumstix.net) or > the buildroot system, which still works fine too. > > The main difference between the 2 is that buildroot builds a uClibc > based rootfs, while OE builds a glibc based one (OE can build a uClibc > system but doesn't by default). The two different libc are not > compatIble with one another, so if you need to make sure what you > compile with is the same as what is on your gumstix. If its not the > same, no need to worry -- just build a rootfs and kernel with whatever > build system you want to use and flash that to your gumstix and all is > well. > > Gumstix just started shipping the motherboards with OE based > filesystems. If when you login your prompt is > 'root@gumstix-custom-verdex' or 'root@gumstix-custom-connex' then you > have an OE based filesystem. If its just 'root@gumstix' chances are > you've got a buildroot based system. If you stil aren't sure what > type of filesystem you have on your stix write back and I'll give you > some other things to help determine it, but keep in mind that if you > want to use buildroot and you do have an OE system on your stix all > you have to do is reflash it and you can continue to use buildroot. > > Chris > >> >> >> ----- Original Message ----- >> From: "Chris Dollar" <chr...@gm...> >> To: "General mailing list for gumstix users." >> <gum...@li...> >> Sent: Thursday, May 15, 2008 10:53 PM >> Subject: Re: [Gumstix-users] Eclipse C++ and using the toolchain for >> gumstix >> >> >>> On Thu, May 15, 2008 at 8:37 PM, Michael Caughey <mi...@ca...> >>> wrote: >>>> This might be a stupid question, but if I use the toolchain from the >>>> buildroot, will the executable that I compile be ready to run on the >>>> gumstix? My assumption, or belief, or thought is yes. I just want to >>>> be >>>> positive so if i try it and hit a brick wall I can rule that out. >>> Yes, assuming you have a buildroot-based root filesystem on your >>> gumstix. If you have an OE-based one you'll need to use the toolchain >>> it builds. >>> >>> ...snip... >>>> I thought about picking up O'Riellys book on Device Drivers. >>> Really just about any book on C programming with linux will work, it >>> doesn't have to be embedded specific. And the Linux Device Drivers >>> book is available online for free if you don't mind reading it from a >>> PDF. >>> >>> Chris >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Chris D. <chr...@gm...> - 2008-05-16 05:28:50
|
On Thu, May 15, 2008 at 11:00 PM, Michael Caughey <mi...@ca...> wrote: > I bought my boards last June and July. I think the last time I flashed them > it was in September. However I did download the Source and followed the > Buildroot process. You should be fine to use buildroot then. > Are there benifits to the OE version? I'm not going to have a GUI, but I > will be using UART, I2C, PWM on the robostix, ethernet and File/IO on the > CompatFlash card. Oh and the board is a verdex . There are more available 'out-of-the-box' buildable packages for the OE build system, but if you're compiling your own code manually via the toolchain as you are planning to do there probably isn't any real advantage to moving to OE. I myself use the OE system and love it.. there are plenty of other folks that still use buildroot because they really have no compelling reason to switch. In the end, its really your preference, but neither build system will restrict you for what you want to accomplish. Chris |