2010-06-10T04:18:44 *** tclarke has joined #opticks 2010-06-10T04:18:44 *** ChanServ sets mode: +o tclarke 2010-06-10T04:23:01 *** goffena has joined #opticks 2010-06-10T04:47:35 *** mconsidi has quit IRC 2010-06-10T04:56:14 *** sbmiller has joined #opticks 2010-06-10T05:44:50 *** dsulgrov has joined #opticks 2010-06-10T06:06:20 *** kstreith has joined #opticks 2010-06-10T06:06:20 *** ChanServ sets mode: +o kstreith 2010-06-10T08:25:13 *** lonzo has joined #opticks 2010-06-10T08:26:15 I have a question. I've compiled the code and I have warnings complaining about the pluginutilities.pdb file. When I build the tutorials no errors occur and a .dll file is created, but it does not appear in opticks after I move it to the plug-ins folder. Any ideas? 2010-06-10T08:29:12 sounds like you are building in debug mode and dropping the dll into a release mode Opticks installation? 2010-06-10T08:31:17 We're dropping the file into the plug-ins directory for Opticks. Should we be doing something differently? 2010-06-10T08:31:27 make sure you are building the dll in the same release configuration (32-bit or 64-bit) as the installed Opticks and try again 2010-06-10T08:31:38 We are. 2010-06-10T08:31:47 the warnings are likely indicating that the release pdf doesn't exist 2010-06-10T08:31:49 you can ignore them 2010-06-10T08:31:51 pdb that is 2010-06-10T08:33:20 you would need to close and restart Opticks if you added the dll while Opticks was running 2010-06-10T08:33:28 it's because the pdbs were generated when we built the dlls but are not included in the sdk 2010-06-10T08:33:33 the pdbs are quite large and don't give you much for release mode 2010-06-10T08:33:33 . 2010-06-10T08:33:46 I closed Opticks and reopened it and the plug-in still did not appear. 2010-06-10T08:33:55 do you see anything in the Message Log about plug-ins failing to load 2010-06-10T08:35:18 that may give you additional information..if the error is there but does not provide much information, you can load the plug-in in the depends.exe tool that comes with Visual Studio 2010-06-10T08:35:25 it will tell you if there are any dependent DLLs which can't be located 2010-06-10T08:35:33 Yes. It says "This file wasa not recognized by an importer. Please enter the requested infromation to load this file using the Generic Importer." 2010-06-10T08:35:43 that's not a plug-in load message...that's an importer message 2010-06-10T08:35:48 you are looking for something indicating that the plug-in did not load 2010-06-10T08:36:02 it will likely be the 2nd or 3rd entry in the message log 2010-06-10T08:37:29 It says pluginerror 2010-06-10T08:37:34 expand the error (the + to the left of the error) for more information 2010-06-10T08:38:14 Error opening DLL in Plugins folder: %1 is not a valid Win32 application\ 2010-06-10T08:39:54 it sounds like your plug-in dll may be missing a manifest 2010-06-10T08:40:23 in visual studio, select File->Open->File 2010-06-10T08:40:25 select the plug-in dll 2010-06-10T08:41:46 You'll see an entry called RT_MANIFEST with a 2 underneath 2010-06-10T08:41:48 double click the 2 2010-06-10T08:41:53 you'll see some XML on the right hand side 2010-06-10T08:42:03 find an entry with the name Microsoft.VC80.CRT 2010-06-10T08:42:19 make sure the version in 8.0.50727.762 and the processorArchitecture matches the opticks version (32-bit or 64-bit) you have installed 2010-06-10T08:42:31 it'll either be x86 or amd64 2010-06-10T08:44:02 open the .dll file in visual studio? 2010-06-10T08:44:40 yes, it will let you look at the embedded manifest information 2010-06-10T08:45:53 it says that i cannot open the file with the selected editor 2010-06-10T08:46:01 did you use File->Open->File or did you drag and drop? 2010-06-10T08:46:08 file open file 2010-06-10T08:46:15 what version of visual studio are you using? professional or express? 2010-06-10T08:46:17 express 2010-06-10T08:46:24 what might be the problem... 2010-06-10T08:46:32 open a command prompt with the visual studio environment loaded (should be in the program group for VS) 2010-06-10T08:46:42 and run mt.exe on your .dll, use the following command line 2010-06-10T08:46:51 mt.exe -inputresource:plugin.dll;#2 -out:plugin.manifest 2010-06-10T08:48:01 you should get a plugin.manifest file with the xml I mentioned above 2010-06-10T08:52:48 it says Manifest Tool Version 5.2.3790.2075 2010-06-10T08:54:20 in the .manifest file? 2010-06-10T08:55:05 you need to look in the file it generates 2010-06-10T08:55:23 No. The three lines appeared with copyright information including that line. Where is the manifest located? Nothing has appeared in the directory with the dll file. 2010-06-10T08:55:30 it should be in the directory you run mt.exe in 2010-06-10T08:58:37 I dont see the manifest file in that directory. 2010-06-10T09:03:08 you can specify a different on then...the -out:"c:\path\to\directory\plugin.manifest" 2010-06-10T09:05:27 its there now 2010-06-10T09:05:37 ok, look in that file for an assemblyIdentity line 2010-06-10T09:05:45 what are the "name" "version" and "processorArchitecture" values? 2010-06-10T09:07:24 name = microsoft.vc80.debugcrt version = 8.0.50727.4053 processArch = x86 2010-06-10T09:07:35 ok, you're dropping this in an opticks install? 2010-06-10T09:07:44 there are two assembly identifiers and they have two different version numbers 2010-06-10T09:07:56 the other is 8.0.50727.762 2010-06-10T09:08:00 are you building this plugin in debug mode or release mode? 2010-06-10T09:08:04 debug 2010-06-10T09:08:12 are you using the debug Opticks binaries that come with the SDK or are you using an Opticks install? 2010-06-10T09:09:41 The SDK 2010-06-10T09:09:58 it sounds like there is a mismatch somewhere in there as that error often indicates you are mixing debug mode and release mode binaries 2010-06-10T09:11:46 verify that you are using the debug build of Opticks....after that I'm going to refer you to kstreith who is our resident expert on DLL behavior...he is currently at lunch but should return shortly...you can eitherhang around this channel or send an email to dev@opticks.ballforge.net and I'll ask him to look into this when he returns 2010-06-10T09:14:04 Thanks and we will continue to hang on this channel for further help. 2010-06-10T09:35:32 *** rforehan has joined #opticks 2010-06-10T09:39:40 *** gmartin_cn has joined #opticks 2010-06-10T10:00:21 *** glenLarsen has joined #opticks 2010-06-10T10:00:49 hello, are there users or developers here? 2010-06-10T10:05:25 we are here 2010-06-10T10:06:35 however, we have a meeting in a few minutes so there might be a bit of a pause 2010-06-10T10:06:42 ok no problem 2010-06-10T10:08:47 kstreith is back...we've got a brief meeting but he'll be able to help you in a few more minutes 2010-06-10T10:08:53 ok thanks 2010-06-10T10:28:11 reading the previous conversation, be up to speed in a minute 2010-06-10T10:30:17 glenLarsen: developers mostly, but the main developers, so we can answer most user questions as well 2010-06-10T10:30:47 lonzo: can you put a copy of your built dll into the "Bin" folder (same folder as Opticks.exe that you are running) 2010-06-10T10:30:59 then start-up Dependency Walker (http://www.dependencywalker.com/) 2010-06-10T10:32:17 and drag-and-drop your plug-in dll (the one in the Bin folder) onto the running instance of Dependency Walker 2010-06-10T10:32:26 let me know if you see any "yellow" icons in the tree view on the left side of the application 2010-06-10T10:32:40 you specifically Want the Version 2.2.6000 for x86 version of Dependency Walker 2010-06-10T10:34:17 does the dependecy walker support windows 7 2010-06-10T10:36:43 yes 2010-06-10T10:38:54 *** gwelch has joined #opticks 2010-06-10T10:39:10 Hey people. I hope I'm not interrupting...pansharpening and atmospheric corrections, are these doable in opticks? It looks to me like all the components are there, I just don't know how to link them. 2010-06-10T10:39:17 yes i see a few yellow icons 2010-06-10T10:39:56 lonzo: which ones? do you mind saying? 2010-06-10T10:40:13 MSVCR80D.Dll QTCORED4.DLL QTGUID4.Dll XERCES-C_2_7D.DLL 2010-06-10T10:42:41 lonzo: did you build a 32-bit dll or 64-bit dll? 2010-06-10T10:42:47 32 bit 2010-06-10T10:42:55 glenLarsen: the Spectral Processing Extension (http://opticks.org/confluence/display/opticksExt/Spectral+Processing) does provide some algorithms that perform basic atmo correction 2010-06-10T10:43:13 glenLarsen: We have ELM (Emperical Line Method) and IARR (Internal Average Relative Reflectance) 2010-06-10T10:43:25 glenLarsen: those are both very basic atmo correction capabilities 2010-06-10T10:45:39 *** glenLarsen has quit IRC 2010-06-10T10:45:52 *** mconsidi has joined #opticks 2010-06-10T10:46:00 lonzo: is the plug-in dll in the "Bin" folder 2010-06-10T10:46:07 lonzo: when you drop it onto Dependency Walker 2010-06-10T10:46:12 lonzo: because those dlls you mentioned should be in the Bin folder along with Opticks.exe 2010-06-10T10:51:27 yes it is 2010-06-10T10:51:31 hmmmm, interesting... 2010-06-10T10:51:48 did you compile against our binaries for Qt and Xerces? 2010-06-10T10:51:54 or did you build those yourself? 2010-06-10T10:52:10 Yes I did 2010-06-10T10:52:28 yes to which one? 2010-06-10T10:52:34 I compiled against your binaries 2010-06-10T10:52:43 ok, good 2010-06-10T10:55:37 are you compiling any non-Opticks 3rd party dependencies? 2010-06-10T10:55:41 compiling against? 2010-06-10T10:55:47 don't need to know what they are 2010-06-10T10:55:49 just if you are 2010-06-10T10:55:58 No were not 2010-06-10T10:57:19 ok, more involved question 2010-06-10T10:57:24 Go to C:\Windows\WinSxS directory on your computer 2010-06-10T10:57:34 how many directories in there start with "x86_Microsoft.VC80.DebugCRT"? 2010-06-10T11:00:05 just one 2010-06-10T11:00:09 interesting 2010-06-10T11:00:19 what is the version number, it's farther down in the folder name, starts with 8.0. 2010-06-10T11:01:43 8.0.50727.4053 2010-06-10T11:02:03 that might be the problem 2010-06-10T11:02:05 let's dig a bit more 2010-06-10T11:02:21 Go to C:\Windows\WinSxS\Policies folder 2010-06-10T11:03:37 and then navigate into the *8.0.Microsoft.VC80.DebugCRT* directory (there should only be one) 2010-06-10T11:03:44 and then look for the *.policy file 2010-06-10T11:03:47 open that up in a text editor 2010-06-10T11:04:00 look for ? 2010-06-10T11:04:05 if you see one, can you tell what's in the oldVersion and what is in the newVersion? 2010-06-10T11:05:54 Im not seeing a policies folder 2010-06-10T11:06:21 alright, hold on 2010-06-10T11:08:00 can you search in C:\Windows folder for any *.policy files? 2010-06-10T11:08:17 just let me know how many you find 2010-06-10T11:12:09 Im not seeing any file that shows in that format... but I see folders with the word policy for ex. search-ms:displayname=Search%20Results%20in%20Windows&crumb=location:C%3A%5CWindows\x86_policy.1.0.microsoft.ink_31bf3856ad364e35_6.1.7600.16385_none_ac169bf8db6dc435 2010-06-10T11:12:47 i think you are encountering problems because you have Microsoft Security Vulnerability MS09-35 installed on your system 2010-06-10T11:12:55 this causes problems for a variety of C++ programs, Opticks included 2010-06-10T11:14:07 you can see my discussion about this issue in our mailing list archives 2010-06-10T11:14:07 https://opticks.ballforge.net/ds/viewMessage.do?dsForumId=31&dsMessageId=16138 2010-06-10T11:14:19 if you can, I would try and uninstall that 2010-06-10T11:16:09 Ok thanks for your time and help, I'll contact you guys if we have any more concerns. 2010-06-10T11:16:12 this problem will go away when we upgrade to Visual Studio 2010, which is scheduled for the 4.5.0 release 2010-06-10T11:16:44 Do you have an release date for this upgrade. 2010-06-10T11:17:04 November 2nd, 2010 2010-06-10T12:45:17 *** lonzo has quit IRC 2010-06-10T13:07:06 *** sbmiller has quit IRC 2010-06-10T13:21:33 *** goffena has quit IRC 2010-06-10T13:34:32 *** gwelch has quit IRC 2010-06-10T13:39:12 *** tclarke has quit IRC 2010-06-10T13:51:18 *** dsulgrov has quit IRC 2010-06-10T15:32:05 *** kstreith has quit IRC 2010-06-10T15:45:58 *** gmartin_cn_ has joined #opticks 2010-06-10T15:51:01 *** gmartin_cn has quit IRC 2010-06-10T15:51:01 *** gmartin_cn_ is now known as gmartin_cn 2010-06-10T19:38:47 *** gmartin_cn has quit IRC 2010-06-10T19:55:21 *** rforehan has quit IRC 2010-06-10T20:01:57 New news from nightlybuilds: Opticks4.4Dev-Nightly-Linux #24 (SUCCESS) 2010-06-10T23:39:07 New news from nightlybuilds: Opticks4.4Dev-Nightly-Solaris #23 (SUCCESS)