firebreath

Try something like this on windows in a batch file: ============ @echo off REM buildboth.cmd prep2010.cmd projects build_32 cmake --build build_32 --config RelWithDebInfo prep2010_x64.cmd projects build_64 cmake --build build_64 --config ... [More] RelWithDebInfo ============ That should about do it. On linux it may be harder; I don't know myself offhand how to build for 32 bit on a 64 bit system, and I suspect you need a 64 bit system to build 64 bit. On mac it'll build for both by default, and with a FAT binary which will work on both 32 and 64 bit. Of course, on mac if you have a 32 bit it'll work on 64 bit browsers, so most people are better off just using a 32 bit binary. On windows cmake won't let you build both in the same project. [Less]

I'm fairly sure you can't do that from within CMake. But you could certainly write a script that outputs to two different directories that output a 64-bit and 32-bit project respectively. That's what I'd do anyway! For Linux and OSX (so long as you generate Makefiles there) you'd want to set:

Hi FireBreath-ers, I am looking for a way to generate, in one pass, both 32 and 64 bits of my plugin. Question: Is there any settings in CMake files I can set to automatically generate the two versions (32 and 64 bits) ? If not, I thought about ... [More] creating a script that switches the PluginConfig.cmake file with different configurations for 32 and 64bits.. [Less]

Neil just posted the exact information/link you are asking for. Richard

Thanks Gaurav for the immediate response. Could you give me some pointers to the first method "You can include link the source files by adding them to the cmake script"? I'm new to Firebreath. If there is any documentation available on this, could you please provide me the link? Thanks, Prem

Yes, I've seen this; it's strange. My work-around was the same as what you're proposing. I'm considering some code to aggregate these various workarounds to event strangenesses... but fear it will be incomplete and fragile in the face of evolving browser implementations.

[link]

There are couple of ways to do this. You can include link the source files by adding them to the cmake script. You can also include the project in Visual Studio but that is not recommended. You can also build your library separately with static flags on and link it to the firebreath project like

Hi, I've created the Firebreath plugin using fbgen.py and prep2012.cmd. Now I want to extend my plugin to work with a dependent static library project. How do I add a new static library projects to the existing Firebreath plugin solution? Can I just have the dependent project and source files under the

Hi Richard, Thanks for the response. Actually I figured out that the "Link Library Dependencies" was set as "Yes" in MyPlugin Property Pages -> Linker -> General -> Link Library Dependencies When I set that as 'No' the DLL function ... [More] related linker errors were gone. Now I'll try to use my static libraries from within the plugin and see how [Less]