<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic FPGA reference typedef causes build problem in Continuous Integration</title>
    <link>https://ni.lithium.com/t5/Continuous-Integration/FPGA-reference-typedef-causes-build-problem/m-p/3392606#M4</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is just an FYI based on a recent experience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a class "FPGA Class X" that has as its private data an FPGA VI Reference. Prior to encapsulating the FPGA VI reference in a class it was a front panel item and I made it a typedef so that I could change the bitfile/interface to the fpga across the entire program. Following putting the VI reference within the class I no longer need to use a typedef because I have a single point that I can go to in order to change the VI (the private data item).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In LabVIEW 2014 I had a probelm with building the project that used the class would cause a crash in the build environment. The build server would generally chech out a clean copy of the repo and build. Then the build would fail due to a LabVIEW crash during the build. I could fix the build server by opening the project on the remote computer and opening and building the project and then pushing the changes to the repo. Not something you want to do frequently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fix was to disconnect the control from the typedef.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just something to be aware of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Casey&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 03 Jan 2015 00:19:24 GMT</pubDate>
    <dc:creator>CaseyLamers1</dc:creator>
    <dc:date>2015-01-03T00:19:24Z</dc:date>
    <item>
      <title>FPGA reference typedef causes build problem</title>
      <link>https://ni.lithium.com/t5/Continuous-Integration/FPGA-reference-typedef-causes-build-problem/m-p/3392606#M4</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is just an FYI based on a recent experience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a class "FPGA Class X" that has as its private data an FPGA VI Reference. Prior to encapsulating the FPGA VI reference in a class it was a front panel item and I made it a typedef so that I could change the bitfile/interface to the fpga across the entire program. Following putting the VI reference within the class I no longer need to use a typedef because I have a single point that I can go to in order to change the VI (the private data item).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In LabVIEW 2014 I had a probelm with building the project that used the class would cause a crash in the build environment. The build server would generally chech out a clean copy of the repo and build. Then the build would fail due to a LabVIEW crash during the build. I could fix the build server by opening the project on the remote computer and opening and building the project and then pushing the changes to the repo. Not something you want to do frequently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fix was to disconnect the control from the typedef.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just something to be aware of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Casey&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Jan 2015 00:19:24 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Continuous-Integration/FPGA-reference-typedef-causes-build-problem/m-p/3392606#M4</guid>
      <dc:creator>CaseyLamers1</dc:creator>
      <dc:date>2015-01-03T00:19:24Z</dc:date>
    </item>
  </channel>
</rss>

