Jump to content

XML Toolkit Breaks my Win7 LV 2011 SP1 Build


Recommended Posts

For the last two days, I've been working through a problem wherein my project build .exe had somehow broken (the build had been working, but I made a number of changes around files/internet access/xml). I didn't see any problems running in the debugger, but when I built the application, I received a series of "The VI is not executable errors and a broken start button.


I've been in discussions with National Instruments concerning possible sources and was successively localizing the offending vis (this is a pretty big application) (including their own known bug workarounds ... no luck).


Bottom Line: If I build with your EasyXML (Generate and Parse), the final executable is broken. I can't perform a debug of the .exe (it crashes) and really have no visibility into the issues. If I conditionally disable the calls, then the application builds and runs. Again, no problems in the debugger.


I am using LabVIEW Professional 2011 SP1 on Windows 7.


Any ideas?

Link to comment
Share on other sites



What version of EasyXML are you using?


Can you send us an example project that produces a broken build?


This will help us reproduce and investigate the issue.


Also, any additional information/screenshots will be helpful.


Thank you.

Link to comment
Share on other sites



I'm using a full version of jki_lib_easyxml version 2.0-2.


The project is including all of the .vis and project is very large (52M), is there something specific that would help?


If I provide the built application with debugging enabled, would that be helpful (although it crashes for me).


I can also provide the (most recent) mass compile logs.



Link to comment
Share on other sites



I spent a day remove code modules from my broken application and adding functionality to a working build. No luck (after removing file/display/math VIs).


I mass compiled vi.lib and my application. No luck.


BUT I finally found out how to successfully build the application ... consistently. What I do is before every build I clear the compiled object cache. The first build after this clear always works. If I don't (clear the cache) the resulting executable is broken ... again with no builder errors.




Any ideas? I have a workaround, but this may come back to haunt me ... are there any utilities that can give me visibility into the final application build?



Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.