Re: [beagleboard] Coding with C/C++ directly on Beaglebone, via IDE?

[The Brisk Beagle]

Hi Fulvio,

Am 05.01.2013 um 23:27 schrieb fulvio...@gmail.com:
> Now I have noticed that the OS has already g++, so it is possible to just write in VI simple C++ code, and compile it to run it directly from console (which is great for me).

[...]

> In the end, I would like to have a better editor than VI, and also would love to use an IDE instead than just using text editors without code completion, breakpoints, step by step instructions and so on...so I thought that cloud9 may work, since I just need to run the browser directly on the BeagleBone and I can code and compile on the go without a computer.
>
> Is this possible? Is there another way to accomplish what I need? I am pretty sure that if I install on the Angstrom release Eclipse, and try to use it; the board will just be too slow to run it,

Why not just mount a directory from your host on the Beagle (or vice versa) so you can edit the files on your host PC with any IDE you like but still compile on the Bone? If you use a managed Makefile approach (as is possible with Eclipse), you'll have the Makefiles in sync easily.

Best,
Mark

[NeonJohn]

On 02/23/2013 01:44 PM, chris...@gmail.com wrote:
> Fulvio,
>
> Netbeans C/C++ has a remote build and debug mode that I've used
> successfully on the beaglebone. I
> followed http://mechomaniac.com/BeagleboardDevelopmentWithNetbeans to get
> it setup. I'm not the biggest fan of netbeans, but the remote stuff is
> really nice

That's a pretty awful way of doing things because it uses the BB's
native compiler which generates code about 10x slower than does v4.6 of
the Gnu C ARM cross compiler. At least that's the case with the
application I'm developing which does a LOT of floating point math.
Plus, on a reasonably fast PC, the compile of a few thousand lines of
code is over before you can lift your finger off the "enter" key.

Here's my setup. Ubuntu Linux 12.04 with Gnome.

I have a BASH alias that calls a script called "startwork". That script
opens 2 more terminal windows in the directory I'll be working in and
opens 2 Nautilus file manager windows, also in the working directory.

Terminal window 1 is where I start gvim from. Window 2 is ssh'd into
the BB. That's

$ ssh root@maggie

I've named my BB maggie and entered her IP in the /etc/hosts table so I
don't have to type the IP number every time.

Window 3 is my "make" window and where I do other general purpose stuff.

In my make file are the following lines after the line that compiles the
code:

