I am running Ubuntu 12.04 LTS. I need to run a Mono environment application (which needs Windows forms).
I have installed Mono runtime, from badgerports.org, version: mono-runtime 3.2.8+dfsg-4~dhx1+precise1.
When I go:
mono Application.exe
it bumps with:
Could not load file or assembly 'System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.
I have then installed:
libmono-winforms2.0-cil 3.2.8+dfsg-4~dhx1+precise1
But when running again:
mono Application.exe
I am getting the same error message as before:
Could not load file or assembly 'System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.
Help will be appreciated
Many thanks in advance
Helen
Edit: should I find where the library has been downloaded (how)? and then install it into Mono GAC using gacutil (How??)
Related
I have an application which I build using conan with different profiles for arm32, arm64 and x86_64.
I am trying to make a debian package which would contain all 3 versions of the application and install the appropriate one depending on the system. Is this possible?
So far I have created a root folder, lets call it my-app and inside it I have folders arm32, arm64, amd64 and DEBIAN. First 3 folders contain folder structure /usr/local/bin/my-app-files while the DEBIAN folder contains control file with the following content:
Package: my-app
Version: 1.0
Maintainer: me
Architecture: arm32 arm64 amd64
Description: My app
Depends: libgomp1
Will this work? Is this the correct way to do this?
I am on a Dell Inspiron laptop with an AMD graphics card and am aiming to install a python package named pyviennacl:
https://github.com/viennacl/pyviennacl-dev
I am using Developer Command Prompt for VS 2019.
When I run:
pip install pyviennacl
The following error message is returned:
LINK : fatal error LNK1181: cannot open input file 'OpenCL.lib'
error: command 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.20.27508\bin\HostX86\x86\link.exe' failed with exit status 1181
Now, I really have no idea how to proceed. I can see what the error is but cannot find any help.
I've tried to install various Intel/AMD OpenCL packages to remedy this issue, however, to be completely honest, I do not know what I'm doing.
did you had a look to this post ?
Also, I resolved the same issue by defining the LIB environment variable to the directory containing the "OpenCL.lib" file (by default at C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.0\lib\x64 for NVIDIA graphic card. It can be different for AMD or Intel GPU).
In summary, PATH is where your binary will look for .dll files at runtime. To tell link.exe where to look for your .lib libraries you need to configure the LIB environment variable instead. (source here)
I try to install vtune command line interface on a target machine following the instrument https://software.intel.com/en-us/vtune-amplifier-install-guide-windows-installing-command-line-collectors. But get the error popup like the screenshot below. Any idea of it?
Met the same error for installing CLI for VTune Amplifier 2019 Update 4.
After some digging with unpacking msi package and dependency walker discovered that msi custom action dll imports functions from amplxe_sampling_utils_3.9.dll. Also this file relies on MS Visual C++ 2013 runtime.
For me it helped taking this dll from the VTune full installation (by default it is located at
C:\Program Files (x86)\IntelSWTools\VTune Amplifier 2019\bin32\amplxe_sampling_utils_3.9.dll
and placing it somewhere under system %PATH% for the installation purposes. I have not found better place than C:\Windows\System32 on a 32-bit target.
After the successful installation this dll can be removed from System32 as it it also installed with command line interface into target directory.
I am compiling openssl-1.1.0h version on Window 7 64 bit machine.
I have followed below steps:
Downloaded the source code from open ssl website
https://www.openssl.org/source/
Installed Visual Studio 2015 and required Perl environment.
perl Configure VC-WIN64A --prefix=custom-dir --openssldir=custom-dir no-asm shared
nmake
namke test
nmake install
I am able to successfully compile the source code, but it has created libcrypto.lib and libssl.lib files under lib folder. How can I create dll instead of libs?
I downloaded the X264 source and installed mingw.
Step 1:
Executed this in the MINGW bash:
./configure --disable-cli --enable-shared --enable-win32thread -
-extra-ldflags=-Wl,--output-def=libx264.def
and then 'make'
Step 2:
Renamed the libx264-142.dll to libx264.dll and Opened up VS2012 Command Prompt and executed this:
LIB /DEF:libx264.def
which gave me libx264.lib and object libx264.exp
Step 3:
Included the lib file in a VS2012 project which uses the X264 API.
Problem:
When I start the project I get the following error message:
"The program can't start because libx264.dll is missing from your computer"
Question:
Why is it looking for the dll when I'm linking the static library in?
How do I resolve this? I would like to build a static X264 library which I can link in with my project.
EDIT:
I just had to put the dll in the same directory as the project executable.
However - My question still stands: How do I build a static x264 library? So I don't need the dll?
After the latest update of x264 you can build static library usable by MSVS project. For such library compilation you will need:
MSYS and MSVS 2013 Update 2 (express version [for Windows Desktop] would also work if you install Update 2)
run "VS2013 x86 Native Tools Command Prompt" or "VS2013 x64 Native Tools Command Prompt" depending what version (32 or 64-bit) you want to build
change dir to x264 path and run MSYS shell (sh)
from shell run "CC=cl ./configure --disable-cli --enable-static" for x264 configuring
run "make" which should build libx264.lib usable from MSVS
P.S. MSVS builds would be a little bit slower than one build by MinGW
Matthew Oliver has a GIT repository of a patched x264 source tree (https://github.com/ShiftMediaProject/x264) that compiles natively in VS2013 update 2 and later. It requires installing a YASM version for VS.
It worked pretty much straight out of the box for me, though I did have to change the VSYASM parameter "-f Win32" to "-f win32" for a 32bit build
Take a look here: http://siliconandlithium.blogspot.no/2014/03/building-x264-on-windows-with-visual.html
Static lib is not possible in windows as per my knowledge.