Re: [Gumstix-users] Programing Robostix

[Stucker, B. M <bri...@uk...>]

Dave

Are you then running everything from the command line interface then?  What do i need to have downloaded besides gcc and winavr to run this from the command line on a windows xp box.  If this is not able to work on windows xp as you have described i also have ubuntu installed on another machine.

But to sum up, if i stick with how the folders are layed out now then i just have to type make from within the folder i want to build the hex file.  So if i want to create a new project i create a new folder and my files, then create a makefile as you have done for the simple-flasher program and that should work?

Thankyou,
Brian

Sent from my AT&T Windows Mobile phone.

-----Original Message-----
From: Dave Hylands <dhy...@gm...>
Sent: Tuesday, November 18, 2008 11:11 AM
To: General mailing list for gumstix users. <gum...@li...>
Subject: Re: [Gumstix-users] Programing Robostix


Hi Brian,

On Mon, Nov 17, 2008 at 10:37 PM, Stucker, Brian M
<bri...@uk...> wrote:
> I see what you mean in the makefile for the included simple-flasher folder, but within avrstudio the makefile is automatically created.  So are you saying that avrstudio might not be making the makefile correctly?  I don't want to have to use gcc to manually compile every time I code, that's what I thought the benefit was to use avrstudio.  Below is the contents of the makefile that avrstudio generated.

To build, I just cd into the directory Flash-LED and type

make

The Makefile that you created for avrstudio only has a single file in
it. To build the Flash-LED sample, you'll need all of the following
files:

robostix/Common/a2d_8.c
robostix/Common/Delay.c
robostix/Common/Timer.c
robostix/Common/UART.c
robostix/Flash-LED/Hardware.c
robostix/Flash-LED/Flash-LED.c

I've never built anything using avr studio, so I'm not sure if that's
enough or not. The Makefile system that's included in the robostix
tree is already complete and works, so you may want to try that first.
Sometimes, files will need particular options.

make v=1

will cause the complete command line for each program which is
executed (ie compiler, linker) to be displayed.

make clean

is normally not required, but it will remove all generated files.

--
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
gumstix-users mailing list
gum...@li...
https://lists.sourceforge.net/lists/listinfo/gumstix-users