Re: [firebreath-dev] VS2012 Build

[Neil Griffiths]

Is it actually registering? Normally these problems are because you're linking to a dependency that can't be found.

I'd suggest getting Dependency Walker (http://www.dependencywalker.com/) and seeing whether it can find all the dependencies or not.

Good luck!

Neil

On Fri, May 31, 2013 at 2:38 PM, Chris Manning <vash...@gmail.com> wrote:

Hi all,

I recently built a new rig with Win8 and VS2012 Ultimate. This meant I had to update my version of firebreath so that I could continue developing in the new environment. After grabbing the latest stable build, I installed it locally and created a test project. I've used firebreath for quite some time, so I'm quite familiar with how it functions, but I can't seem to get the dll that compiles even from a test project to be recognized by any browser. In older versions, I would compile, then register the dll, and lastly I could open up chrome and visit a page with an embedded object of that particular mime-type.  With the latest version of firebreath, however, I cannot seem to get the browser to recognize the dll after registering it. Any ideas?

Additional information:

If you use a process monitor, you can see the command line that each Chrome process was launched with. This makes it easy to see whether or not the dll instance has been created when visiting a page with the particular mime-type. If I register a test project dll compiled on my old rig, using an old firebreath build for VS2010, it creates the dll instance and works properly. In the latest stable build, however, using VS2012 I am unable to get a test project dll (or any dll created using firebreath) recognized by the browser after registering it on the machine.

--
 
---
You received this message because you are subscribed to the Google Groups "firebreath-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebreath-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Chris Manning]

No complaints on registering from regsvr32. I used Dependency Walker and got complaints about SHCORE.dll, SHLWAPI.dll, EXT-MS-WIN-ADVAPI32-PSM-APP-L1-1-0.dll, and IEFRAME.dll.

Not sure what could be causing all of these issues, as I'm only compiling the test projects as they are created with the latest stable from Firebreath. It's not missing dependencies on my computer, as I can compile test projects from previous stable builds in VS2010 on my laptop, bring over the DLL's, register them, and run them just fine on this computer. Something has changed from previous Firebreath iterations and it is causing issues on this setup.

[Neil Griffiths]

So Dependency Walker finds issues with dependencies and then you go on to claim that it's not a problem with dependencies? Unfortunately the fact that it works with VS2010 just implies that you have all of the VS2010 dependencies installed.

The only dependency warning I know is safe for you to ignore is IESHIMS.DLL. Maybe not finding IEFRAME.DLL is okay too - though I've not seen that one before. It not finding SHCORE.dll, SHLWAPI.dll, EXT-MS-WIN-ADVAPI32-PSM-APP-L1-1-0.dll is a little disconcerting! Have you built any other DLLs (not plugins) with VS2012 and had them work? This looks like an issue with your machine more than it does FireBreath. :-(

Do you have all of the MSVC runtimes installed? Are you using the version of boost that came with FireBreath?

Neil

[Chris Manning]

Thanks for the response :) I have the latest runtimes installed, and am using the version of boost that comes with FireBreath. I've compiled other DLLs on this machine using VS2012 with no issues.

[Neil Griffiths]

Do you have the runtimes installed for older versions of MSVC? Specifically the runtime needed for the boost that comes from FireBreath?

I don't use it, I use my own - so I'm not familiar with how that works. But that would be my guess. You're definitely missing dependencies - I just don't know which ones!