Invoking the Propeller tool's compiler from the command line?

Fjornir

How do I go about invoking the compiler from the command line? I'm not a huge fan of the IDE (I've invested a lot of time learning vi over the years) and I'd like to be able to do some stuff with makefiles to simplify my workflow. Checking over the help files is yielding no clues.

Any insight?

kwinn

As far as I know this is not possible. Not really of any benefit either since the compiler does everything for you that a makefile normally does.

David Betz

Fjornir wrote: »

How do I go about invoking the compiler from the command line? I'm not a huge fan of the IDE (I've invested a lot of time learning vi over the years) and I'd like to be able to do some stuff with makefiles to simplify my workflow. Checking over the help files is yielding no clues.

Any insight?

You can do this with Brad's Spin Tool. He includes a command line compiler called 'bstc' that will do just what you want. I use it with makefiles all the time.

Fjornir

kwinn wrote: »

As far as I know this is not possible. Not really of any benefit either since the compiler does everything for you that a makefile normally does.

Except, of course, that it doesn't. To start with the IDE has the nasty feature of needing one interaction to start the compile and a second to drop the file onto disk. And it would be really nice to have my makefile be able to deploy the newly dropped image onto my device from a single 'make' instead of having to build, save the file, and then run a command to handle the reboot/reload/reboot cycle. A make can also check my latest changes into my svn on successful build so if I decide I want to back up I've got good revision history. And, again, using the as-distributed IDE is frustrating since I'm quite good with a good text editor and don't want to have to use something that feels crippled.

Fjornir

David Betz wrote: »

You can do this with Brad's Spin Tool. He includes a command line compiler called 'bstc' that will do just what you want. I use it with makefiles all the time.

Awesome, I will definitely look this up.

jazzed

@Fjornir,

Following up what David said with links, etc....

You're in luck. There are currently 3 PC command line Propeller compilers and one Propeller hosted compiler. All the PC hosted compilers create equal quality code. I've not used the Propeller hosted compiler, so I don't know much about it. There is also a set of spin.vim language highlighting files.

Of the compilers, Homespun offers the most pre-processor features but requires .net (i don't have a problem with .net). A very popular option is BSTC which is cross-platform and offers all of Homespun's pre-processor features except #include. Propellent is the Parallax command line compiler. It does not have any pre-processor options, but it is better than the PropellerTool GUI because it lets you specify a library path.

HOMESPUN http://forums.parallax.com/showthread.php?106401-Homespun-Spin-compiler-0.30-Now-with-ifndef
BSTC http://www.fnarfbargle.com/bst.html
Propellent http://www.parallax.com/Portals/0/Downloads/sw/propeller/Propellent-v1.3.zip
SPIN.VIM http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBQQFjAA&url=http%3A%2F%2Fforums.parallax.com%2Fshowthread.php%3F118328-Spin-syntax-definition-for-Vim&ei=DV5pTbbTOIXAsAPShNymBA&usg=AFQjCNGe2i3_eATTUsqRhkOYYLL8trTtzw&sig2=uFORpB5B9cH36XHjvIZGsw

Fjornir

jazzed wrote: »

@Fjornir,

Following up what David said with links, etc....
<snipping an excellent post for brevity>

Thank you very much, I will look into these.