Posted
over 12 years
ago
by
[email protected]
(GeoffC)
That's pretty much what I did, but it wouldn't work. For my dylib, I ended up with: if (APPLE) SET( CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS} -Wl, -rpath /Users/Shared/MyFolder") endif()
|
Posted
over 12 years
ago
by
[email protected]
(GeoffC)
Hi Richard, I'm using FireBreath 1.7, from just a few days prior to your official 1.7 release (no particular reason, we were just up and running fine at that point). We have a plugin that has no UI and is simply used to control external devices. I'm noticing that when our plugin is loaded, we get the
|
Posted
over 12 years
ago
by
[email protected]
(Taran Rampersad)
I only violated #2. :-) I violated #1 *once*. That's all it took. I have not violated #3, but I shall try to do better. ;-)
|
Posted
over 12 years
ago
by
[email protected]
(Richard Bateman)
That's because you're violating a couple of core rules: 1) Don't ever change the files in the build directory manually. If you do, cmake will overwrite the files the next time it needs to run. 2) Don't ever try to run a different prep script on the same build directory. 3) Don't ever copy a build directory to another computer.
|
Posted
over 12 years
ago
by
[email protected]
(Taran Rampersad)
No, it won't delete any of the files, but it might overwrite some stuff. I'm not 100% sure, but when swapping from a 32 bit to 64 bit build in the same directory by running prep2010x64.cmd, the build was getting peculiar link errors. So I did a fresh FB build in another directory with fbgen.py/prep2010x64.cmd and those problems went away.
|
Posted
over 12 years
ago
by
[email protected]
(Richard Bateman)
… You don't need to delete any of your files, just delete the build/ directory and rerun the prep script. unless you've changed firebreath internal files that should fix it. Richard
|
Posted
over 12 years
ago
by
[email protected]
(Taran Rampersad)
Backup your own files and those you have diligently copied from the gen_templates directory, then regenerate the project as mentioned above. Then stick your files back in and update any dependencies within your project as needed. If that doesn't work, start with a virgin directory with Firebreath and do
|
Posted
over 12 years
ago
by
[email protected]
(Murasoli Selvan)
Hello, Did anyone solved this error, I am facing same issue. Muras K
|
Posted
over 12 years
ago
by
[email protected]
(Taran)
Oh, I agree completely. What the client wants, the client gets. With lots of warnings. That said, I'm exploring a few options for the client and if there's something useful that pops up, I'll wave it around. ;-) On Monday, February 11, 2013 4:59:50 PM UTC-6, Richard Bateman (taxilian) wrote:
|
Posted
over 12 years
ago
by
[email protected]
(Taran Rampersad)
Actually, someone asked that recently. Take a look here: [link]
|