Leaderboard
Popular Content
Showing content with the highest reputation on 09/02/2011 in all areas
-
You can get that info from the project object: <img src="http://i.imgur.com/qNsTR.png" alt="" title="Hosted by imgur.com" /> (2011 snippet). Ton2 points
-
(Thumbs up for the extensive document). How would this work for legacy packages? One of the requirements is that you have a 'lava-compliant'-namespace. That's quite hard for the Code Capture Tool with an allready existing API. Ton1 point
-
To my knowledge (I'm not in the office to be able to check) on the LV FPGA install DVD there should be separate installers for two different versions of the Xilinx FPGA compiler. You should only need to installer the newer of these two for your specific FPGA target. I think starting with LV 2010 installing the compiler was separate from the LV FPGA module installation. http://www.ni.com/pdf/manuals/371572f.pdf1 point
-
Daklu, I believe you need the xilinx compile tools. It seems they have gotten a bit hidden since the release of 2011. Here's a link that (should) still work for 2010: http://joule.ni.com/nidu/cds/view/p/id/2592/lang/en1 point
-
If we are going to implement this, I wouldn't want it to be strict regarding the case, one of the reasons being that LabVIEW using %x formatter outputs uppercast hex-values. Regarding the SHA hashes, yes my intention is to offer that code in the OpenG package, however I haven't got time to write unit tests for the SHA and HMAC hashing, though I have a complete set of unit test's for AES cyper/decypher routines. Ton1 point