|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Anyone install windriver on linux yet?
I was just wondering if anyone has successfully installed WindRiver on a Linux machine yet?
My team hasn't gotten our software yet, as we just paid right before the deadline. I am particular interested in it successfully being installed on Debian based systems, however any Linux success is relevant too. Please post any failures, confusion, and especially success stories. also I've heard there is a version of labview that runs on linux now, anyone using that? -Andrew (keen101) |
|
#2
|
|||
|
|||
|
Re: Anyone install windriver on linux yet?
I have it installed with ubuntu as host OS. It is not "supported" but seems to be fine. My team has not received the kit yet, but will see how it goes then.
Before I installed windriver workbench, I looked into building a GNU toolchain. Unfortunately I was not able to get gcc to completely build. For those that want to continue on that route, you will need to download headers for vxworks. National instrument provides this for vxworks 6.1 and 6.3 (no idea what is on the controller we get from first). http://zone.ni.com/devzone/cda/tut/p/id/5694 You can build binutils with the target powerpc-wrs-vxworks just fine. Trying to build gcc I had major issues relating to the headers. Another alternative would be to use the compiler provided in workbench and create some makefiles. Not my preferred route, but it should work okay. |
|
#3
|
|||
|
|||
|
Re: Anyone install windriver on linux yet?
Quote:
As for me, as soon as I get my hands on the compiler suite, I am going to first install it under WINE and play with it that way. After I get it working under Wine with Makefiles, I'll see about running it naively if performance is actually a problem. No sense in spending a couple of days in order to shave 1 second off compile time. Does anyone know much about how the Debugger works? If it uses standard gdb network protocols, we might be able to just use gdb or one of it's graphical interfaces like ddd to be able to debug code under Linux. Along those lines, does anyone know where to get the compiler suite besides from the kit? |
|
#4
|
||||
|
||||
|
Re: Anyone install windriver on linux yet?
Quote:
I was only able to get it using the CD or by downloading their evaluation product. It may be based on GCC but AKAIK it is not free. |
|
#5
|
||||
|
||||
|
Re: Anyone install windriver on linux yet?
Cool. I'm anxious to hear more success stories with Linux and windriver. I don't think it will work very well under WINE, but that's my opinion.
on another note... i successfully got Labview to work on Ubuntu Linux. The price is pretty steep, so most teams won't be able to afford it. Our team really can't afford it either if you want to know the truth. Anyway, the hardest part was converting the .RPM packages to .DEB files, but i sucessfully did it with "alien". feel free to email me with specific questions regarding Labview under Ubuntu. I can even try to help look for some sort of discounts if you are really drooling to get labview working under ubuntu. It is much faster under linux. ![]() Last edited by keen101 : 11-12-2008 at 06:02. |
|
#6
|
||||
|
||||
|
Re: Anyone install windriver on linux yet?
Quote:
|
|
#7
|
||||
|
||||
|
Re: Anyone install windriver on linux yet?
Quote:
But, i found this today so we will request it. http://www.chiefdelphi.com/forums/sh...56&postcount=9 I haven't tried any of the Vi's yet, and if NI hadn't been willing to ship Linux versions by request, I'd probably have never been able to manage getting everything to work. As i understand it many things are different in the FRC version, especially the Real-Time module and some other drivers. |
|
#8
|
||||
|
||||
|
Re: Anyone install windriver on linux yet?
Also, no matter what operating system you're running, they're having issues with a bug in the FRC version that modifies a file shared between all LabView installations on the machine incorrectly, therefore resulting in data that's unusable by all installations. Uninstall all other installations BEFORE you install the FRC version.
Sweet, I definitely need to look into getting one of them Linux installer CD's. I'm so glad NI is so cross-platform with everything, it makes everybody love them more! Also, where did you get the evaluation version of LabView for Linux? I haven't been able to find one anywhere. Last edited by daltore : 15-12-2008 at 23:43. |
|
#9
|
||||
|
||||
|
Re: Anyone install windriver on linux yet?
Quote:
I went back to one page i thought i had been on, but can only find the windows trial version. Weird. I don't know, i was doing a lot of googling at the time, and was trying to find anything that had to do with labview and linux. Oh, well. It doesn't matter anyway i suppose. Does anyone know how to obtain the Linux version of WindRiver? Is it included on the software DVD? Or do we have to request it from FRC team support? |
|
#10
|
|||
|
|||
|
Re: Anyone install windriver on linux yet?
Quote:
Though there is a native Linux version of LabVIEW, if I've understood the situation correctly, in order to program for a CompactRIO target you need to have the LabVIEW Real-time Module, which is Windows-only. |
|
#11
|
|||
|
|||
|
Re: Anyone install windriver on linux yet?
I just spent some time fiddling with it, and it's of note that the redistributable compiler for VxWorks 6.3 (mentioned further up) runs and successfully compiles the example code that comes in the zip provided that you set the proper environment variables in the Wine registry.
The following is a modified version of the Makefile from the example code that allows it to be built through Eclipse on Linux: Code:
# edit these as needed to fit your setup WIND_BASE = "c:\gccdist\WindRiver\vxworks-6.3" WINECMD = wine # These variables control the compiler and linker flags. Change them as # appropriate. DEBUG_MODE = 0 ADDED_CFLAGS = ifeq ($(DEBUG_MODE),1) OBJ_DIR := PPC603gnu_DEBUG CFLAGS = -g -mlongcall else OBJ_DIR := PPC603gnu CFLAGS = -Os -fstrength-reduce -fno-builtin -fno-strict-aliasing -mlongcall endif LINKFLAGS = $(CFLAGS) LIBPATH = # List all the *compiled* object files here, under the OBJ_DIR # directory. Make will automatically locate the source file and # compile it. OBJECTS := $(OBJ_DIR)/example.o # This is the name of the output shared library. PROJECT_TARGETS := $(OBJ_DIR)/example.out # If you have other VxWorks .a files to reference, list them here. LIBS = LIBPATH = # Everything after this line should not need to be modified for # basic compilation. However, significant changes to the build structure # will probably involve modifying these lines. CPU = PPC603 TOOL_FAMILY = gnu TOOL = gnu CC_ARCH_SPEC = -mcpu=603 -mstrict-align -mno-implicit-fp IDE_INCLUDES = -I$(WIND_BASE)/target/h -I$(WIND_BASE)/target/h/wrn/coreip # This basic rule compiles a .c file into a .o file. It can be adapted to # all other source files that gcc can compile, including assembly (.s) and # C++ (.cpp, .cc, .C, .cxx) files. To enable support for those extensions, # copy this rule and modify its extension and compile flags for the # required source file type. $(OBJ_DIR)/%.o : %.c $(WINECMD) ccppc $(CFLAGS) $(CC_ARCH_SPEC) -ansi -Wall -MD -MP $(ADDED_CFLAGS) $(IDE_INCLUDES) $(ADDED_INCLUDES) -DCPU=$(CPU) -DTOOL_FAMILY=$(TOOL_FAMILY) -DTOOL=$(TOOL) -D_WRS_KERNEL $(DEFINES) -o "$@" -c "$<" # Adapted rule for .cpp files $(OBJ_DIR)/%.o : %.cpp $(WINECMD) c++ppc $(CFLAGS) $(CC_ARCH_SPEC) -ansi -Wall -MD -MP $(ADDED_CFLAGS) $(IDE_INCLUDES) $(ADDED_INCLUDES) -DCPU=$(CPU) -DTOOL_FAMILY=$(TOOL_FAMILY) -DTOOL=$(TOOL) -D_WRS_KERNEL $(DEFINES) -o "$@" -c "$<" all : check_objectdir $(PROJECT_TARGETS) $(PROJECT_TARGETS) : $(OBJECTS) rm -f "$@" ctdt.c;$(WINECMD) nmppc $(OBJECTS) | $(WINECMD) tclsh $(WIND_BASE)/host/resource/hutils/tcl/munch.tcl -c ppc > ctdt.c $(WINECMD) ccppc $(LINKFLAGS) $(CC_ARCH_SPEC) -fdollars-in-identifiers -Wall $(ADDED_CFLAGS) $(IDE_INCLUDES) $(ADDED_INCLUDES) -DCPU=$(CPU) -DTOOL_FAMILY=$(TOOL_FAMILY) -DTOOL=$(TOOL) -D_WRS_KERNEL $(DEFINES) -o ctdt.o -c ctdt.c $(WINECMD) ccppc -r -nostdlib -Wl,-X -T $(WIND_BASE)/target/h/tool/gnu/ldscripts/link.OUT -o "$@" $(OBJECTS) $(LIBPATH) $(LIBS) $(ADDED_LIBPATH) $(ADDED_LIBS) ctdt.o rm -f ctdt.c ctdt.o check_objectdir : @if [ ! -d "$(OBJ_DIR)" ]; then\ mkdir -p $(OBJ_DIR);\ fi clean : rm -f $(OBJECTS) $(PROJECT_TARGETS) $(wildcard $(OBJ_DIR)/*.unstripped) .DUMMY: check_objectdir clean I'll post back as I make progress. |
|
#12
|
||||
|
||||
|
Re: Anyone install windriver on linux yet?
Well, just requested a linux version of LabVIEW. Hopefully NI will send it....
Quote:
Keep me informed on any progress you make.Quote:
Quote:
If I made any comments about the Real-time module, it was that i am pretty sure the Real-time module on an everyday version of labview is very different from the FRC version. I think it's different because our cRIO's aren's standard cRIO's, they are custom built ones. |
|
#13
|
|||
|
|||
|
Re: Anyone install windriver on linux yet?
Quote:
Quote:
Quote:
Last edited by pogenwurst : 18-12-2008 at 08:45. Reason: BBCode fix |
|
#14
|
||||
|
||||
|
Re: Anyone install windriver on linux yet?
The links you provided don't prove anything. Most of the documentation from ni is for windows anyway. that doesn't mean mac and Linux versions don't exist.
i remember seeing a real time module .rpm file with the linux tutorial. I could email it to you if you want to look at it. (if i still have it) But, i have the feeling you just feel like arguing. |
|
#15
|
|||
|
|||
|
Re: Anyone install windriver on linux yet?
Quote:
I suspect that the RPM you're referring to is labview85-rte-8.5.1-1.i386.rpm. Unless I'm terribly mistaken RTE in this case stands for the LabVIEW Run Time Engine, which is used to deploy VIs on computers that don't have the full development system installed. In any case, I will say no more, and wish you the best of luck with your search. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Trouble booting Linux from hard drive after CD install | edomus | Technical Discussion | 2 | 01-11-2004 08:03 |
| Anyone registered yet? | Gary Dillard | General Forum | 54 | 20-10-2004 01:22 |
| anyone know how to install gallery on a webserver? | Greg Needel | Website Design/Showcase | 5 | 19-08-2004 14:40 |
| anyone at epcot yet? | Jgreenwd1 | Chit-Chat | 3 | 24-04-2002 18:26 |