I'm using sqlite3, fmdb glad to know that, but try to use, build upon get errors. I do not know why. Gcc4.2 compilation options are used. (or LLVM GCC4.2). I need a good solution.
For those of you that might have this problem. Remove fmdb.m from your project and it will compile fine.
Related
I am attempting to add a CefSharp control to an AnyCPU project. I have followed the instructions here: https://github.com/cefsharp/CefSharp/issues/1714 and I thought I had everything working correctly. I pushed my changes to to SVN and then checked out a clean copy.
The first time I attempted to build using that clean copy, I received this error:
error MC3074: The tag 'ChromiumWebBrowser' does not exist in XML namespace 'clr-namespace:CefSharp.Wpf;assembly=CefSharp.Wpf'. Line 18 Position 14.
as a result of this error, several other libraries fail to compile. If I attempt to build again, everything compiles fine.
I ran a diagnostic build, and, it appears that the CefSharp packages are in fact being installed from NuGet prior to this error and, the error occurs during MarkupCompilePass1.
This seems very, very similar to this issue: https://github.com/dotnet/project-system/issues/4158, however, in that case, it sounds as if the problem was resolved by switching from package.config to PackageReference, but, that approach did not seem to fix my error.
I have read https://www.xavierdecoster.com/post/2014/03/06/migrate-away-from-msbuild-based-nuget-package-restore.html as amaintland suggested in the issue I mentioned above, and, unless I'm misunderstanding, it's not a solution that I can use. For the time being, out continuous integration runs on CruiseControl (which isn't mentioned as a tool that supports automatic package restore out of the box), and we're stuck on VS 2013.
Right now the only option that I can find that seems like it might work is checking the NuGet packages into SVN. This is a last resort solution for me, but, lacking a better option, I don't know what to do.
If anyone has any insights or suggested steps, I would really appreciate the advice.
For now i'm working on complicated Qt project and trying to eliminate many of warnings which appears when i'm trying to build project with using of different compilers (gcc,clang,msvc). Full rebuild of project takes up a long time.
Is there a some tool or maybe a artful approach to rebuild only modules that has warnings on previous build?
I think it might be reached by deleting (or outdating) those modules. Thus Make utility can rebuild them for me.
As the earlier comment say, only do a normal build. Anything that didn't compile last time will now compile. This of cause requires that you set a compiler flag to treat warnings as error or the compiler will create object files even though there are warnings. And the above strategy will fail.
I am trying to build QtCore.lib and I get this weird error.
PRJ0019: A tool returned an error code from "MOC kernel\qtimer.cpp"
I am able to build qtmain.lib but not able tp go any further.
moc.exe is available in bin folder and the path is added to my PATH.
kernel\qtimer.cpp file is also present in corelib folder.
Any help in this regard will be appreciated. I am building with Qt-4.5.2 source.
In Qt 4.5.2 moc.exe has some issues. An email I sent to Qt Support mentions it moc'ing files that were not modified. It could have further issues, which could be related to what you are experiencing.
Sorry I can't recall the exact details. To make things worse the link Qt Support had sent me at the time is broken.
They had suggested using 4.5.3. I think we ended up staying on 4.5.1, which we are still using today, although the move to 4.7.x. is occurring as I write this. :)
I'm having a problem with adding the Qxt library to Qt Designer. The error it gives is:
Cannot load library C:/Qt/4.6.2/plugins/designer/QxtDesignerPlugins.dll; The specified module cannot be found.
Any ideas on what the problem is?
Try setting the QT_DEBUG_PLUGINS environment variable to 1 and then try again. This should give you some additional debug output that will help isolate the problem.
Did you check that this file is actually there?
Usually, the problem with designer plugins is that they're installed in the wrong directory, or linked against a different Qt (esp. debug vs. release).
Check that the plugin itself can find all the dlls it depends on. Use depends.exe (Dependency Checker) or maybe FileMon.exe to find out.
The error message can be a bit misleading, as it is the same if any of the primary dlls dependencies are missing too.
I have been working on a project for a long time now and there have been numerous situations in which I cannot seem to build.
I try 'clean', then I try building again.
Whether I do this manually or 'automatically' via saving it doesn't help anything.
This particular time I have no idea what to look for.
Can anyone shed some light on what the heck is happening?
Very frustrating.
Thanks,
jml
EDIT:
The main issue now seems to be the following error:
File not found:
file:/yourhd/documents/flash_files/your_project/bin-debug/your_project.html
I understand that it can't find the html file, but i can't force it to rebuild it, no matter what i've tried.
What do you mean that it won't build? Is there a build error?
If you have a compiler error, Flex won't build and you'll always be running old code when you debug, so make sure you take care of your source folder errors.
I suspect this is happening because "something" happened to your bin-debug folder.
The fastest fix is to simply nuke the entire folder, then rebuild - FlexBuilder will recreate it for you.
Sometimes a hung instance of FlashPlayer or your testing browser can cause this. Kill them in you task list (or other-OS equivalent)
you just need to do a "clean" before doing a rebuild. it should regenerate the html template file.
I've seen this same thing happen a few times. Everything's okay and then it just stops building. Clean doesn't fix anything and usually anything object I add in the MXML file suddenly isn't visible to the AS code.
There's probably something solveable but after fighting for a while I found it's quicker to just create a new project, copy everything and rebuild.