My app in (perfectly working on windows 10 64bit on .NET 4.6) does not compile on linux. I followed a guide that states to run xbuild /p:VbcToolExe=vbnc.exe NAME.sln
That gave this error:
home/icbosk/Desktop/WindowsApp1/watch.sln: warning : Don't know how to handle GlobalSection ExtensibilityGlobals, Ignoring.
Then it fails.
I don't know how to do make this work on linux.
Here is the full output with diagnostics:
https://pastebin.com/WB5p9Zsi
Related
I'm trying to compile a pyqt5 application following the pyqtdeploy documentation but no success.
When running build-demo.py, it produces an error when qt is been configured.
I have downloaded all the correct and required tarballs for demo.
Also, if i compile qt separately, it works just fine following this https://www.ics.com/blog/how-compile-qt-source-code-linux.
Running this,
python3 build-demo.py --verbose
I get the following error:
pyqtdeploy-sysroot: Execution failed: returned exit code 3
I wonder if I am missing any command configure options or libraries.
Any help will be greatly Appreciated
I'm using python 3 on ubuntu 18
I built my application with the Facebook login feature for iOS last week.
I don't know why but when I opened my app today I get this strange error.
** BUILD FAILED **
The following build commands failed:
CompileC /Users/alan2305/dougo/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/jschelpers.build/Objects-normal/x86_64/JSCWrapper.o /Users/alan2305/dougo/node_modules/react-native/ReactCommon/jschelpers/JSCWrapper.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
CompileC /Users/alan2305/dougo/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/jschelpers.build/Objects-normal/x86_64/Value.o /Users/alan2305/dougo/node_modules/react-native/ReactCommon/jschelpers/Value.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
CompileC /Users/alan2305/dougo/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/jschelpers.build/Objects-normal/x86_64/JSCHelpers.o /Users/alan2305/dougo/node_modules/react-native/ReactCommon/jschelpers/JSCHelpers.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
CompileC /Users/alan2305/dougo/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/jschelpers.build/Objects-normal/x86_64/Unicode.o /Users/alan2305/dougo/node_modules/react-native/ReactCommon/jschelpers/Unicode.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(4 failures)
Installing build/Build/Products/Debug-iphonesimulator/dougo.app
An error was encountered processing the command (domain=IXUserPresentableErrorDomain, code=1):
This app could not be installed at this time.
Underlying error (domain=MIInstallerErrorDomain, code=4):
Failed to chmod /Users/alan2305/Library/Developer/CoreSimulator/Devices/27A18B40-AF2B-4FDF-A98C-796B1E53CC7B/data/Library/Caches/com.apple.containermanagerd/Bundle/Application/535974D3-D4A0-4EB1-AEE1-F7CBC7107F9B/dougo.app/dougo : No such file or directory
Launching org.reactjs.native.example.dougo
org.reactjs.native.example.dougo: 54919
Not able to find the solution to fix this please help.
here is my terminal error image
here is my XCode error image
When I follow the instructions to get Doppl going, and I run the dopplBuild Gradle task, I get an error message about j2objc returning error code 127. What is going on?
One cause of this is not having a JDK available for command-line use on your development machine. While Android Studio can use its own JDK copy, that does not make javac and related tools available from the command line. The j2objc tool in the Doppl toolchain needs these tools available from the command line.
The simplest solution is to download and install a JDK, following whatever the normal practice is for doing so on your development machine's OS, such as downloading JDK 8 from Oracle's site and installing it. If javac runs successfully from the command line, then try running dopplBuild again and see if you get past the "error code 127" result.
I'm trying to build detours library, and I encountered some problems that I did not succeeded to solve.
I ran on Windows 7 and 10 64bit, Visual Studio 2015.
I tried in all possible command prompts( WOW64/ VS), ran vcvarsall.bat/vcvars32.bat.
Please find attached the errors that I've got.
Is there any other way to do it? or what could be the problem?
Thanks.
Since the Detours Express only supports 32-bit processes, some of the files, such as disolx64.cpp and disolarm.cpp, cannot be compiled.
To work around the problem, try commenting the #include "disasm.cpp" directives in the disol*.cpp files that generate the fatal error messages (i.e. excepting disolx86.cpp). Then compile using nmake command.
Or better find and download DetourExpress.msi.
I'm trying to create a simple (software) driver using these instructions.
Host is Windows 7 x64 with fully updated MSVS Express 2013.
Latest windows driver kit is installed and working fine.
A virtual machine also with Windows 7 x64 is succesfully provisioned by VS, and configured exactly following these instructions.
The deployment process seems to execute properly and the build log shows something like:
1> Catalog generation complete.
1> <snip>\Win7Debug\Driver Package\driver.cat
1> Done Adding Additional Store
1> Successfully signed: <snip>\Win7Debug\Driver Package\driver.cat
1>
1> Deploying driver files for project "<snip>\Driver Package\Driver Package.vcxproj". Deployment may take a few minutes...
2>------ Deploy started: Project: Driver, Configuration: Win7 Debug Win32 ------
2> Done Adding Additional Store
2> Successfully signed: <snip>\Win7Debug\Driver.sys
2>
3>------ Deploy started: Project: Driver Package, Configuration: Win7 Debug Win32 ------
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 2 succeeded, 0 failed, 0 skipped ==========
However, when Visual Studio tries to start a debug session, I receive the following error message:
Unfortunately, there's no mention of which file it can't find. I've tried attaching a debugger and hooking kernel32's MessageBox so that maybe I could check the call trace / see which file it is looking for, but VS doesn't like me attaching ollydbg and it brings up a whole lot of other issues.
I've also tried Process Monitor to see what file it is trying to access but it's pretty hard to wade through everything it is doing.
Am I missing something? Anyone can point me in the right direction?
edit1: Did a clean install of both the host as target machine. Followed instructions perfectly: exact same error. Has nobody come across this before?
So the answer is that Visual Studio defaults to Kernel Debugger rather than Remote Debugger. Changing this at least got it to deploy and install the driver, but still caused the build process to hang forever.
I've given up on trying to write a KMDF driver and will instead opt for a global hook via SetWindowsHookEx instead. Not something I preferred, but the process for writing a kernel mode driver in Windows is way too tedious in my eyes.