A work around for Linux users

[Scimor5]

compiling in a terminal is really easy. for c++ programs using g++ and its arguments correctly takes care of everything.

g++ -o myProgram thing.cpp main.cpp

This command compiles and links the code files
"thing.cpp" and "main.cpp" together into the executable program called
"myProgram".

other things to worry about are libraries

-I : Sets the path to the include files.
-L : Sets the path to the libraries.
-l : Use this library (eg. -lm to use libmath.so, -lpthread to use libpthread.so)

You can have multiple -I, -L and -l entries.
So, your final command should look like this:

g++ -o myProgram thing.cpp main.cpp -I /path/to/includes -L /path/to/libraries -l library1 -l library2

info about libraries can be found with the pkgconfig command.

[theNerd]

Originally Posted by Scimor5

compiling in a terminal is really easy. for c++ programs using g++ and its arguments correctly takes care of everything.

g++ -o myProgram thing.cpp main.cpp

This command compiles and links the code files
"thing.cpp" and "main.cpp" together into the executable program called
"myProgram".

other things to worry about are libraries

-I : Sets the path to the include files.
-L : Sets the path to the libraries.
-l : Use this library (eg. -lm to use libmath.so, -lpthread to use libpthread.so)

You can have multiple -I, -L and -l entries.
So, your final command should look like this:

g++ -o myProgram thing.cpp main.cpp -I /path/to/includes -L /path/to/libraries -l library1 -l library2

info about libraries can be found with the pkgconfig command.

Haha! You have no idea how happy I am to have found a c++ person who knows about libraries . I used to be a Java programmer - still am - but now I would like to make c++ my core language seen that I'm going to need it a ton in college. Could you send me links to resources that greatly aided you in learning c++? and could I private message you with questions as I go through my learning curve?

[Scimor5]

Originally Posted by theNerd

Haha! You have no idea how happy I am to have found a c++ person who knows about libraries . I used to be a Java programmer - still am - but now I would like to make c++ my core language seen that I'm going to need it a ton in college. Could you send me links to resources that greatly aided you in learning c++? and could I private message you with questions as I go through my learning curve?

sure you can PM me all you like. for the most part i learned by googling what i needed at the time. Lots of trial and error. the only specific resource i recommend is this http://www.amazon.com/C-Pocket-Refer...2730753&sr=8-3 it's purely an outline of every command and bit of syntax, no tutorials. its for when you remember your supposed to use something, but don't remember how to use it, or you know this command exists in java, and want to see how to use the c++ equivalent. c++ isn't very hard to learn especially if your coming from a different programming language.

[Kevin Wang]

I put this together quickly to see what a terminal-based FRC IDE would look like. It's Vim and ant in tmux.

http://i42.tinypic.com/wjfa7b.png

Vim is running NERDtree on the left and the bottom window is zsh running 'ant deploy'.

[theNerd]

Wow! I like it! Would you guys happen to know where the wpilib is installed on a unix based system? ..... specifically Ubuntu

[alberth]

The biggest hurdle for Linux users is the FRC Driver Station. Sure, you can definitely program on any OS, but to control the robot itself... I faintly recall someone working on a portable, Python version of the driver station (barebones).

As for IDE, I'm still a GUI fan (I have an interesting aversion to vim). Nevertheless, I like my IDEs light - I use Geany for the majority of my code editing. (For Windows users, this is an amazing counterpart to Notepad++!)

I'm not sure how C/C++ can be compiled on Linux, simply because what you compile might not be compatible with the cRIO. When you compile something, you are usually compiling it for the current system. Most compilers compile for x86, which I'm 99% sure isn't the cRIO's processor!

If you want to, you can find the cRIO's processor target, and then build the GCC cross compiler for that particular processor target. (I have a few BASH scripts to do that - if you're interested in attempting this, free free to ask) Even then, you will also need the FRC specific headers to make things work.

It's hard, but it's possible!

EDIT: Based on the screenshot found here (my team programs in Java, not C/C++), it looks like the processor is a MPC5200 processor or similar. (This one is based on a PowerPC CPU core.) Happy hacking!

[andreboos]

I'm surprised nobody has brought this up yet: UCPP by nikitakit is a decent way to build on Linux or Mac.

Last year I used a custom makefile to compile C++ code for the robot, but it was incompatible with this year's version of WPILib, so I switched to UCPP. Now I can program, compile, and deploy from emacs.

[StevenB]

Originally Posted by theNerd

Wow! I like it! Would you guys happen to know where the wpilib is installed on a unix based system? ..... specifically Ubuntu

I don't have Netbeans installed right now, but my best guess is ~/.netbeans/plugins or something like that. You don't need root to install the plugin, so it's got to be somewhere in your home directory. If you just need the files, you can download them from FIRSTForge and unzip the archive yourself.

PS, locate is your friend.

[Kevin Wang]

Originally Posted by theNerd

Wow! I like it! Would you guys happen to know where the wpilib is installed on a unix based system? ..... specifically Ubuntu

I believe it's somewhere in ~/sunspotfrcsdk.

[Slix]

It'd be nice to be able to do all FRC programming tasks in Linux. Unfortunately, the LabVIEW-based Driver's Station, cRio Imaging Tool, and others make that difficult.

I know someone was working on a Driver's Station without these restrictions. What about the others? Could the imaging tool's functionality be reimplemented in some cross-platform way?

[techhelpbb]

Originally Posted by Slix

It'd be nice to be able to do all FRC programming tasks in Linux. Unfortunately, the LabVIEW-based Driver's Station, cRio Imaging Tool, and others make that difficult.

I know someone was working on a Driver's Station without these restrictions. What about the others? Could the imaging tool's functionality be reimplemented in some cross-platform way?

For just the build environment you could create a build environment in Windows you RDP to and drop your source on through a network share.

All you need is a real license of Windows XP Professional, if you use XP Home you can use VNC.

You could also put the whole thing in a VMWare, Xen or KVM virtual machine and then don't even need more harware (haven't tried this in a while but it should work).

I know my team does most of it's development in Eclipse with Java on Linux and Mac OSX. They tried to port the driver's station with some success. However, even if you create that code I'm not convinced it's entirely legal for competition use without specific approval.

[Earnesterin]

Earlier this week, we reported how the Free Agent range had difficulty using the Linux operating system due to the power management system.
A Seagate diskspinner called Nathan Papadopulos said that all Seagate and Maxtor branded external storage drives feature a power management that places the drive into a sleep mode after 15 minutes of inactivity.

[techhelpbb]

Originally Posted by Earnesterin

Earlier this week, we reported how the Free Agent range had difficulty using the Linux operating system due to the power management system.
A Seagate diskspinner called Nathan Papadopulos said that all Seagate and Maxtor branded external storage drives feature a power management that places the drive into a sleep mode after 15 minutes of inactivity.

With the Seagate utilities you can change the relevant settings.

Otherwise Vixie cron up a job to write or touch a file on the mounted volume.

You can also change the threshold of the write cache to flush more frequently or less frequently (in Linux you can delay the writes for 24 hours I do it all the time, just remember if you don't flush before you loose power your data is gone). Flush more frequently you keep your data and keep the drive awake (especially if you use a journaling partition). Flush less frequently you don't care if the drive sleeps, but you might loose your data.

Also, the problem is not confined to Linux. The power management on the Seagate Free Agents is especially aggressive and can shorten the drive life even in Windows. I'd recommened tinkering with it if you leave the drive connected for long periods of time.

If you need more assistance on how to do this please let me know.