I am trying to use CefSharp for MonacoEditor, but whenever I build the project it says this:
Severity Code Description Project File Line Suppression State Error CefSharp.Common contains unmanaged resoures, set your project and solution platform to x86 or x64.
I tried updating cef.redist.x64 and cef.redist.x86, but it says it's "not compatible." Can someone help me?
Related
I wanted to start learning the LibGDX Framework, and therefore using the Setup app to generate a new project sounded very convenient in the beginning. My problem showed up when i tried to import it as a gradle project into the eclipse IDE. The error message i get is as follows:
Description Resource Path Location Type Could not run build action
using Gradle distribution
'https://services.gradle.org/distributions/gradle-5.4.1-bin.zip'.
Build file 'E:\Workspace\Eclipse\LibGDX\test\desktop\build.gradle'
line: 27 A problem occurred evaluating project ':desktop'. Could not
get unknown property 'classesDir' for main classes of type
org.gradle.api.internal.tasks.DefaultSourceSetOutput. build.gradle /test/desktop line
27 Gradle Error Marker
Since I am pretty new to Gradle I dont really now what to do with that.
I have already tried to delete my .grade/wrapper/dist directory and let the LibGDX setup app download it all again. Also the version that was used int the setup app was 4.6 so i tried using that in the import, without success.
When using the gradle version used in the setup app I encountered an other Error message:
Description Resource Path Location Type Could not create an instance
of Tooling API implementation using the specified Gradle distribution
'https://services.gradle.org/distributions/gradle-4.6-bin.zip'. Could
not create service of type FileMetadataAccessor using
NativeServices.createFileMetadataAccessor(). Could not determine java
version from '11.0.3'. test line 0 Gradle Error Marker
If you need more information, dont hesitate to ask for it, I dont really know what you might need.
Thank you in advance!
"classesDir" is deprecated in gradle 5 and replaced with "classesDirs".
If you run into any other issues updating, you may find this link helpful.
I am trying to run a .NET Core version 1.1 application from inside VS Code version 1.8.1. When I push the F5 button, the console appears at the bottom of the screen. After enabling tracing, I get this output:
Reading fx resolver directory=[C:\Program Files\dotnet\host\fxr]
Considering fxr version=[.]... Considering fxr version=[..]...
Considering fxr version=[1.1.0]... Detected latest fxr
version=[C:\Program Files\dotnet\host\fxr\1.1.0]... Resolved fxr
[C:\Program Files\dotnet\host\fxr\1.1.0\hostfxr.dll]... Loaded library
from C:\Program Files\dotnet\host\fxr\1.1.0\hostfxr.dll Tracing
enabled
--- Invoked hostfxr [commit hash: 928f77c4bc3f49d892459992fb6e1d5542cb5e86] main Own DLL
path=[C:\Program Files\dotnet\dotnet.dll] Checking if CoreCLR path
exists=[C:\Program Files\dotnet\coreclr.dll] Detecting mode... CoreCLR
present in own dir [C:\Program Files\dotnet] and checking if
[dotnet.deps.json] file present=[0]
--- Executing in split/FX mode... Detected a non-standalone application, expecting app.dll to execute. Application 'build' is not
a managed executable.
Also, a bar appears at the top of the screen that says:
The preLaunchTask 'build' terminated with exit code 2147516564.
When I click the "show problems" option, a blank problems tab appears that contains the message:
No problems have been detected in the workspace so far.
Why is VS Code refusing the build the project, and why are there no problem messages? I am only posting this on SO, because Google was not helpful, and because the VS Code GitHub page recommends asking questions here first.
UPDATE
This problem was caused by me having put coreclr.dll in C:\Program Files\dotnet. I did this, because of a different problem related to building the app. I thought that, since the output mentions it is looking in this directory, it might be helpful to put this file here. It turns out that this was a very bad idea, as it just complicated the problem! LOL!
You can get this error if you have problems in:
packages - please check if all packages are ok and restored successfully
core version - check that core installed with correct version
.net tools - please check if version of .net tools correct.
Can you try visual studio?
I'm new to Netbeans Platform Development and following this tutorial.
When I try to build the project I get this error:
Module org.netbeans.modules.editor.util excluded from the target platform
There are apparently no errors in the app.
I'm using
NB 8.0
JDK jdk1.7.0_45
OS Win 8.1
What might be going wrong?
UPDATE:
Somehow the module was excluded via the disabled.modules in the platform.properties properties file.
When i comment it out (or remove it), it runs but gives this warning
Regards,
I nailed part of the problem. The error occurred because of unresolved dependencies.
I went through the tut again on a Linux Mint with NB7.4.
Now I get no errors but facing yet another problem. Now as I open a file, it opens the file but the Cookie Editor disappears.
I'm expecting someone will help on the second Issue.
Moderators: I'm not sure how will you guys respond to this but I've no clue how to go about my half solved problem.
With Vuforia's ImageTargets sample application, I tried using OpenGL ES 1.1 by setting USE_OPENGL_ES_1_1 to true in jni/Android.mk and uncommenting and changing the corresponding line in AndroidManifest.xml (). After converting the project so that it has a C++ perspective and associating ndk-build and the proper include directories, I could successfully run the application on my Android device.
However, the problem is that once I open up jni/ImageTargets.cpp, I get several errors from Eclipse, all from places where OpenGL ES 2.0 code would execute, the first one being:
Description Resource Path Location Type Symbol 'vertexHandle' could
not be resolved ImageTargets.cpp /ImageTargets/jni line 402 Semantic
Error
Sure enough, vertexHandle is defined at the top of the ImageTargets.cpp, inside the "#ifdef USE_OPENGL_ES_2_0" block. Because USE_OPENGL_ES_2_0 is not defined (per Android.mk), the code should be able to compile successfully, and sure enough, ndk-build does not report any problems. So it seems that only Eclipse reports the problems and when I run the project, Eclipse says, "Your project contains error(s), please fix them before running your application." And thus, I cannot run my application anymore. In a sense, it's kind of strange that this never occurred until I opened ImageTargets.cpp and Eclipse "discovered" the errors.
The best work-around I've found so far is to just delete or comment out those lines (that should not be causing problems because USE_OPENGL_ES_2_0 is not supposed to be defined)... Is there a better way to deal with this problem? Did I miss a setting in Eclipse that should solve this?
I've found a solution: go to the project properties -> C/C++ Build -> Discovery Options -> Check "Automate discovery of paths and symbols"
I installed CodeCover to my STS so I can use it in my project. I can run code cover and get the measurments, but there is one thing that is bothering me.
If I enable code cover for a given project, everytime when I make a change to a source file and then save it I get this error message:
[FATAL]An error occured when trying to compile instrumented sources
if there are some errors reported by eclipse validator in some project file. Can I disable this feature, because it is really frustrating that I save one file and I get bit message that there are errors, even if I can see them underlined red by the editor.
This is most likely a bug, I suggest you file a bug at the project web-site, or try to fix it yourself by getting the source.