I am new Lua user. No experience with C++. I need to have test code coverage functionality my tests in Lua so after googling I found this site:
https://github.com/nmcveity/lcovtools
Nice but the author says:
"Turn luacov/luacov.cpp into a Lua module"
and I stopped here. No experience what tool to use to do this.
I am Windows 8.1 user; Lua ver 5.1.4 .
Can somebody deliver me a ready to use solution for my problem (eg which compilator with all magic options to have ready to use Lua module)
Thanks in advance.
Rafal
compile it as DLL named lcovtools.dll. You can use any compiler you want but i recommend using Visual Studio. Create a new DLL Project. Delete all files and just add luacov.cpp
You can follow http://msdn.microsoft.com/en-gb/library/ms235636.aspx on how to setup the project
http://www.visualstudio.com/downloads/download-visual-studio-vs#d-express-windows-8 here is a free version of Visual Studio.
Related
There's a great article here that describes how to use native C++ libraries in Xamarin/C#, and I would assume that this would extend to MAUI: https://learn.microsoft.com/en-us/xamarin/cross-platform/cpp/
I followed these instructions, and put together an end-to-end demo solution of it here: https://github.com/whodges/bindingsample. This does require that you link Visual Studio to a MacBook to build the full solution.
That example essentially uses the default MAUI template, and modifies it slightly so that the actual 'click counter' value is set and retrieved from a native library on a per-platform basis. For Windows, that's a C++ DLL (works great). For Android, that's a .so library (works great). And for iOS, that's a static .a library, and here's where I'm running into trouble: when I try to launch this app using the iOS Simulator, it fails with a clang++ error, and something along the lines of "Could not extract the native library 'libCounteriOS.a' from .../obj/Debug/net6.0-ios/iossimulator-x64/linker-cache/libCounteriOS.a'. Please ensure the native library was properly embedded in the managed assembly (if the assembly was built using a binding project, the native library must be included in the project, and its Build Action must be 'ObjcBindingNativeLibrary')".
I created a C# .NET iOS Binding Library project (Counter.iOS in my example), and this is supposed to bundle libCounteriOS.a, which is generated when CounteriOS (a C++ project) is compiled. First, when Counter.iOS is built using Visual Studio on Windows, it fails to generate the Counter.resources folder in its 'bin' folder, along with the subsequent 'manifest' file. When I use Visual Studio for Mac, these files do get generated. So, I stuck with Visual Studio for Mac to build the iOS.Counter project (everything else is built with Visual Studio on Windows).
Regardless, I still get the "could not extract the native library" error I described. I've tried setting the library file's Build Action in Counter.iOS to ObjcBindingNativeLibrary, but that just results in an unhelpful "Build failed - see build log for details" error in Visual Studio for Mac, and I cannot find said log file for the life of me. On top of that, it's not an Objective C library anyway - it's a C++ one - so I'm not sure if this step is actually appropriate. Does it have to be Objective C? The Xamarin article suggests otherwise, and the native reference option 'Is C++' is there as well. I've also tried setting libCounteriOS.a's Build Action to 'BundleResource' - no luck with that either. I've tried it with .NET 7.0 as well - also no luck there.
I'm really at a loss. Is this even possible? It doesn't seem to work and I've been poking at it for weeks on it. That Xamarin article seems to suggest it should be possible. Any help would be greatly appreciated.
I have an asp.net web application (.NET Framework) by Visual C#, and this web application uses native C++ DLL by DllImport. The native C++ DLL project is also part of the solution. However when I do the debugging, and try to step into the native C++ code, it fails, the breakpoint on the C++ code shows "the breakpoint will not currently be hit no symbols have been loaded".
The solution is : make sure The "Native Code" check box (Project>Property>Web>Debugger>native code) as shown on the picture is checked. By default it is unchecked when the .net project is created.
I spent whole morning to find out cause, and it is not mentioned in stackoverflow and other website, therefore would like to share the solution.
//Follow Jack's suggestion to post the solution as an answer, instead of putting it as part of the question. Thanks Jack.
According to my client's demand, I am aiming to write a Internet Explorer BHO which on button click executes my custom Javascript. I have started with this link which contains an example BHO which is inplemented in C++,
http://www.codeproject.com/Articles/37044/Writing-a-BHO-in-Plain-C
But when I try to run it in Visual C++ 2010 Express, it doesnot build. I have these question regarding IE BHO:-
1) On which platform can I build and make changes to the above example code , in VC++ 2010 or Windows 7 SDK?
2) Any other tutorial you can refer me; which can guide me how to make BHO in C++ ?
3) I intend to make a button while using IE BHO, such that whenever it is clicked, my custom javascript is executed. Can anybody give me a general guidance on how to do this?
I have searched alot about this matter on Internet, but it seems that majority of the people are implementing BHO in C#. I am in need of some good suggestions.
First question: You should not ask a question saying "it does not build" and saying nothing about your build problem. Do you want us to download the project and guess what is Ok and what is not depending on VS and OS versions? Update your question with your build problem.
Second question: Use Google: Building Browser Helper Objects with Visual Studio 2005 It's old now, but nothing has really changed since then. Alas, you must have an ATL capable version of VS, and the Express versions are not. Anyway,I very strongly discourage writing a C++ BHO without the help of ATL. You may get the ATL sources by downloading a recent SDK, but you will not have the wizards. If you have a "full" VS2008, it will do the job perfectly well.
Third question: general guidance is the IHTMLWindow2 execScript method
I am currectly finishing my project in C++ and i'm looking for a way to create my own C++ installer file
which will create the project dll's and exe files into a specific path
what is the easier way to learn how to do it?
There are several ways to build an installer. While you can of course always make one yourself, you should google for something like "create an installer". Some prebuilt solutions include "InstallShield", or the ".msi" file format, which you can create on your own using something like "Advanced Installer".
Of course, if you want your users to build your project from source, then you need a makefile and to make sure you bundle all the libraries. There are also kits like autotools to do that for you.
If you use VS 2010, Installshield LE would suffice as it is integrated into VS 2010.
If you have access to Installshield IDE, there is nothing better available for your packaging needs.
There are two ways of packaging:
a) The LEGACY way
b) The Windows Installer way, Basic MSI is the keyword here.
The LEGACY way involves creating your own scripts for:
a) Installing the files to their locations
b) Writing registry entries, if needed
c) Registering COM components, if needed
d) Creating shortcuts etc...
Tools that can be used for LEGACY approach are:
a) NSIS - very good and has a scripting language of its own.
b) Installshield - has a project type called Installscript Project. Installscript is the scripting language to be used.
The Windows Installer way is a bit hard comapred to the LEGACY way.
One has to learn the basics of MSI technology which can be daunting.
The package created has .msi as extension. This file is a database that the developer configures and the Windows Installer takes care of all other things. This is called TRANSACTIONAL installation procedure.
Even the UI presented during install is configured in the Database using tables like Dialog, Controls etc...
Tools that can be used for Windows Installer approach are:
a) Installshield - has a project type called Basic MSI
b) Wix - Opensource and xml based. You configure appropriately named xml files and various utilities in the Wix package will help you to create an MSI package.
First after completing your project click save. Second click on file tab,Add,New Project.
In new Project Click other Project types , Setup and Deployment and in that You can click InstallShield LE or Visual Studio Installer.
Hope this Helped you
I always recommend NSIS. You might also investigate HM Nis Edit - it's an IDE for NSIS that has a useful wizard feature. It will generate an installer script for you which you can further customize. The documentation is extensive.
can't believe no one mentioned install creator pro(there is also a free version with a branded message that displays after installing). Its feature set is pretty limited, though it has options for writing registry values and specifying custom paths to %AppData% or any other place you may want to install some files. it also has an optional wizard interface, and with each step you have the oppurtunity to preview each individual page.
the paid version offers the option for adding serial number/registration to your program. i've never tried it so i'm not sure how effective it may be. its also quite and expensive little program, but i would recommend it atleast to the beginner or someone who is more concerned with maintaining the codebase of their program and less concerned with how fancy and decorated their installer program is.
i know its been a long time since this was posted but for future reference this program is far easier for any beginner to creating installation packages for the first time
I'm looking for a native C++ static analysis tool that I can use both from within Visual Studio and as part of a TFS 2010 build. It must also work for 64-bit compilation. Does anyone know any tools that support this?
I am using CppCheck.
This is a commandline tool which we use in our continous integration server, but I'm sure it can be called from a pre/post build event. It outputs to console or file (text/xml).
See our SD C++ CloneDR tool, which detects cloned code in spite of changes to layout, variable names and often even replaced statements.
This tool can be launched from a command line.
I'm not sure about 64-bit compilation. But, I think can use FxCop for static code analysis of C++ projects by integrating FxCop into VS2010 project, run fxcopcmd.exe in the post-build event to automatically perform code analysis when building projects (or) you can use Invoke Process Activity in Build process Template.
According to this blog, Visual Studio 11 will support 64-bit code analysis out-of-the-box in all editions:
http://blogs.msdn.com/b/codeanalysis/archive/2012/03/09/what-s-new-in-code-analysis-for-visual-studio-11.aspx