chmod +x $@
rm -rf /tmp/code
mkdir /tmp/code
mv $@ /tmp/code
scp jgd@neonjohn:/tmp/code/* root@maggie:.
rm -rf /tmp/code
@echo ""
@echo "finished $@"
@echo ""

This additional stuff changes the mode of the cross-compiled executable
to "execute", copies it to a temp directory because scp doesn't like
relative addresses too much, scps the file over to the BB, removes the
temp file and announces completion.

Scp or secure copy is like rcp only secure. In fact, in Ubuntu the
command "rcp" is just a link to scp.

So I have my work files open in as many instances of gvim as I need, I
have one terminal window remote logged into the BB and I have a
make/compile window.

I write some code, save it (without exiting the editor), move the mouse
over to the compile window and up-arrow to recall "make", make and copy
the binary over to the BB and am ready to test the code, all in about 5
seconds, most of that time being spent on scp setting up the secure
connection.

This is especially nice if you're a vi fanatic like I am or you have
another favorite editor. It sure kicks butt against an IDE.

John



--
John DeArmond
Tellico Plains, Occupied TN
http://www.fluxeon.com <-- THE source for induction heaters
http://www.neon-john.com <-- email from here
http://www.johndearmond.com <-- Best damned Blog on the net
PGP key: wwwkeys.pgp.net: BCB68D77

[Fulvio C]

Thanks for your replies Chris and Neon

As now I've found a sort of compromise, using Eclipse on Ubuntu, but I was more interested in being able to code "on the go".

Like if I have a monitor available I can hook up the BB and just start to code on it; same for the LCD screen. I am aware that compiling on the bone itself would be slow; but I think that if you need to, and have no other options, it is better than nothing. 

The bone does not handle a full GUI environment, if you need to code, so my hope was that anyone has found a way to in fact write code on these boards without having a computer attached to it. Either with some app like cloud9, that in fact allows you to write C++ code, compile and run it directly on the bone, or with a sort of IDE, that is able to run on minimal X server (I don't need the whole windows manager and such, I just need a window that allows me to code and build, so when I go back home I can copy what I coded and continue to work on the computer). 

As is now I am oriented to just write shell scripts to make complex operations easier (and saves me a bunch of typing), and just use one of the shell editors; or I gotta write such IDE from scratch :)

In the meantime I will give a try to both of your solutions...they look different from the Eclipse setup that I have now, so I am very interested in see how faster they are, compared to what I do now.

Thanks!

[pco...@gmail.com]

Hi all

I have a brand new beaglebone black and I'm also trying to install an IDE directly in Angstrom so I can do all the programming from within the board. I don't want to use a cross compiler, do you know of any package that can do this?

Thanks a lot!!

[Karl Longen]

Sadly there are no options to code directly on the BB; unless you run the full desktop environment on a tv or monitor.

In which case you may be able to use a couple of lightweight text editors...eclipse won't run on Angstrom decently; it would take forever to use it honestly.

I hope that someone will make something simple, like Cloud9 but with C++ support, so you have a full IDE without having to cross compile.

The whole point of having a board that run a full OS is to have a full IDE to write code, after all. This is not an Ipad/Droid device in the end :)

[William Hermans]

There is no reason why you can not use an IDE / Editor on a PC and then use SCP, SSH or whatever else to move the source over then compile on the BBB.

However, there is a reason why most people choose to cross compile. Anything sizable will take forever to compile directly on the BBB.

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[walter harms]

Am 05.03.2014 07:52, schrieb William Hermans:
> There is no reason why you can not use an IDE / Editor on a PC and then use
> SCP, SSH or whatever else to move the source over then compile on the BBB.
>
> However, there is a reason why most people choose to cross compile.
> Anything sizable will take forever to compile directly on the BBB.
>
>

IMHO, the most easy way is to crosscompile and share a directory via NFS
with the beagleboard. This way you can test without copying.

re,
wh

[c...@isbd.net]

Karl Longen <2frikki...@gmail.com> wrote:
> [-- text/plain, encoding 7bit, charset: UTF-8, 35 lines --]

>
> Sadly there are no options to code directly on the BB; unless you run the
> full desktop environment on a tv or monitor.
>

Ay? You can do it all from the command line surely, there's gcc and
g++ there and make. There's also vi for editing your files. I
personally find that IDEs just get in the way.

Open multiple ssh connections to the BBB, run vi in one of them, make
in another and do testing in a third - the best IDE there is.

--
Chris Green
·

[Karl Longen]

He is asking to code via IDE directly in Armstrong...G++ and the other command line solutions do not fit the IDE requirement.

[Karl Longen]

BTW you have never tried to code pages and pages using just VI probably....

Any person in their right state of mind would not use VI, unless you are writing short programs (like shell script), or very simple applications.

Renounce to auto correction, color syntax, auto completion, and a ton more of functionalities, when you are coding millions of lines, is not different from running win 3.1 on a modern computer :)

As much as I love terminal, there are things that are not feasible without a good text editor with plenty of functions; without even mentioning the pros of a real IDE, when you need to debug and such.

On Wednesday, March 5, 2014 4:15:11 AM UTC-8, c...@isbd.net wrote:

[walter harms]

Am 05.03.2014 13:25, schrieb Karl Longen:
> He is asking to code via IDE directly in Armstrong...G++ and the other
> command line solutions do not fit the IDE requirement.
>

he did not specify what IDE could simply use emacs.

re,
wh

> On Wednesday, March 5, 2014 4:15:11 AM UTC-8, c...@isbd.net wrote:
>>

[Paulo Ferreira]

On 05/03/2014, at 12:30, Karl Longen <2frikki...@gmail.com> wrote:

> BTW you have never tried to code pages and pages using just VI probably....
>
> Any person in their right state of mind would not use VI, unless you are writing short programs (like shell script), or very simple applications.
>
> Renounce to auto correction, color syntax, auto completion, and a ton more of functionalities, when you are coding millions of lines, is not different from running win 3.1 on a modern computer :)
>
> As much as I love terminal, there are things that are not feasible without a good text editor with plenty of functions; without even mentioning the pros of a real IDE, when you need to debug and such.

Well, last time I checked vim has (even in text mode):

Color syntax (and syntax checking when doing save) : https://github.com/scrooloose/syntastic
Auto Completion and more: http://www.vim.org/scripts/script.php?script_id=213
When I compile it can place me on the file and on the line where the error is...

And the "colorized" syntax works on ssh connections, and you can have multiple windows in text mode with just one ssh connection with tmux: http://tmux.sourceforge.net

It may not be a tool for everybody, editor and IDEs are alms a religious issue, and b=should be left to the individual taste, but vi (vim) is more powerful than it looks.

Best regards
Paulo Ferreira

[c...@isbd.net]

walter harms <wha...@bfs.de> wrote:
>
>
> Am 05.03.2014 13:25, schrieb Karl Longen:
> > He is asking to code via IDE directly in Armstrong...G++ and the other
> > command line solutions do not fit the IDE requirement.
> >
>
> he did not specify what IDE could simply use emacs.
>

Exactly! :-)

--
Chris Green
·

[c...@isbd.net]

Karl Longen <2frikki...@gmail.com> wrote:
> BTW you have never tried to code pages and pages using just VI
> probably....
>

I have used it since some time in the mid 1980s, so I am fairly
familiar with it - and it's available on *every* platform I program on
which is a big advantage. (Not to mention that I use it for composing
E-Mail, Usenet messages, etc.)

> Any person in their right state of mind would not use VI, unless you are
> writing short programs (like shell script), or very simple applications.
> Renounce to auto correction, color syntax, auto completion, and a ton more
> of functionalities, when you are coding millions of lines, is not

Er, have you looked at recent versions of vi! :-)

> different from running win 3.1 on a modern computer :)
> As much as I love terminal, there are things that are not feasible without
> a good text editor with plenty of functions; without even mentioning the
> pros of a real IDE, when you need to debug and such.
>

As I said, editor in one window, make in the next, testing in the next
(i.e. the debugger).

I'm semi-retired now but I used to work on systems with several
million lines of code, everyone used either EMACS or vi.

--
Chris Green
·

[Micka]

VI ? Really ?

You should start using Eclipse or visual studio .... they provide tons of function that vi don't provide. 

eclipse/visualstudio => with a few click you configure your workspace, you build your project, you deploy your project, your run/debug your project .

VI => with tons of hours you configure your workspace .... 

I don't have time to argue with it, it's just a simple matter of accepting the evolution ...... 

Micka,

--
Chris Green
·

[Alexander Holler]

Am 05.03.2014 13:30, schrieb Karl Longen:
> BTW you have never tried to code pages and pages using just VI probably....
>
> Any person in their right state of mind would not use VI, unless you are
> writing short programs (like shell script), or very simple applications.

That's just plain wrong and doesn't reflect reality.

> Renounce to auto correction, color syntax, auto completion, and a ton more
> of functionalities, when you are coding millions of lines, is not different
> from running win 3.1 on a modern computer :)

If you really need those things, vim and emacs are offering such stuff too.

> On Wednesday, March 5, 2014 4:15:11 AM UTC-8, c...@isbd.net wrote:

>> Open multiple ssh connections to the BBB, run vi in one of them, make
>> in another and do testing in a third - the best IDE there is.

Try <esc>:make in vim.

Regards,

Alexander Holler

[William Hermans]

Cross compiling is really as simple as downloading a Linaro toolchain, and just setting up the toolchain binary paths in an IDE. Even on Windows.

Then on Windows you can use Visual Studio, Eclipse, Code:Blocks, or even use the toolchain directly via comandline, with an editor like notepad++, or Sublime text. Notepad is even possible, but I think that any reasonable developer will know that notepad is not really an option.

Personally, I use Code:Blocks for project management, and cross compiling( Via Linaro GCC). Sublime text as my main editor, and a directory shared via Samba, which is them maped as a network drive in Windows.

[Karl Longen]

Emacs is not an IDE, but a text editor.

IDE include a source code (text) editor, a compiler, a linker and a debugger

Eclipse, Netbeans, Mono development, Visual studio; these are IDE

I second the use of Emacs, it is great to write code, but you still need to use a compiler, linker and debugger to write executables on the BB

[Karl Longen]

These are commodities added on top; the original VI or VIM do not have all of these features. If you log in into a standard Unix box, you won't have that.

Technically you can write shell script that allow you to compile and link directly from VI, but is more work than expected...it was not made for that after all.

Not saying that you can't do it; but that it is a pain to do it for big projects. I use VI all the time for any small project, but try to write something like a full size application and you can see that is not feasible.

BTW you refer to text editors preference, not IDE, since VI is not an IDE. I agree that each person choose their own, same goes for the IDE :) For example I still love DEV C++; does all that I need and I wish that there was a version for Angstrom...and that's an ancient IDE, but it is lightweight and decently fast. Most people do not need the ton of features that big IDE gives you, like VS.

[Karl Longen]

Exactly, that was in the past....this is 2014; we don't necessarily need to use things from the past, when there is something else new that perform better

Do you still drive your old carburetor car from the 70s? Do you still use an 8086, green phosphor monitor and textual OS? You may, but why would you, other than for a nostalgic/habit reason?

I own an old car because I love that specific model, but I have as main car an hybrid, which is fairly new...cost less to maintain, less to own 

My point is not that you can't use it; just that won't make any sense, if you have better options.

[Karl Longen]

I don't see anything wrong.....in this world nothing is "wrong" (other than the attitude), there is what is right for someone and what is right for most of the people.

In 15 years working as programmer, I have NEVER experienced a single developer using VI for anything other than modify server side files (either config, daemons, apache config files), or to create quick shell script to automate some process.

I've been in plenty of companies, where there were awesome people that had 40 years of experience, that were so kind to show me how they do their job....most of them avoided intentionally VI when they had the chance, because they had to work with it in the past, since there was nothing else :) Strange enough, nobody loved it, while writing applications of a certain size.

If someone likes it as text editor, so be it, but I would not go around saying to others that they are "wrong", just because they don't see it in the same way. Conflicts are born because someone think that he/she has the right to be right, while the others are wrong. Especially in CS, there is more than a way to do anything, so the right or wrong is really a matter of personal opinion. 

Then again: Emacs and VI are text editors, not Integrated Development Environments; for the same reason that a VW beetle with a Porsche engine is not a Porsche, a text editor with IDE functionalities is not an IDE....it can be used for that purpose, but there are a ton of other easier and more reliable alternatives; which means that the use of this or that method is purely discretional and based on personal preferences.

The original topic was "is there an IDE for the BB, to avoid cross compile?", unless I am mistaken.

Have a good day

[Karl Longen]

Did you try with Eclipse? It is multi platform, and there is a nice youtube tutorial video that show how to set it up for the BB.

Quite simple to cross compile, but not possible on the BB itself; Eclipse just sit and cry if you run it on the IDE, even without loading the full desktop (tried to just start X11).

[Alexander Holler]

Am 06.03.2014 00:14, schrieb Karl Longen:
> I don't see anything wrong.....in this world nothing is "wrong" (other than
> the attitude), there is what is right for someone and what is right for
> most of the people.
>
> In 15 years working as programmer, I have NEVER experienced a single
> developer using VI for anything other than modify server side files (either
> config, daemons, apache config files), or to create quick shell script to
> automate some process.

Hmm, I wonder what you've did in 15 years.

You even didn't know that vim has code coloring since a long time but
then you say nobody uses vim.

Alexander Holler

[Micka]

This kind of topic will never stop .... can we stop this discussion ? Every one has his favorite tools + we don't develop together which means that this discussion is useless. 

Micka,

Alexander Holler

[Alexander Holler]

Am 06.03.2014 11:43, schrieb Micka:
> This kind of topic will never stop .... can we stop this discussion ? Every
> one has his favorite tools + we don't develop together which means that
> this discussion is useless.

Not if someone says he knows it all and makes obvious false statements.

[Alexander Holler]

Am 06.03.2014 00:05, schrieb Karl Longen:
> Exactly, that was in the past....this is 2014; we don't necessarily need to
> use things from the past, when there is something else new that perform
> better

And in 2016 you don't have a device anymore where your, what *you*
declare as IDE, still will run on.

Alexander Holler

[Karl Longen]

What did I do in 15 years? Participated in the released 5 Windows games, 4 applications for Windows and Mac, 2 for iOS.

Changed 4 companies, all of them are top tier company in USA, where VI is not used at all. Then of course, I may live in a different world from yours.

I didn't even bother checking color coding for Vim, because as mentioned earlier, I don't need to use it for something that is not meant to; when I have something better, newer, faster, easier. Same goes for the places where I used to work: people do not use it.

I have seen few people using Memacs, but it was a rarity, and limited to few old engineers. The world is not only like you see it; the fact that you have certain experiences is not a considerable proof to say " this is how it is everywhere".

There are 6M of people on this planet, in case you didn't realize it.

[Karl Longen]

I was merely pointing out that the original topic is asking for an IDE and not a text editor to write applications; and that's the line that I am taking in my replies. 

I never syndicated what a person should or should not use; just brought my personal experience and described my case. If someone wants to use notepad, Vi, Emacs or his wall to write code, is their problem.

I simply said that the point is an IDE, and this whole thing of Vim with color coding and such started.

[Karl Longen]

Amiga is still alive; was made in 1985; has a great OS, which many still use for simple tasks (and many copied)....as you can see old hardware and software survive if there are people using them, but this won't make them "the best" just because they are still in use.

Same goes for Vi, Vim, Sed, Awk and another hundred of utilities and applications.

What "I declare" as IDE is the definition of it; pretty simple and clear; if you want to use something and call it IDE, it is your business; like using a painting brush to mop he floor. The point was never "you can't do it", but "there is something more functional and productive".

Now let's bring back coal, it is still around, so we should use it to retrofit our cars.

[Alexander Holler]

Am 06.03.2014 20:54, schrieb Karl Longen:

> I have seen few people using Memacs, but it was a rarity, and limited to
> few old engineers. The world is not only like you see it; the fact that you
> have certain experiences is not a considerable proof to say " this is how
> it is everywhere".
>
> There are 6M of people on this planet, in case you didn't realize it.

Err, you made the obvious wrong statement that no one uses vi(m) for any
large and/or serious project. So you have to ask yourself who is the the
narrpw-minded one and who has to learn a bit more about reality.

Anyway, it's getting boring.

[Micka]

Can we stop this discussion ?  

And to make everyone happy, there is eclipse + vim => http://eclim.org

Micka,

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Karl Longen]

And this is the video that I was mentioning earlier:

http://www.youtube.com/watch?v=vFv_-ykLppo

Setup of Eclipse for the BB (but it apply also to the BBB).

The whole channel is a really great and educational site; all that I know about the BB is thanks to this guy.

[William Hermans]

I.D.E == integrated development environment. Technically, any well featured text editor could do these same duties.

Isnt bloodsheds DevC++ opensource ? Rewrite to use linaro's armhf toolchain . . . or make it configurable like Code::Blocks. Hell write your own for that matter.There is another similar ( but better looking ) C/C++ IDE out now. PellesC. I used to like bloodsheds IDE myself years ago, but prefer PellesC on the Windows desktop now days.However for cross platform developement ( cross arch ) PellesC is not configurable. At least not the last time I checked.

Also, someone with 15 years development experience should know that there are many developers that use VIM. Most Unix / Linux developers I know prefer VIM. Hell as primarily a Windows developer for the last 18 years. Even I like the way it looks in appearance( or can be made to look ).

Visual Studio

Pro's:

Excellent layout, very good code completion, excellent debug error reporting( honestly when setup correctly is very hard for other options to even match ), and a definition search feature that no other IDE seems to have either.

Con's:

With the latest version, the IDE has become very bloated. Many of the features mentioned above can require extensive setup outside of using Microsoft's cl.exe. That means any custom compiler / toolchain option. So for instance any version of gcc would have to be setup using a makefile project, and batch scripting / perl scripting for correct debug information, and proper / wanted compiler options. Or would require a plugin written using one of the professional or higher versions. Also is not cross platform.

Code::Blocks

Pro's:

Highly configurable, you can choose which toolchain / options you wish to use( custom if need be ). Essentially can be made to use any gcc / g++ type compiler. Is opensource, and is free( as in beer ). Has a very nice base project creation tool. Allowing the user to create projects from scratch which can then be used as project profiles in later projects. A very useful feature. Cross platform. Binaries for Windows, Linux, and I do believe OSX as well.

Con's:

Some feature can be buggy or do not seem to work correctly. For the most part from my own experience this just means the debugger would not work correctly for me. Granted I was using a specialized toolchain for the MSP430 MCU's.

Also as a personal preference, Code::Blocks while very capable as an IDE, just does not seem to be as polished as Visual Studio, or even Eclipse. This means in appearance as well as usability. Granted, considering the price, there is no real reason to complain.

Again a I mentioned in a previous post. I Personally use Code:Blocks for project management / binary compiling. For editing source code I prefer to use sublime text.

My reasons are simple.

1) Code::Blocks is very good at project management.

2) Code::Blocks can be made to use just about any opensource toolchain.

3) Code:Block is less than appealing visually for me personally ( read: code editor ).

4) Sublime Text has very attractive dark themes that is very easy one the eyes,

5) Sublime Text has *many* attractive features including a fairly intuitive addon manager.

6) Sublime text has many, many addons for many, many programming languages.

7) Sublime text is highly configurable / customizable as well.

[Karl Longen]

William; to be an IDE it needs a debugger, compiler and linker....if you can do that just with VI, I will personally work 80 hours a day and donate all my salary to you for the rest of my life :) 

The problem is not if Dev-C++ is open source or not...80% of the code probably is not even reusable (I don't really have the will nor the time to check it), and the rest is just the text editor probably; the problem thou is simple: it would be too heavy to run on the BB.

Write my own? Either you have too much free time or I have a very busy life :) How many people do you know that build their own IDE, just because ? Reinventing the wheel is one of the biggest mistake that most of the novice programmers do...you are not writing code that someone else already wrote, because makes no sense...if there is a library you extend it or take part of it to customize it (if the license allow you to do so), for your needs; altho if the person that wrote the library is a good architect, he/she made the API as generic as possible, and probably with overloading where needed.

Please leave out the VI topic, let's not start all over again with this nonsense.

BTW the topic is an IDE that runs on the Beaglebone....thanks for your insight about these software (I would go code:blocks for sure over VS...gb and gb of stuff that you may never use, just over bloating the software); it may help someone that is allergic to Eclipse. The original question started with that request, unless I am missing something.

[William Hermans]

Personally I am allergic to anything that requires JRE. Hence I refuse to use Eclipse.

There are text editors out there that are configurable to the point where you can configure external binaries to run on the press of a hotkey. Since the gcc toolchain consists of all cmd line tools, you do not need to output directly in the editor its self. You could however always redirect stdout / stderr if you so wished.

Anyway, watch these sometime.

https://tutsplus.com/course/improve-workflow-in-sublime-text-2/

Specifically "Vintage mode". Which is essentially VIM inside the text editor. The text editor can also execute external binaries, and is highly configurable / customizable. Anyway, this is about as close to VI / VIM in an IDE you're going to get I suppose.

As it happens I have started to write something which resembled a very simplistic  IDE with no built in text editor. Instead of finishing it however, I instead invested some time learning how Code::Blocks works, and just use GDB via the command line.

Personally, I think it is folly to even consider running an IDE directly on the BBB. So a moot point.

[mmk...@yahoo.co.uk]

Helllo,
     I am planning to get started with the BBB.  I want to develop  code in C or C++  on a PC, with Eclipse, compile and download to the BBB.   I dont want to get into the Eclipse debate, just so happens that I am familiar with it, and find it very powerful, so that is way I want to go.  I know it has been mentioned in this series of posts,
     Can somebody please give a step by step list of instructions, or possibly link, to how to get the full Eclipse toolchain setup and configured for use with the BBB.   It would be really helpful if  there were some example projects to help get started especially a project that uses the gpio.
Thanks in advance,
Mike.

On Saturday, 5 January 2013 22:27:50 UTC, Fulvio C wrote:

Hi all

Finally I've got my BeagleBone today, and I started to play with it already. I've updated the latest distro of the OS, and set it up to run with a power adapter and ethernet cable. Love it so far.

Now I have noticed that the OS has already g++, so it is possible to just write in VI simple C++ code, and compile it to run it directly from console (which is great for me).

Altho, it does not seem possible to do the same in cloud9....or I do not know how to do it.

I am planning to write code with the board attached to my computer, so I can just write code as usual and then move the source on the board and compile there (or do everything on my machine and just send the compiled program to the board...still experimenting here); but there will be some cases where I will be on the go, and would just power the board and work on it without a computer (I have ordered a lcd cape for this purpose).

VI is fine for simple code, but if you gotta code something more demanding, using VI would be a real pain, so I am trying to achieve productivity without burn my patience :)

In the end, I would like to have a better editor than VI, and also would love to use an IDE instead than just using text editors without code completion, breakpoints, step by step instructions and so on...so I thought that cloud9 may work, since I just need to run the browser directly on the BeagleBone and I can code and compile on the go without a computer.

Is this possible? Is there another way to accomplish what I need? I am pretty sure that if I install on the Angstrom release Eclipse, and try to use it; the board will just be too slow to run it,

Thanks in advance for any pointer! 

[mmk...@yahoo.co.uk]

[Karl Longen]

Guess it is a matter of preferences in the end...I trust more Oracle stuff than Microsoft.

Memacs is able to do as you described; you can write macro; altho you are still tied to a debugger to debug an application; and the lack of many facilities makes you wonder why you hate yourself so much, to use a textual environment instead of a full graphical IDE...if you are in a pinch then it may work, but for any daily job, I would not rely on it.

I think that a text editor is the base block for an IDE; then it is a matter of putting some buttons to run the build and run commands; but the hard part is all the translation from pure textual symbols to something more clean, when you are debugging. Technically you can script almost all the functions of gdb, but it is slow as hell. 

I believe that there is room for a full IDE on the BB; especially if you consider that stuff like Storm C was running on Pc and Amiga computers, which had 14 Mhz processor and barely a mb or 2 of ram

http://www.haage-partner.de/amiga/storm/sc_ft_e.htm#StormC1

[Karl Longen]

Mike,

You may want to try to read the posts that were made; you will find everything you need.

Just scroll up, you will find the link to youtube videos and some other link posted by other users.

Google is also your friend; the first 5 top results will show you all that you need to know. Especially if you follow the channels on Youtube; you will find plenty of GPIO examples.

BTW there is no debate about Eclipse...you probably just skimmed the posts here

[William Hermans]

You can find any old Eclipse howto that walks through setting up some form of a GCC toolchain in it. All the various tools are going to be named similar from toolchain to toolchain. The important part is knowing what settings to use with each tool ( compiler / linker etc ). The best thing here is to get a book on GCC( there are a few free online, findable with google ), and start reading. I know we al get impatient and do not want to invest a huge amount of time into something like this. However, you really need to know this information, and once learned it will apply to any GCC based compiler.

If you are going the cross compile route you may want to consider using a linaro toolchain. This should simplify setup considerably. Then later as you understand moreyou can either make adjustments to this toolchain, or switch out completely without too much effort.

As for the Eclipse "debate". There really is none. I like the IDE a lot ( as in how it looks, configurability etc ), but i refuse to use anything JRE related. That is personal, and I do not expect / require anyone else to agree / understand. Eclipse certainly is a top notch IDE.

--

[csu...@idapl.in]

can anyone help me in how to setup codelite on beaglebone directy

thanks in advance

sumik

 

[David Goodenough]

If you are running Debian:-

apt-get install codelite codelite-plugins

You will either need to be root to do this or use sudo if that is set up.

David

[bris...@yahoo.com.au]

I avoid using vi as much as I can so if I'm doing some simple testing of code on the bbb, I use the editor built in to mc (midnight commander). I'll have that open in one vc, run make in another and test the program in a 3rd. For debugging on the bbb I use cgdb which is a bit better than just the command line of gdb.  

[William Hermans]

ug, midnight commander reminds me of the old dosshell, which was fine, for 1994 . . .

Now days we have wonderful technologies such as Samba, NFS, and syntax highlighting editors. So we can do "weird" things like:

boot our dev boards via NFS.

Share a sub directory of the NFS share out via Samba.

Write code on another system, via the Samba share, as if it were a local file.

Compile natively on the dev board.

Imagine that !

On Sun, Nov 16, 2014 at 3:30 AM, briselec via BeagleBoard <beagl...@googlegroups.com> wrote:

I avoid using vi as much as I can so if I'm doing some simple testing of code on the bbb, I use the editor built in to mc (midnight commander). I'll have that open in one vc, run make in another and test the program in a 3rd. For debugging on the bbb I use cgdb which is a bit better than just the command line of gdb.  

--

[Barry Day]

with mc I can connect to another machine, edit remote files, move files between machines, peek inside and expand compressed files, etc, all without typing anything on a command line. And it's editor has syntax highlighting. 

[c...@isbd.net]

'Barry Day' via BeagleBoard <beagl...@googlegroups.com> wrote:
> [-- multipart/alternative, encoding 7bit, 70 lines --]
>
> [-- text/plain, encoding 7bit, charset: UTF-8, 32 lines --]

>
> between machines, peek inside and expand compressed files, etc, all without
> typing anything on a command line. And it's editor has syntax
>

... and why is that an advantage? :-)

--
Chris Green
·

[Sumik C]

hello david,

when i run apt-get install codelite codelite-plugins it throws and error saying codelite not found

--
For more options, visit http://beagleboard.org/discuss
---

You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/6lis7cZcTKg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.