On Wed, 27 Nov 2013, Phil Dibowitz wrote: >> So it looks like we deterine firmware based on a value of "Firmware_Main" >> inside a "TYPE" tag in the Data.xml - but neither of those tags are in the >> firmware file I got from the website. >> >> Looking at the file, best I can see is, in the COMPLETEPOSTOPTIONS, there's a >> PATH of EasyZapper/New/ProcUpgradeFirmware/Upgrade_Receive_Complete.asp >> >> I'll look into fixing this in the next few days. > > Attached is a patch.
Works fine on a 688 firmware update, so this seems fine to me. Signed-off-by: Scott Talbert <s...@techie.net> > I would rather have put the const in xml_headers.h, but I had weird problems > with this. Even though xml_headers.h is protected with the standard: > > #ifndef XML_HEADERS_H > #define XML_HEADERS_H > > If I included it from operationfile.cpp, I got duplicate define errors when > libtool tried to link each of it's object files together. So I left it in > operationsfile.cpp. Thoughts welcome. I think that is because those variables in xml_headers are technically global variables, so when they get included in multiple files, they cause duplicate definition errors when linked together. There are a few different ways we could work around this, but I'm not sure it is worth bothering. See this for more info: http://stackoverflow.com/questions/9049320/linking-issue-with-multiple-definition-of-compilation-error Scott ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel