I am trying to compile mod_auth_openidc module on windows 7 64bit os
I got source code from
Source Code from github
I tried to build this module using visual studio 2015 but it was throwing an error "You must use GNU compiler".
From last few days am trying to build this in windows but ...
Could you please help me to build this module in windows or if any one done this in windows can you please share build steps.
Thanks...
It would be best to download the binary that is compiled for Windows from the release page but if you insist you can follow the guidelines from: http://wgsnetman.blogspot.nl/2013/04/building-apache-244-from-unix-source.html with a lot of adaptations/workarounds...
The code for mod_auth_openidc was forked to this git repository https://github.com/dematic-spe/mod_auth_openidc.
The build steps as documented on that page are:
bootstrap-windows.cmd
build.cmd - the output is in the tartet folder. The output is two zip files, one for x86 and one for x64.
deploy_to_artifactory.cmd
There were a couple of minor edits to the code so that it would also compile for win32 as well. It used the microsoft vcpkg project which is great at compiling a lot of opensource code for windows. I tested it all with VC2019.
Related
I tried to "Build Solution" from Visual Studio 2019, since the Python.NET project comes with a .sln VS Solution file
However, it skipped the Python.Runtime build which is what I'm interested in:
1>------ Skipped Build: Project: Python.Runtime ------
Furthermore, the other 4 builds had an error:
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\NuGet\16.0\Microsoft.NuGet.targets(186,5): error : Your project file doesn't list 'win-x64' as a "RuntimeIdentifier". You should add 'win-x64' to the "RuntimeIdentifiers" property in your project file and then re-run NuGet restore.
Alternatively, when running python setup.py following instructions on https://github.com/pythonnet/pythonnet/wiki/Installation#github-installation-from-master-branch, I ran into another error from not being able to find Windows Kits installed roots. Have been looking around for answers and tried different versions of Python, .NET Core, .NET etc. to no avail. I detailed it in https://github.com/pythonnet/pythonnet/issues/1272
Environment
Pythonnet version: 3.0 (ongoing, latest master branch ending at c81c3c3)
Python version: 3.7.9
Operating System: Windows 10, 64bit, WinPE
I just loaded pythonnet.15.sln instead of pythonnet.sln and was able to build the DLL file.
Although I'm still not sure why pythonnet.sln didn't work for me, does "15" refer to the VS version? The regular sln was being used in this screenshot from a talk https://youtu.be/P7Or7XzeIno?t=1163
When I starts a new project (Blank App (C++/WinRT)) on Windows10 1909 # VS2019(up to date) its shows up a lot of errors as if the extension wasn't installed. But after trying to compile and run its works - so why do I get the errors and how can I solve this? screenshot
Edit: I have fond a solution for that. its turns out that the project was needed an additional include directory:
under the project properties->C/C++->General->[Additional Include Directory]
I added the winRT folder:
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\cppwinrt
screenshot2
and that's it now there's no errors (correction - after creating new project its still have the same errors)
edit2:
Update: I installed the last windows 10 SDK and was still getting the seam errors. Than I installed a package via cmd with the following command:
D:\vcpkg> vcpkg install cppwinrt:x86-windows
after this was done it seem to work now
edit3:
I'm sorry for the annoying newcomer questions...
its looks like I have another problem now with my project
in the packages.config file is says that the package is not declared with the following warning packages.config pic
thanks for any help in advance.
(edit4) I followed this thread:
nuget 'packages' element is not declared warning
and that's it, now all I have to do is to learn how to code :D
The 'standard' include paths for Visual C++ projects are the VC_IncludePath and WindowsSDK_IncludePath. The Windows SDK includes path already has all of the directories:
include\<10.0.build.0>\ucrt
include\<10.0.build.0>\shared
include\<10.0.build.0>\um
include\<10.0.build.0>\winrt
include\<10.0.build.0>\cppwinrt
"Blank App (C++/WinRT)" is not part of the standard VS 2019 template set. The name of the project in the screenshoot is "ConsoleApplication2", which would imply you created a Win32 console C++ project instead of a C++/WinRT project. Even still, you can reach the standard C++/WinRT headers from a Win32 console application since they are part of the standard path.
From the looks of the errors in your first screenshot, it appears you are using a generated C++/WinRT rather than the one in the Windows 10 SDK. With VS 2019, you must add the NuGet package Microsoft.Windows.CppWinRT to your project to get the MSBuild rules needed to build with the C++/WinRT VSIX installed, so that's likely a problem here. See VS Marketplace
I have the same problem as described here:
https://github.com/NLua/NLua/issues/33
Though I have followed the instructions to create a console application...
http://www.screencast.com/t/M12TqePQxW
...which works just fine, when I create a library project and reference it from another project (in this case, a Web API project) the following error occurs:
Unable to load DLL 'lua52': The specified module could not be found.
At this line:
using (var lua = new Lua())
How can a library project be made with the NLua nuget package without failing?
It is the exact same issue as described in the GitHub issue, the Nuget package is missing two DLLs that you need to use lua52.dll. One small difference, the current package (version 1.3.2.1) includes a newer version of lua52.dll that was built with VS2013. And therefore has a dependency on msvcr120.dll and msvp120.dll.
Beware that this may change in the future when Nuget updates your project.
As-is, you need to download and install the Visual C++ redistributable package for VS2013. Run both vcredist_x64.exe and vcredist_x86.exe so your project can run either in 32-bit or 64-bit mode.
To avoid having to do this on the machine on which you want to deploy your program, I recommend you copy the two DLLs from the c:\windows\system32 (64-bit) or c:\windows\syswow64 (32-bit) directories into the same directory as your EXE.
The package author could have done a better job putting this package together. Short from including the DLLs in the package, the better solution would be for him to rebuild lua52.dll with the /MT option so these dependencies are linked in. Consider clicking the New Issue button to let him know.
I downloaded the WinPcap sources 4.1.3 as well as the corresponding AirPcap developer kit. I followed the build instructions described from the WinPcap website 1:
I loaded the project contained in the directory PacketNTx\dll\project with VS2013 (running on Windows 7 Professional x64). When I try to build the default project configuration (Debug, Win32) I get the error that the include file "netmon.h" cannot be opened. I also searched the web and found that this file is part of the wiretap library included in the Wireshark source code...
Can anyone suggest how to build the default configuration of the WinPcap packet.dll and wpcap.dll?
Thanks in advance!
best regards!
I'm building 2 different MSI with Visual Studio Setup Project. One for x86 and x64. But i couldn't find a way to combine both into one project so that the bootstrapper is installing the correct platform version.
Is there a way to do so in VS Setup Project or are are there any free 3rd party tools i can use? I found dotnetinstaller, but i'm not sure if that is what i'm looking for.
You can use WiX bootstraper: More info can be found here: http://www.wixwiki.com/
An example how to build both 32 and 64 bit MSIs you will find here:
http://blogs.msdn.com/astebner/archive/2007/08/09/4317654.aspx
You could write a native app and have it check if the system is x86 or x64 then have it write the correct installer to a temp directory and run it. I wrote a blog post that could probably get you started at http://blog.foldertrack.com/?p=45