Failed to external entity ".../htmlhelp.xsl" - visual-studio

I'm building a development version of Wireshark to create dissectors, following the tutorial found in their official documentation
I receive two warnings and four errors. The four errors seems to come from the fact this link cannot be loaded. The errors are:
Build FAILED.
"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
"C:\Development\wsbuild64\docbook\developer_guide_chm.vcxproj.metaproj" (default target) (15) ->
"C:\Development\wsbuild64\docbook\developer_guide_chm.vcxproj" (default target) (118) ->
(CustomBuild target) ->
CUSTOMBUILD : warning : failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/htmlhelp/htmlhelp.xsl" [C:\Development\wsbuild64\docbook\developer_guide_chm.vcxproj]
"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj" (default target) (65) ->
"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj" (default target) (119) ->
CUSTOMBUILD : warning : failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/htmlhelp/htmlhelp.xsl" [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
"C:\Development\wsbuild64\docbook\developer_guide_chm.vcxproj.metaproj" (default target) (15) ->
"C:\Development\wsbuild64\docbook\developer_guide_chm.vcxproj" (default target) (118) ->
(CustomBuild target) ->
CUSTOMBUILD : I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/htmlhelp/htmlhelp.xsl [C:\Development\wsbuild64\docbook\developer_guide_chm.vcxproj]
CUSTOMBUILD : compilation error : file /Development/wireshark/docbook/custom_layer_chm.xsl line 8 element import [C:\Development\wsbuild64\docbook\developer_guide_chm.vcxproj]
"C:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj.metaproj" (default target) (65) ->
"C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj" (default target) (119) ->
CUSTOMBUILD : I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/htmlhelp/htmlhelp.xsl [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
CUSTOMBUILD : compilation error : file /Development/wireshark/docbook/custom_layer_chm.xsl line 8 element import [C:\Development\wsbuild64\docbook\user_guide_chm.vcxproj]
2 Warning(s)
4 Error(s)
Time Elapsed 00:00:07.72
When I go to the URL directly, I am taken to a blank page. Going through the directory online I can go up to here, but clicking on "htmlhelp.xsl" brings me back to the blank page.
However, although the VS 2015 CMD says the build failed, an executable version Wireshark is built and I can use it with more or less full functionality.
My main issue is I kept on having errors building a C++ dissector (Lua dissectors work just fine) due to LNK errors. I was thinking, because the build is "incomplete", the issues could be arising from a missing file or such.

Hopefully this will help someone with similar issues.
It turns out the file could not be reached because of the company's proxy settings. I have been using IE and the file would not load.
However, when I used Mozilla Firefox, I was able to download the file. I changed the XSL import address to a local directory containing the downloaded file and the import errors were fixed.

Related

Cycle inside ARVideoKit; building could produce unreliable results

I have encountered the issue while building a project in Xcode. It says "Cycle inside ARVideoKit; building could produce unreliable results. This usually can be resolved by moving the target's Headers build phase Compile Sources."
I've done so by looking into the build orders of ARVideoKit, I've moved the Headers in front of compile Sources. But the issue still persists.
Any tips would be greatly appreacited.
Below are the detailed error messages:
Showing Recent Messages
Cycle inside ARVideoKit; building could produce unreliable results. This usually can be resolved by moving the target's Headers build phase before Compile Sources.
Cycle details:
→ Target 'ARVideoKit' has link command with output '/Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Products/Debug-iphoneos/ARVideoKit.framework/ARVideoKit'
○ Target 'ARVideoKit' has compile command with input '/Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Intermediates.noindex/ARVideoKit.build/Debug-iphoneos/ARVideoKit.build/DerivedSources/ARVideoKit_vers.c'
○ Target 'ARVideoKit' has compile command for Swift source files
○ Target 'ARVideoKit' has copy command from '/Users/richardmac/Documents/GitHub/ARVideoKit/ARVideoKit/ARVideoKit.h' to '/Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Products/Debug-iphoneos/ARVideoKit.framework/Headers/ARVideoKit.h'
Raw dependency cycle trace:
target: ->
node: <all> ->
command: <all> ->
node: /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Products/Debug-iphoneos/ARVideoKit.framework/ARVideoKit ->
command: target-ARVideoKit-2bded4ab62199ada5f79527c1e5e4d0e2e48c26ea4c59645a2f99f2829476ecd-:Debug:Ld /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Products/Debug-iphoneos/ARVideoKit.framework/ARVideoKit normal ->
CYCLE POINT ->
node: /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Intermediates.noindex/ARVideoKit.build/Debug-iphoneos/ARVideoKit.build/Objects-normal/arm64/ARVideoKit_vers.o ->
command: target-ARVideoKit-2bded4ab62199ada5f79527c1e5e4d0e2e48c26ea4c59645a2f99f2829476ecd-:Debug:CompileC /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Intermediates.noindex/ARVideoKit.build/Debug-iphoneos/ARVideoKit.build/Objects-normal/arm64/ARVideoKit_vers.o /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Intermediates.noindex/ARVideoKit.build/Debug-iphoneos/ARVideoKit.build/DerivedSources/ARVideoKit_vers.c normal arm64 c com.apple.compilers.llvm.clang.1_0.compiler ->
node: <target-ARVideoKit-2bded4ab62199ada5f79527c1e5e4d0e2e48c26ea4c59645a2f99f2829476ecd--generated-headers> ->
command: Gate target-ARVideoKit-2bded4ab62199ada5f79527c1e5e4d0e2e48c26ea4c59645a2f99f2829476ecd--generated-headers ->
node: /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Intermediates.noindex/ARVideoKit.build/Debug-iphoneos/ARVideoKit.build/Objects-normal/arm64/UIView+isType.o ->
command: target-ARVideoKit-2bded4ab62199ada5f79527c1e5e4d0e2e48c26ea4c59645a2f99f2829476ecd-:Debug:CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler ->
node: /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Products/Debug-iphoneos/ARVideoKit.framework/Headers/ARVideoKit.h ->
command: target-ARVideoKit-2bded4ab62199ada5f79527c1e5e4d0e2e48c26ea4c59645a2f99f2829476ecd-:Debug:CpHeader /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Products/Debug-iphoneos/ARVideoKit.framework/Headers/ARVideoKit.h /Users/richardmac/Documents/GitHub/ARVideoKit/ARVideoKit/ARVideoKit.h ->
node: <target-ARVideoKit-2bded4ab62199ada5f79527c1e5e4d0e2e48c26ea4c59645a2f99f2829476ecd--phase0-compile-sources> ->
command: Gate target-ARVideoKit-2bded4ab62199ada5f79527c1e5e4d0e2e48c26ea4c59645a2f99f2829476ecd--phase0-compile-sources ->
node: /Users/richardmac/Library/Developer/Xcode/DerivedData/AR_Remote_Support-aaanobrrwbejkycmcyjzmsmrwiic/Build/Intermediates.noindex/ARVideoKit.build/Debug-iphoneos/ARVideoKit.build/Objects-normal/arm64/ARVideoKit_vers.o

Error CS2007: Unrecognized option: /analyzerconfig

I have a Unity project which I use Roslyn for Code Analysis and I found that you can get the warnings and errors report from console using msbuild.
In the PC I have VS 2019 version 16.6.3, it gave the following error that I will comment below and updated to version 16.11.9, thinking it was the incompatibility and still gets the error. I tried running the command described below on other PCs with other versions of VS and it works fine, but I have not been able to identify what makes the command work well.
Command:
By running the following line in Developer Command Prompt for VS 2019:
msbuild ScriptsAssembly.csproj /p:RunCodeAnalysis=true /t:Clean;Rebuild
I expect to see the total number of warnings for the project and zero errors with successful execution like this:
Instead I get the following error:
CSC : error CS2007: Unrecognized option: '/analyzerconfig:C:\Users\...\Documents\...\...\UnityProject\.editorconfig' [C:\Users\...\Documents\...\...\UnityProject\SimpleJSON
.csproj]
Done Building Project "C:\Users\...\Documents\...\...\UnityProject\SimpleJSON.csproj"
(default targets) -- FAILED.
Done Building Project "C:\Users\...\Documents\...\...\UnityProject\ScriptsAssembly.csp
roj" (Clean;Rebuild target(s)) -- FAILED.
Build FAILED.
...
"C:\Users\...\...\...\...\UnityProject\Project.csproj" (Clean;Rebuild target) (1) ->
"C:\Users\...\...\...\...\UnityProject\SimpleJSON.csproj" (default target) (2:3)
->
(CoreCompile target) ->
CSC : error CS2007: Unrecognized option: '/analyzerconfig:C:\Users\...\Documents\...\...\UnityProject\.editorconfig' [C:\Users\...\Documents\...\...\UnityProject\SimpleJS
ON.csproj]
1 Warning(s)
1 Error(s)
Time Elapsed 00:00:00.91
What I expect to see is a thousand warnings, instead of 1.
I don't know if I am missing a package to install in VS. I have seen the error that the compiler message mentions in the Microsoft documentation, but it doesn't help me much.
Any idea, or help is welcome.

Microsoft.Solutions.ResourceSelector - latest aure portal SDK doesn't recognize options->filter - is the Example out of date?

https://learn.microsoft.com/en-us/azure/azure-resource-manager/managed-applications/microsoft-solutions-resourceselector
IS this example out of date?
"c:\Users\idani\Desktop\POC----\src\Default\Extension\Extension.csproj" (default target) (1) ->
(CompileDxExtension target) ->
c:\Users\idani\Desktop\POC----\src\Default\Extension\Client\Create\CreateRedisForm.dx.json(35,41): error JSON0101: Failed to valida
te the schema of JSON file 'c:\Users\idani\Desktop\POC----\src\Default\Extension\Client\Create\CreateRedisForm.dx.json'. Details: Pro
perty 'filter' has not been defined and the schema does not allow additional properties. [c:\Users\idani\Desktop\POC----\src\Default
Extension\Extension.csproj]

I recently create a project of OPNET 14.5 and i have been unable to run the simulation. the error is about Pipeline stage model (dpt_ecc_pon)

I installed OPNET modeler 14.5 at my laptop (OS: Windows 8).
I slightly modified a process model, and ran simulation. But I see the following errors.
<<< Recoverable Error >>>
Pipeline stage model (dpt_ecc_pon) compilation failed
Source code was unavailable to the compiler
----
<<< Recoverable Error >>>
Object repository construction failed
Pipeline stage (dpt_ecc_pon) compilation failed, no source code found.
T (0), EV (-), MOD (NONE)
----
<<< Program Abort >>>
Error encountered rebuilding repository -- unable to proceed
T (0), EV (-), MOD (NONE)
How can i overcome this?
If you create dpt_ecc_pon pipeline stage source, there are some rules to define them. Based on your error message, the dpt_ecc_pon.ps.c/cpp is not included in the model_dirs.
All source code should be included in model_dirs. Press Ctrl+Alt+P. In preference dialog, search 'model_dirs' and make sure the directory where your codes are included in the 'model_dirs'.

Installing SystemC for VS2013

I am using Windows 10 64-bit machine with Visual Studio Professional 2013 and I want to install SystemC. I downloaded SystemC 2.3.1 and I tried following the "Installation notes" provided but they're slightly outdated.
For one, it says "for VS 2005 and higher on Windows 7 machines" but I am using Windows 10, nevertheless I still tried to follow it. Second, the inclusion of src and lib files cannot be followed as stated there since this method was changed in VS2013. There seems to be no global setting anymore via Tools->Options->Projects->VCC++ directions tab.
Now, I was able to successfully buiold the SystemC.sln solution. However, when I tried to build an example project I got the following error:
LINK : fatal error LNK1104: cannot open file
'C:\Users\Andrew\Downloads\systemc-2.3.1a\systemc-2.3.1a\msvc80\SystemC\Debug.obj'
Even though I think I've correctly specified the src and lib directories in the project properties.
Can anyone explain how to build SystemC with VS2013 on Windows 10 x64?
Update: if you use CMake with Visual Studio, check Setting up a SystemC project with CMake: undefined reference to `sc_core
Currently I have no MSVC2013 installed, so here are steps for MSVC2017 that worked for me.
Download latest SystemC from http://accellera.org/downloads/standards/systemc
Open systemc-2.3.1a\msvc80\SystemC\SystemC.sln in Visual Studio
Visual Studio will offer to update solution, click ok. You can ignore report with warnings.
In VS menu bar set configuration to “Debug“ “Win32”. (In my case was already selected by default)
Build solution (F7)
In console, you may find messages like:
Unknown compiler version - please run the configure tests and report the results
You can ignore them. Solution should build without errors:
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
As a result you will have SystemC.lib in systemc-2.3.1a\msvc80\SystemC\Debug
Now you can create some test SystemC project.
File->New -> Project -> Win32 Console application
Right click on project in solution explorer -> Properties
In Configuration Properties -> C/C++ -> General-> Additional include directories
Add path to: \systemc-2.3.1a\src
In Configuration Properties -> C/C++ -> Code generation -> Runtime Library
Select: Multi-threaded Debug (/MTd)
In Configuration Properties -> C/C++ -> Language -> Enable Run-Time Type Information
Select: Yes (/GR)
In Configuration Properties -> C/C++ -> Command Line -> Additional options
Type: /vmg
In Configuration Properties -> Linker -> General -> Additional Library Directories
Add path to: systemc-2.3.1a\msvc80\SystemC\Debug
In Configuration Properties -> Linker -> Input -> Additional dependencies
Add: SystemC.lib
Now it's time to type some code. For example this "Hello world":
#include "stdafx.h"
struct test_module : sc_module {
SC_HAS_PROCESS(test_module);
test_module(::sc_core::sc_module_name) {
SC_THREAD(test_thread);
}
sc_signal<std::string> message{ "message" };
void test_thread() {
message.write("Hello world!");
wait(1, SC_NS);
cout << message.read() << endl;
sc_stop();
}
};
int sc_main(int argc, char** argv)
{
test_module tmod{ "tmod" };
sc_start();
return 0;
}
In stdafx.h add:
#include <systemc.h>
Build project, it will fail with:
\systemc-2.3.1a\src\systemc.h(120): error C2039: 'gets': is not a member of 'std'
gets was removed from std namespace in latest MSVCs, but it is not really required.
So just open systemc.h and comment out Line 120:
// using std::gets;
In case you got error about sprintf
Add _CRT_SECURE_NO_WARNINGS to list of preprocessor definitions
Build again. Run without debugging (Ctrl+F5). You should see the following introduction test on your console:
SystemC 2.3.1-Accellera --- Feb 1 2017 14:43:06
Copyright (c) 1996-2014 by all Contributors,
ALL RIGHTS RESERVED
Hello world!
Info: /OSCI/SystemC: Simulation stopped by user.
Press any key to continue . . .
Hope that helps

Resources