I have a project which is windows 8 application that create by using VS C++, javascript and html5.
But when I compile the project (Windows Runtime Component project) using ARM solution platform, a winmd file is not generate. What I success to generate is dll file, pri file, ilk file and pdb file.
Can someone teach me how to generate winmd file?
Check the below image. You need to set the output type as Windows Runtime Component.
Related
I have windows dynamic linked library which I want to access from Linux environment. I don't have the source code of that library, so I cannot build .so file.
Is there a way by using Winelib or any other library or tool for converting library file to .so file, so that I can call functions defined in that library?
There is no easy way to do it, because the DLL cannot run in Linux enviromnemt all by itself. It will probably rely on user32.dll msvcrt.dll and friends at runtime, so you'll have to provide those files as well.
You can use winelib, but it doesn't just convert a .dll to an .so. You'll have to link the whole project that wants to call the DLL against winelib, and include the DLL itself with your app at runtime. If you are trying to port a Windows app to Linux, winelib will be able to convert your makefile for you, but it's far from automatic for complex projects.
i created selenium webdriver java project,is it possible to convert into .exe file.If it is possible means whether it runs in all other devices without need of any specifications.
Consider Launch4J java exe wrapper: http://launch4j.sourceforge.net/
Here is the documentation: http://launch4j.sourceforge.net/docs.html
In looking for a solution to this myself I recently created an application that can generate executable launchers, with optional embedded icon, for jar files.
CStExe will compile C# scripts into Windows executables, you can write C# scripts, or edit the included example script, to launch a batch file that points to your jar files or directly launch the jar file from the C# script then use CStExe to compile the script into a Windows executable.
Personally I prefer to use the executable to launch a batch (.bat) file rather than launching the jar directly. With this method you can just edit the batch file to reflect command/argument changes over the course of your applications development without having to re-compile the executable.
You can grab CStExe from my personal site here:
http://1337atr.weebly.com/cstexe.html
P.S. One of the benefits of this method is that you have a few options in regards to how the end user has access to the Java Runtime Environment.
One of my favorites is that you can bundle the JRE with your application so that the end user doesn't have to install it at all. In this case simply include the JRE in a subdirectory of your application.
For example if you have created an executable that launches a batch file that points to your jar, instead of calling java -jar from the batch file use something like "Java\JRE_1.8.0_25\bin\java.exe -jar Jars\MyApplication.jar" without quotes. This will launch the application via the included JRE.
Conversely if you're skilled in C# you could write your C# script so that running the compiled executable will check for installed Java and if it is either not found or an incorrect version instead of trying to launch the application it launches an included JRE installer or opens a web browser to the JRE download page.
So i am trying to get a C# application that i have developed that uses the Iconic Zip library, when i compile the program into an executable, and run it on another machine i get an error saying
"Could not load file or assembly 'Iconic.Zip...' or one if its dependencies. The system cannot find the file specified."
I realise that this is because the .dll is not in the same directory/expected directory as the exe.
Is there a way to bundle in the .dll to the exe through Visual Studio so that i do not have to provide the library as a seperate entity?
My background is Linux and traditional makefiles. I have a project where the makefile builds several dozen executables I can then run to perform tests against the library being developed. This library is now ported to Windows.
My question: In Microsoft Visual C++, do I have to create a new project for every individual test .exe file? Or is there a way to create 1 project that will easily build all of the .exe files? E.g., test001.cpp becomes test001.exe, test002.cpp becomes test002.exe, etc.
I'm using Microsoft Visual C++ 2010 Express. Right now what I do is click on File->Add->New Project...->Win32 Console Application->... for every test executable. But it would be nicer if all these test files could be built without a new project for each one.
You need to have one project per executable, but you can have multiple projects per Visual Studio "solution".
When you build a solution, all of its projects get built. If you need the projects to be built in a specific order within the solution, you can easily set up dependencies.
If you're using Visual Studio in the normal fashion, then yes, each VS project (i.e. each .vcproj file) corresponds to exactly one output file (an executable, DLL, or static library).
You can also use Visual Studio with makefiles though, if you want. Just write your makefile as usual, except the C++ compiler is the cl.exe in the VS binaries directory, the linker is link.exe, and of course all of the command line flags are completely different. You can even set your VS project to use make instead of its built-in system, so you can still use the IDE for editing and debugging.
I have an legacy application which builds into exe.
I am using Visual Studio 6.0 and the application is an c++ application. It used many lib files, built in VS6.0. Now i need to use the api's which in the executable. I want to create a lib file while it is creating an exe. I cannot change the code of the legacy application.
Any help is highly appreciated.
Thanks,
AH
Create a separate library project and add any source files with APIs you want to reuse into it. It's probably cleaner to also remove those files from the exe project and make the exe project depend on the library project, but this isn't strictly necessary.