[taichichuan]

FWIW, I don't use Workbench for much of my library development. I haven't been able to figure out how to generate a static library successfully in the tool. I'm sure it can be done, but I just haven't found the right project and sequence of steps.

So, it turns out that you can do all of the development "old school" if you're so inclined. The way it's done is to open a host shell from the Workbench menu bar. This opens at DOS box that has sourced the environment variables needed to run the tool from the command line. From there, Makefiles can be written to compile and build any code you want.

Now, this does not side step any licensing issues you may be having because Wind's version of the GNU compiler has a front end that checks the license before the GNU compiler actually starts to run. However, once you have the compiled code you can use it as a link target for other projects in or out of Workbench.

As for getting code onto the cRIO, filezilla works nicely. The cRIO is running an FTP server on port 21. If you open a connection to the cRIO and log in, you'll see the Flash file system on the cRIO. In order to automatically start your code, you need to copy it to the cRIO as FRC_UserProgram.out (or something obvious like that -- I dont' have the cRIO in front of me and it's late, so my memory is failing me). The FTP is essentially what the "Deploy Code" button is doing in Workbench.

Now, I share these techniques with you in the hope that it will "de-mystify" how the FIRST control system works. But, as GVarndell pointed out, if you're having trouble with Workbench, then working outside of Workbench will likely not make anything any easier for you. FWIW, I've also been successful in generating code in Linux for the cRIO. But, that's a whole other kettle of fish and not for the faint of heart.

HTH,

Mike