Hi,
It works, starts anyway. But we need some sample bas files (you know me I use
C!).
If the editor selector box, you need to add a option to select a file with no
extension. You see linux is kinda short in that respect, executables don't need
extensions. Tcl has a var for os type somewhere.
For ubuntu you can default to /usr/bin/gedit
I am also using ubuntu.
linux support
-
- Posts: 1462
- Joined: Fri Oct 19, 2012 5:11 am
Re: linux support
jmrobert5 wrote:
>
>
> Hi,
>
> It works, starts anyway. But we need some sample bas files (you know
> me I use C!).
>
> If the editor selector box, you need to add a option to select a file
> with no extension. You see linux is kinda short in that respect,
> executables don't need extensions. Tcl has a var for os type somewhere.
>
> For ubuntu you can default to /usr/bin/gedit
>
A lot of Linux utilities use the EDITOR environment variable for this
purpose.
http://en.wikibooks.org/wiki/Guide_to_U ... les#EDITOR
If possible, it would be a nice feature to have the default set to that.
Unfortunately there isn't a universal editor across distros or even
within a distro.
Jim
>
>
> Hi,
>
> It works, starts anyway. But we need some sample bas files (you know
> me I use C!).
>
> If the editor selector box, you need to add a option to select a file
> with no extension. You see linux is kinda short in that respect,
> executables don't need extensions. Tcl has a var for os type somewhere.
>
> For ubuntu you can default to /usr/bin/gedit
>
A lot of Linux utilities use the EDITOR environment variable for this
purpose.
http://en.wikibooks.org/wiki/Guide_to_U ... les#EDITOR
If possible, it would be a nice feature to have the default set to that.
Unfortunately there isn't a universal editor across distros or even
within a distro.
Jim
-
- Posts: 1462
- Joined: Fri Oct 19, 2012 5:11 am
Re: linux support
> > It works, starts anyway. But we need some sample bas files (you know
> > me I use C!).
If there's any interest in C tools, MakeItC would be fairly easy to port, though
I have no experience setting up the ARM gcc compilers in linux-land. On the PC
we spent a lot of time trimming out the stuff not really needed in embedded work
(>220 MB down to much less than 20)
> http://en.wikibooks.org/wiki/Guide_to_U ... les#EDITOR
> If possible, it would be a nice feature to have the default set to that.
>
> Unfortunately there isn't a universal editor across distros or even
> within a distro.
The TclTerm tcl script could look for that.
Isn't there always vi? (as I go running off screaming NO...)
> > me I use C!).
If there's any interest in C tools, MakeItC would be fairly easy to port, though
I have no experience setting up the ARM gcc compilers in linux-land. On the PC
we spent a lot of time trimming out the stuff not really needed in embedded work
(>220 MB down to much less than 20)
> http://en.wikibooks.org/wiki/Guide_to_U ... les#EDITOR
> If possible, it would be a nice feature to have the default set to that.
>
> Unfortunately there isn't a universal editor across distros or even
> within a distro.
The TclTerm tcl script could look for that.
Isn't there always vi? (as I go running off screaming NO...)
-
- Posts: 1462
- Joined: Fri Oct 19, 2012 5:11 am
Re: linux support
basicnode wrote:
>
>
> > > It works, starts anyway. But we need some sample bas files (you know
> > > me I use C!).
>
> If there's any interest in C tools, MakeItC would be fairly easy to
> port, though I have no experience setting up the ARM gcc compilers in
> linux-land. On the PC we spent a lot of time trimming out the stuff
> not really needed in embedded work (>220 MB down to much less than 2
>
There isn't a .deb package for it, but from what I've read it's pretty
straight forward. You do have to build it from source.
>
>
> > http://en.wikibooks.org/wiki/Guide_to_U ... les#EDITOR
> > If possible, it would be a nice feature to have the default set to that.
> >
> > Unfortunately there isn't a universal editor across distros or even
> > within a distro.
>
> The TclTerm tcl script could look for that.
> Isn't there always vi? (as I go running off screaming NO...)
>
I think it's pretty universal, but I do recall doing a minimal install
of something a while back that didn't include vi. Battles to the death
have been fought over the vi vs emacs issue.
Since I'm on the vi
side, defaulting to vi isn't a problem for me.
Jim.
>
>
> > > It works, starts anyway. But we need some sample bas files (you know
> > > me I use C!).
>
> If there's any interest in C tools, MakeItC would be fairly easy to
> port, though I have no experience setting up the ARM gcc compilers in
> linux-land. On the PC we spent a lot of time trimming out the stuff
> not really needed in embedded work (>220 MB down to much less than 2
>
There isn't a .deb package for it, but from what I've read it's pretty
straight forward. You do have to build it from source.
>
>
> > http://en.wikibooks.org/wiki/Guide_to_U ... les#EDITOR
> > If possible, it would be a nice feature to have the default set to that.
> >
> > Unfortunately there isn't a universal editor across distros or even
> > within a distro.
>
> The TclTerm tcl script could look for that.
> Isn't there always vi? (as I go running off screaming NO...)
>
I think it's pretty universal, but I do recall doing a minimal install
of something a while back that didn't include vi. Battles to the death
have been fought over the vi vs emacs issue.

side, defaulting to vi isn't a problem for me.
Jim.
-
- Posts: 1462
- Joined: Fri Oct 19, 2012 5:11 am
Re: linux support
EDITOR is not set by default in FedoraCore 8 which I have here at work. In any
case the real issue was that the editor dialog is expecting a .exe file
extension.
IF your system is using normal gcc command stuff, consider simply having us
download codesourcery toolchain or yagarto toolchain.
Both are already integrated to Eclipse et al, both already set for
linux+arm+openocd. Just need to figure how to add your lib set.
There was a script called 'crosstool' that I used long ago to make our PPC405
crosscompiler.
You might check with the yahoo LPC2000 group as well for toolchain
recommendations.
case the real issue was that the editor dialog is expecting a .exe file
extension.
IF your system is using normal gcc command stuff, consider simply having us
download codesourcery toolchain or yagarto toolchain.
Both are already integrated to Eclipse et al, both already set for
linux+arm+openocd. Just need to figure how to add your lib set.
There was a script called 'crosstool' that I used long ago to make our PPC405
crosscompiler.
You might check with the yahoo LPC2000 group as well for toolchain
recommendations.
-
- Posts: 1462
- Joined: Fri Oct 19, 2012 5:11 am
Re: linux support
On a short search, eclipse or codeblocks with the codesourcery arm toolchain is
the easiest to setup.
yagarto and winarm are designed to be installed on win32.
Since haven't done this yet, some sort of package for eclipse might be a neat
way to do it.
Also, wild idea, but the real beauty of Arduino IDE - is the easy way they
integrate user libraries into the build tool/system.
the easiest to setup.
yagarto and winarm are designed to be installed on win32.
Since haven't done this yet, some sort of package for eclipse might be a neat
way to do it.
Also, wild idea, but the real beauty of Arduino IDE - is the easy way they
integrate user libraries into the build tool/system.
Re: linux support
We have a version of BASICtools running on Linux
follow the link - http://www.coridiumcorp.com/forum/viewt ... f=9&t=1003
follow the link - http://www.coridiumcorp.com/forum/viewt ... f=9&t=1003