When I build my Windows form application, I'm getting following errors. Can someone tell me what could be wrong?
ResGen : error RG0000: Could not load referenced assembly "\.....\bin
\Debug\PlugingCommon.dll". Caught a FileNotFoundException saying
"Could not load file or assembly '\...\PluginSource.dll' or one of its
dependencies. The system cannot find the file specified.".
ResGen : error RG0000: Could not load referenced assembly "\...\bin
\Debug\MetadataField.dll". Caught a FileNotFoundException saying
"Could not load file or assembly '\...\bin\Debug\MetaField.dll' or
one of its dependencies. The system cannot find the file specified.".
There are several such bugs in the solution.
I'd say the problem is that your system cannot find the files MetaField.dll or PluginSource.dll.
It's kinda glaringly obvious if you think about it.
Related
So I'm having this error in DS-5 assembly, I cant seem to make an executable file whenever I build the project, this is the only error I can't fix in my program, I heard it has something to do with directories.
Heres an image
I am trying to use nmake to build a program I downloaded (source). The program is old (1994) but I need to build it for research purposes.
As I'm using windows, I'm calling nmake whilst in the \install\dos\ directory, and receiving:
makefile(62) : fatal error U1052: file '..\source\targets.mak' not
found.
I've checked, and targets.mak does exist in 'X:\Desktop\rsaref\source\targets.mak' so I tried the command:
nmake /F X:\Desktop\rsaref\source\targets.mak
But I now receive the error:
NMAKE : fatal error U1073: don't know how to make 'desc.c'
I have no clue what i'm doing here as i've never used makefiles before, and as this program is highly depreciated, i'm struggling to find advice on how to use it.
I'm trying to build an R package which is calling some C subroutines via .Call.
All of the functions are working fine if I manually do R CMD SHLIB and then dyn.load the .dll files.
Now, I'm building the package with R CMD build.
I put all the C code in the src folder, together with the .h files for some libraries I'm adding. When I run R CMD build NAMEPACKAGE everything seems to be fine, but then when I run R CMD check NAMEPACKAGE I get the following errors:
*** arch - i386
Error in library.dynam(lib, package, package.lib) :
DLL 'NAMEFUNC' not found: maybe not installed for this architecture?
Error: loading failed
Execution halted
*** arch - x64
Error in library.dynam(lib, package, package.lib) :
DLL 'NAMEFUNC' not found: maybe not installed for this architecture?
Error: loading failed
Execution halted
ERROR: loading failed for 'i386', 'x64'
I was trying to get some information on the internet, I have the feeling that I should write a Makevars file, but honestly I spent a lot of time on the Writing R extensions tutorial (1.2.1) and I'm really struggling to understand what is it exactly that I need to do.
Could someone please beifly explain to me how to solve the problem? Consider I would like to submit my package to CRAN. Thanks.
I just found out what the problem was! It was (as usual) a fairly silly thing, I didn't know that even if you call a certain function with a certain name, the associated dll is automatically called with the name of the package and not of the function itself, like it happens instead when you just create your dll through R CMD SHLIB.
Therefore, in the NAMESPACE I had to add useDynLib(NAMEOFPACKAGE) instead of useDynLib(NAMEOFFUNCTION).
I am trying to compile the Win32 Example of the Parrot ARDrone SDK v1.8 using Visual Studio 2012 Express for Windows Desktop. I am running Windows 7 64-bit. The SDK is written in C, not C++.
I've managed to get through every error so far, but this one has me stumped.
When Run, I get these 3 messages in the Error List:
Warning 1 warning LNK4001: no object files specified; libraries used C:\Users\Netex\Desktop\ARDrone_SDK_Version_1_8_20110726\ARDrone_SDK_Version_1_8_20110726\Examples\Win32\VCProjects\ARDrone\Win32Client\LINK Win32Client
Error 2 error LNK2001: unresolved external symbol _mainCRTStartup C:\Users\Netex\Desktop\ARDrone_SDK_Version_1_8_20110726\ARDrone_SDK_Version_1_8_20110726\Examples\Win32\VCProjects\ARDrone\Win32Client\LINK Win32Client
Error 3 error LNK1120: 1 unresolved externals C:\Users\Netex\Desktop\ARDrone_SDK_Version_1_8_20110726\ARDrone_SDK_Version_1_8_20110726\Examples\Win32\VCProjects\ARDrone\Debug\Win32Client.exe Win32Client
I've tried many suggested solutions, including setting the SubSystem in Linker->System to "Not Set" and setting the entry point manually, which gets rid of the 2 errors and replaces it with:
`Error 2 error LNK1221: a subsystem can't be inferred and must be defined'
I've tried setting the Platform Toolset to v90 (which it was originally compiled in, I believe), which gets rid of the warning, but the errors persist.
QUESTION: What is causing these messages, and how can I fix it? Is it because I am trying to compile a Win32 console program on a 64-bit system?
Any help is much appreciated,
Dan
I'm using Qt VS Tools extension with Visual Studio 2019 and working in C++ on a Qt Gui Application created using the new project wizard. In my project properties under Configuration Properties | Linker | System, I have set SubSystem to "Console (/SUBSYSTEM:CONSOLE)" to cause a console window to come up alongside my GUI when debugging. This allows me to view outputs that I've added using qDebug like this:
qDebug() << "Testing";
What I have found is that if I perform a Build | Clean Solution and then Build | Build Solution, I get this error on the first build:
LNK2001 unresolved external symbol mainCRTStartup
Initially I was trying to figure out how to fix this (and ran across this post), but then I found that if I repeated Build | Build Solution the error goes away on subsequent builds, so my solution is to remember to build twice after a clean.
To see what would happen if I had never changed SubSystem to "Console (/SUBSYSTEM:CONSOLE)", I created a new Qt Gui Application project using the wizard. In this project SubSystem is set to "Windows (/SUBSYSTEM:WINDOWS)" as the default. Again I get the error on first build after a clean, but in this case it is a different unresolved symbol:
LNK2001 unresolved external symbol WinMainCRTStartup
Although I'm curious about the cause of the problem, the build twice solution is working for me for now.
in my case, the solution was to explicitly name the 'entry point', e.g. with the command line:
ml64 main.asm /subsystem:console /entry:main
the last option: '/entry:main' was crucial
I am recompling a project using Borland C++ Builder 6 and LMD tool 2010. The recompile process failed due to linker error. The message was:
"[Linker Fatal error] Fatal unable to open file LMDOneInstance.OBJ"
I searched the whole hard drive, but could not find any reference to LMDOneInstance.OBJ
Any help is appreciated.
Thanks in advance.
David
LMDOneInstance.Obj is an object code file generated a source file called LMDOneInstance.Cpp or a combined list of sources that make up the compiled object code. It could be an object file lying in a lib directory....
Hope this helps,
Best regards,
Tom.
Another good tactic is to look for
#pragma link "LMDOneInstance"
in your source code.
But tommieb's suggestion is also correct, look for LMDOneInstance.LIB and make sure it's path is in your library path or add the lib file to your project.